Uptime Kuma MCP Server

Created By
Camusamaa year ago
Overview

what is Uptime Kuma MCP Server?

Uptime Kuma MCP Server is a server designed for managing Uptime Kuma monitors using the MCP protocol.

how to use Uptime Kuma MCP Server?

To use Uptime Kuma MCP Server, install it via pip with the command pip install uptime-kuma-mcp-server and follow the setup instructions provided in the documentation.

key features of Uptime Kuma MCP Server?

  • Manage multiple Uptime Kuma monitors efficiently.
  • Utilize the MCP protocol for seamless communication.
  • Easy installation and setup process.

use cases of Uptime Kuma MCP Server?

  1. Monitoring the uptime of various services and applications.
  2. Centralized management of multiple monitoring instances.
  3. Integration with other tools for enhanced monitoring capabilities.

FAQ from Uptime Kuma MCP Server?

  • What is Uptime Kuma?

Uptime Kuma is an open-source status monitoring solution that allows users to monitor the uptime of their services.

  • Is Uptime Kuma MCP Server free to use?

Yes! Uptime Kuma MCP Server is free to use and open-source.

  • What programming language is Uptime Kuma MCP Server written in?

Uptime Kuma MCP Server is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Camusama
Star
0
Language
Python
License
-
Category
monitoring
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago