Skip to content
Agentmart
Submit a tool

MCP Uptime Kuma

A Model Context Protocol (MCP) server for Uptime Kuma version 2.

Connector by DavidFuchs · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 60
Write a review

Chalk Labs

Need help deploying MCP Uptime Kuma?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/davidfuchs-mcp-uptime-kuma

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

A Model Context Protocol (MCP) server for Uptime Kuma version 2.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools
14 read · 11 write · 6 delete · 4 not yet classified
Secrets
4 (API keys, tokens or passwords)
Install scripts
None found
Runs as
Node.js package

Tools by what they do 35

Read from the source code; the running server may list different tools.

Read 14 · Look things up without changing anything.

  • getHeartbeats
  • getMaintenanceWindows
  • getMonitor
  • getSettings
  • getStatusPage
  • listDockerHosts
  • listHeartbeats
  • listMonitors
  • listMonitorTypes
  • listNotifications
  • listStatusPages
  • listTags
Show 2 more tools
  • pauseMonitor
  • resumeMonitor

Write 11 · Create, change, send or run things.

  • addDockerHost
  • addNotification
  • addTag
  • createMaintenance
  • createMonitor
  • createStatusPage
  • updateDockerHost
  • updateMaintenance
  • updateMonitor
  • updateNotification
  • updateStatusPage

Delete 6 · Delete, drop, revoke or wipe things.

  • deleteDockerHost
  • deleteMaintenance
  • deleteMonitor
  • deleteNotification
  • deleteStatusPage
  • deleteTag

Not yet classified 4 · We could not tell from the name and description.

  • getMonitorSummary
  • pauseMaintenance
  • resumeMaintenance
  • testDockerHost

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • UPTIME_KUMA_2FA_TOKEN
  • UPTIME_KUMA_HEADERS
  • UPTIME_KUMA_JWT_TOKEN
  • UPTIME_KUMA_PASSWORD

Other settings (environment variables or headers).

  • UPTIME_KUMA_URL
  • UPTIME_KUMA_USERNAME

Network hosts it talks to 1

  • github.com · found in code

Files it touches

  • /var/run/docker.sock

