Uptime Kuma MCP Server

Created By
phukit29182a year ago
Overview

what is Uptime Kuma MCP Server?

Uptime Kuma MCP Server is a FastMCP (Message Control Protocol) server that serves as an intermediary for managing Uptime Kuma instances, allowing users to interact with monitors, tags, and status pages.

how to use Uptime Kuma MCP Server?

To use the server, clone the repository, install the dependencies, and run the server in either STDIO or SSE mode. You can then access various tools to manage your Uptime Kuma instance.

key features of Uptime Kuma MCP Server?

  • Adds, retrieves, deletes, pauses, and resumes monitors.
  • Manages tags associated with monitors.
  • Retrieves heartbeat data and status page details.
  • Asynchronous operations for efficient handling of requests.

use cases of Uptime Kuma MCP Server?

  1. Managing multiple HTTP monitors for uptime tracking.
  2. Automating the retrieval of heartbeat data for monitoring services.
  3. Customizing and managing tags for better organization of monitors.

FAQ from Uptime Kuma MCP Server?

  • What is required to run the server?

You need Python 3.7+, an Uptime Kuma instance, and access credentials.

  • How do I run the server?

You can run the server in STDIO mode or SSE mode by modifying the main.py file accordingly.

  • What happens if I don't set the required environment variables?

The server will fail to start and raise a ValueError if essential Uptime Kuma environment variables are not set.

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

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)

a day ago