Skip to main content
Glama
mehbul

uptime-kuma-mcp-server

by mehbul

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort for HTTP transport3000
TRANSPORTNoTransport mode: stdio or httpstdio
UPTIME_KUMA_URLYesThe URL of the Uptime Kuma instance (e.g., http://localhost:3001)
UPTIME_KUMA_TOTPNoTOTP 2FA code if enabled (used with username/password)
UPTIME_KUMA_TOKENNoJWT token from login with 'Remember Me' (alternative to username/password)
UPTIME_KUMA_API_KEYNoAPI key for REST /metrics endpoint
UPTIME_KUMA_PASSWORDNoUptime Kuma password (alternative to token)
UPTIME_KUMA_USERNAMENoUptime Kuma username (alternative to token)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
uptime_kuma_list_monitorsA

List monitors from Uptime Kuma with pagination and optional search.

Args:

  • limit (1-100, default 20): max to return

  • offset (default 0): skip N for pagination

  • search (optional): filter name/type substring

  • response_format: markdown (default) or json

Returns paginated list with has_more/next_offset. Use when: "show my monitors", "list http monitors", "what do I monitor?" Don't use when: you need single monitor details (use uptime_kuma_get_monitor).

uptime_kuma_get_monitorA

Get single monitor details by ID.

Args:

  • monitor_id (int): ID from list_monitors

  • response_format: markdown or json

Returns all fields (type, url, interval, status, tags). Use when: need edit/delete/pause context.

uptime_kuma_create_monitorA

Create a new monitor. Returns new monitorID.

Args:

  • name (required): display name

  • type: http|port|ping|keyword|dns|push|steam|mqtt|docker (default http)

  • url/hostname/port/keyword as required by type

  • interval (default 60, min 20)

  • notificationIDList (optional): { "1": true }

Use when: "monitor https://example.com every 60s" Don't use for edits (use edit_monitor).

uptime_kuma_edit_monitorA

Edit existing monitor. Only provided fields are updated.

Args:

  • id (required): monitor ID

  • name, url, interval, active, description (optional)

Use when: renaming, changing URL/interval.

uptime_kuma_delete_monitorA

Delete a monitor and its heartbeat history (destructive).

Args:

  • monitor_id (int)

Requires confirmation — this is irreversible.

uptime_kuma_pause_monitorA

Pause heartbeat checks for a monitor (sets active=false).

Args: monitor_id

uptime_kuma_resume_monitorA

Resume a paused monitor.

Args: monitor_id

uptime_kuma_get_heartbeatsA

Get recent heartbeats for a monitor (status, ping, msg, time).

Args:

  • monitor_id

  • period_hours (1-720, default 24)

  • limit (1-200, default 50)

  • response_format

Returns newest-first list. Use when: "show recent checks for monitor 5", "why was it down?"

uptime_kuma_get_statusA

Get uptime ratio and avg ping for a monitor over a period.

Args:

  • monitor_id

  • period_hours (default 24)

  • response_format

Returns: uptime (0-1), avgPing ms, computed from heartbeats if needed.

uptime_kuma_list_notificationsA

List notification channels (Slack, email, Telegram, etc.) configured in Uptime Kuma.

Returns id/name/type/active. Use when wiring monitor to notification.

uptime_kuma_list_status_pagesA

List public status pages.

Returns id/slug/title/published.

uptime_kuma_get_metricsA

Fetch Prometheus metrics from /metrics (requires UPTIME_KUMA_API_KEY or username/password).

Returns raw Prometheus exposition format. Useful for AI to parse monitor_status, monitor_response_time.

No params.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mehbul/uptime-kuma-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server