Tools (35)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • addDockerHostAdd Docker Host

    Creates a new docker daemon connection. For a unix socket use dockerType="socket" and dockerDaemon="/var/run/docker.sock". For a TCP proxy (e.g. tecnativa/docker-socket-proxy) use dockerType="tcp" and dockerDaemon="http://host:2375". Consider calling testDockerHost first to verify reachability.

  • addNotificationAdd Notification

    Creates a new notification channel. The configuration fields depend on the notification type (e.g., for slack: webhookURL; for ntfy: ntfyTopic, ntfyServerUrl; for discord: discordWebhookUrl).

  • addTagAdd Tag

    Creates a new tag that can be assigned to monitors.

  • createMaintenanceCreate Maintenance

    Schedules a new maintenance window. During maintenance, the monitors in monitorIDs are suppressed and show MAINTENANCE status instead of DOWN. A window created without monitorIDs suppresses nothing. Use strategy "manual" for a window you switch on and off with resumeMaintenance / pauseMaintenance.

  • createMonitorCreate Monitor

    Creates a new monitor in Uptime Kuma. Requires at minimum a name and type. Use listMonitorTypes to see supported types. For HTTP monitors include url; for TCP/port monitors include hostname and port; for json-query include url, jsonPath, jsonPathOperator and expectedValue; for database types (mysql, postgres, mongodb, redis, sqlserver) include databaseConnectionString. A push monitor is given a generated push token (Uptime Kuma only generates one in its own web UI) and the resulting ping URL is returned. timeout defaults to 0.8 x interval seconds for polled types.

  • createStatusPageCreate Status Page

    Creates a new (empty) status page with the given title and slug. After creating, call updateStatusPage to set the description, theme, groups, and monitors. Slug must be lowercase letters, digits, and dashes only.

  • deleteDockerHostDelete Docker Host

    Permanently deletes a docker daemon connection. Any monitors referencing it will have their docker_host cleared by Uptime Kuma (the monitors themselves are not deleted).

  • deleteMaintenanceDelete Maintenance

    Permanently deletes a maintenance window. Its monitors return to normal alerting. Use getMaintenanceWindows to find the ID.

  • deleteMonitorDelete Monitor

    Permanently deletes a monitor and all its heartbeat history. This action cannot be undone.

  • deleteNotificationDelete Notification

    Permanently deletes a notification channel. Monitors that used this channel will no longer send alerts through it.

  • deleteStatusPageDelete Status Page

    Permanently deletes a status page by slug. The status page URL will no longer be accessible.

  • deleteTagDelete Tag

    Permanently deletes a tag. It will be removed from all monitors that use it. Use listTags to find the tag ID.

  • getHeartbeatsGet Heartbeats

    Retrieves historical heartbeat data for a specific monitor (response times, status changes over time). Use this for analyzing patterns or history for one monitor. Beats are returned NEWEST-FIRST. By default returns only the most recent heartbeat; set maxHeartbeats (up to 100) for historical analysis. Keep maxHeartbeats ≤10 unless user requests more. Set important:true for the status CHANGES only (Uptime Kuma's own event list) — that is history, not current state, so do not read status from it. Credentials embedded in a status message URL (user:pass@host) read "***" unless includeSecrets is set…

  • getMaintenanceWindowsGet Maintenance Windows

    Returns all maintenance windows defined in Uptime Kuma, each with monitorIDs — the monitors it suppresses. A window with an empty monitorIDs list suppresses nothing.

  • getMonitorGet Monitor

    Retrieves configuration details for a specific monitor by ID (URL, check interval, notification settings, etc.). Use this when you need to examine or modify settings for a specific monitor. For current status, use getMonitorSummary instead. By default returns only common fields plus runtime data (uptime, avgPing); set includeTypeSpecificFields to true to include type-specific fields (e.g., url for HTTP, hostname/port for TCP).

Show 20 more tools
  • getMonitorSummaryGet Monitor Summary

    START HERE for status overview questions. Retrieves current status for all monitors showing UP/DOWN/PENDING/MAINTENANCE states with the most recent heartbeat message. Use this when asked "how is everything doing?", "what's down?", "what's up?", or for any general status overview. Returns essential information (ID, name, pathName, active state, maintenance state, status, message, lastBeatTime, type, tags). Supports filtering by keywords, type, active/maintenance status, tags, parent group, and current status. Check lastBeatTime before trusting the status of a push monitor — one that has stopped…

  • getSettingsGet Settings

    Retrieves the current Uptime Kuma server settings including timezone, authentication status, primary base URL, and other configuration options.

  • getStatusPageGet Status Page

    Returns the full configuration of a status page by slug, including the ordered list of groups, the monitors inside each group, and active incidents. Only works for published status pages (fetches the public `/api/status-page/{slug}` endpoint).

  • listDockerHostsList Docker Hosts

    Returns all docker daemon connections configured in Uptime Kuma. These are referenced by docker container monitors via docker_host.

  • listHeartbeatsList Heartbeats

    Retrieves historical heartbeat data for ALL monitors (response times, status changes over time). Use this for analyzing patterns across multiple monitors or correlating events. Beats are returned NEWEST-FIRST. By default returns only the most recent heartbeat per monitor; set maxHeartbeats (up to 100) for historical analysis. Keep maxHeartbeats ≤5 unless user requests more. Credentials embedded in a status message URL (user:pass@host) read "***" unless includeSecrets is set.

  • listMonitorsList Monitors

    Retrieves configuration details for all monitors (URLs, check intervals, notification settings, etc.). Use this when you need to examine or modify monitor settings. For status checks ("how is everything doing?", "what's down?"), use getMonitorSummary instead. By default returns only common fields plus runtime data (uptime, avgPing); set includeTypeSpecificFields to true to include type-specific fields (e.g., url for HTTP, hostname/port for TCP). Supports filtering by keywords, type, active/maintenance status, tags, and parent group.

  • listMonitorTypesList Monitor Types

    Returns a list of all available monitor types supported by Uptime Kuma. Use this to discover valid values for type filters in other tools.

  • listNotificationsList Notifications

    Returns all configured notification channels (Slack, ntfy, Discord, email, webhooks, etc.). To attach a channel to a monitor you only need its id — the credentials in `config` are withheld by default and the names of the withheld fields are listed in `redactedConfigKeys`.

  • listStatusPagesList Status Pages

    Returns all configured status pages with their slug, title, visibility, and custom domain settings.

  • listTagsList Tags

    Returns all tags defined in Uptime Kuma (name, color, and ID).

  • pauseMaintenancePause Maintenance

    Switches a maintenance window off: it stops suppressing its monitors and its schedule stops until resumed. For a manual window this ends the maintenance.

  • pauseMonitorPause Monitor

    Pauses a monitor, stopping it from performing checks. The monitor will remain in the system but will not send notifications or collect data until resumed.

  • resumeMaintenanceResume Maintenance

    Switches a paused maintenance window back on. For a manual window this starts the maintenance immediately; a scheduled window resumes following its schedule.

  • resumeMonitorResume Monitor

    Resumes a paused monitor, restarting all checks. Use this to re-enable monitoring after pausing.

  • testDockerHostTest Docker Host

    Tests connectivity to a docker daemon without persisting it. On success the message includes the number of containers. Use this before addDockerHost to avoid saving a broken configuration.

  • updateDockerHostUpdate Docker Host

    Updates an existing docker daemon connection. Use listDockerHosts to find the docker host ID. Only the fields you pass are changed — the others are preserved.

  • updateMaintenanceUpdate Maintenance

    Updates an existing maintenance window. Only the fields you provide are changed (the server merges them with the stored window). monitorIDs replaces the full monitor list. To switch a window on or off use pauseMaintenance / resumeMaintenance.

  • updateMonitorUpdate Monitor

    Updates an existing monitor configuration. You must include the monitorID. Only the fields you provide will be changed (the server merges your changes with the existing config). Use getMonitor first to get the current config.

  • updateNotificationUpdate Notification

    Updates an existing notification channel. Use listNotifications to find the notification ID.

  • updateStatusPageUpdate Status Page

    Updates an existing status page. Pass the full config (title, description, theme, published, etc.) and the full publicGroupList — both are replaced wholesale. Each group has a name, weight, and monitorList of [{id}]. Use getStatusPage first to read current state before modifying.

Signals

Stars
60
Forks
25
Open issues
0
Weekly downloads
271
Last commit
Oct 23, 2026 (10 days ago)
Last release
Oct 20, 2026 (13 days ago)
Last package publish
Oct 20, 2026 (13 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.DavidFuchs/mcp-uptime-kuma
Version
0.12.1
Auth
API key
Packages
npm @davidfuchs/mcp-uptime-kuma
License
MIT
Repository
github.com/DavidFuchs/mcp-uptime-kuma
First seen
Oct 24, 2026
Last checked
Nov 1, 2026
Source
Official MCP Registrygithub-graphql

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get MCP Uptime Kuma running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying MCP Uptime Kuma?

CallGet help
Cite this page

MCP Uptime Kuma. Agent Mart. https://agentmart.dev/connectors/davidfuchs-mcp-uptime-kuma (last updated 2026-11-01)