Skip to content

Use UptimeMonitoring through MCP

Model Context Protocol (MCP) lets AI agents interact with external tools. UptimeMonitoring’s MCP server lets any compatible agent create, inspect, and manage monitors using natural language.

ToolDescriptionRead-only
list_monitorsList all monitors with current statusYes
get_monitorGet monitor details + recent evidenceYes
create_monitorCreate a new monitorNo
update_monitorUpdate monitor configurationNo
delete_monitorDelete a monitorNo (destructive)
list_incidentsQuery incidents with filteringYes
assert_monitor_healthyCheck if monitor is healthy (for deploy gates)Yes
get_account_statusUsage against capsYes
TooltitlereadOnlyHintdestructiveHintidempotentHintopenWorldHint
list_monitors”List Monitors”truefalsefalsetrue
get_monitor”Get Monitor”truefalsefalsetrue
list_incidents”List Incidents”truefalsefalsetrue
assert_monitor_healthy”Assert Monitor Healthy”truefalsefalsetrue
get_account_status”Get Account Status”truefalsefalsetrue
create_monitor”Create Monitor”falsetruefalsetrue
update_monitor”Update Monitor”falsetruefalsetrue
delete_monitor”Delete Monitor”falsetruetruetrue

openWorldHint: true reflects that all tools make external API calls. idempotentHint: true is set only on delete_monitor — repeating the call after the monitor is gone produces the same result.

The MCP endpoint accepts Bearer credentials: API keys, session tokens, and OAuth access tokens. Which credential you configure depends on the host.

OAuth-based connector hosts such as Claude.ai, Claude Desktop, and ChatGPT should use the OAuth flow when prompted. Config-file and API clients such as Claude Code, Cursor, and the OpenAI API can pass an OAuth access token or a custom Authorization header when the host supports custom headers.

OAuth 2.1 discovery endpoints are published at https://api.uptimemonitoring.com/.well-known/oauth-authorization-server (authorization server metadata) and https://api.uptimemonitoring.com/.well-known/oauth-protected-resource/mcp (protected resource metadata for the MCP endpoint).

For API-key setups, use the same key as the REST API:

Authorization: Bearer umk_live_...

Create a dedicated key labeled mcp for API-key based agent setups.

User:
Create a monitor for https://example.com/healthz
and tell me whether it is healthy right now.
Agent:
I'll create the monitor and check its status.
Tool: create_monitor
Result: Monitor created (id: 1287, name: "example-healthz")
Tool: assert_monitor_healthy
Result: Healthy — EU, 200, ttfb 184ms

UptimeMonitoring’s MCP server is listed in the Official MCP Registry under com.uptimemonitoring/mcp. MCP-aware tools that auto-discover servers from the registry can install it without any manual configuration; the registry entry carries the canonical transport, endpoint, and auth metadata.

Manually maintained pre-release — open an issue if your host should be listed.

HostTransportAuthStatus
Claude.aiRemote MCP connectorOAuth
Claude DesktopRemote MCP connectorOAuth
Claude CodeRemote MCP HTTPOAuth / Bearer header
ChatGPTCustom MCP connectorOAuth✅ Listed on ChatGPT app store
CursorMCP configOAuth / Bearer header
OpenAI APIResponses MCPOAuth token / custom headers

Last verified: 2026-05-26.

Questions or issues with the MCP server? Email hello@uptimemonitoring.com.

In Claude.ai, open Customize → Connectors, add a custom connector, and enter:

https://api.uptimemonitoring.com/mcp

Complete the OAuth flow when Claude prompts you to connect your UptimeMonitoring account.

In Claude Desktop, add UptimeMonitoring through Settings → Connectors as a custom remote MCP connector:

https://api.uptimemonitoring.com/mcp

Complete the OAuth flow when Claude prompts you to connect your UptimeMonitoring account. Remote MCP servers in Claude Desktop should be added through Connectors, not claude_desktop_config.json.

OAuth or Bearer header via claude mcp add. Full install steps, verification, and common errors: Connect Claude Code.

OAuth via the ChatGPT connector UI. Listed on the ChatGPT app store. Full install steps, verification, and common errors: Connect ChatGPT.

Bearer header or OAuth via mcp.json. Full install steps, verification, and common errors: Connect Cursor.

MCP tool in Responses API calls, API key or OAuth token. Full install steps, verification, and common errors: Connect via OpenAI API.