Drive your monitoring from an AI agent

Uptime Globe exposes a remote Model Context Protocol server so your AI client (Claude Code, Claude Desktop, claude.ai, Cursor, …) can read and manage your monitors, incidents, channels, rules, maintenance windows, and status pages.

• Endpointhttps://mcp.uptimeglobe.com
• TransportStreamable HTTP · JSON-RPC 2.0 (protocol 2025-06-18)
• AuthAuthorization: Bearer sk_live_… (a scoped API key)
• PlanAvailable on any paid plan

Connect your client

Two ways to authenticate: one-click OAuth (sign in + approve in your browser — best for desktop/web clients), or a scoped API key as a Bearer header (best for CLI/headless). Both require a paid plan.

One-click OAuth (claude.ai, Claude Desktop, OAuth-capable clients)

Add a custom connector pointing at https://mcp.uptimeglobe.com — leave the auth blank. The client discovers the authorization server, registers itself, and opens a browser where you sign in to Uptime Globe and approve the requested permissions. No key to copy or paste. OAuth connections act as you, so they can do real-user actions like acknowledge_incident that API keys can’t.

Claude Code (CLI) — with a scoped key

claude mcp add --transport http uptimeglobe https://mcp.uptimeglobe.com --header "Authorization: Bearer sk_live_YOUR_KEY"

Cursor & other HTTP MCP clients

Point any Streamable-HTTP MCP client at the endpoint with a Bearer header. The exact config shape varies by client; a common form is:

{
  "mcpServers": {
    "uptimeglobe": {
      "url": "https://mcp.uptimeglobe.com",
      "headers": { "Authorization": "Bearer sk_live_YOUR_KEY" }
    }
  }
}

stdio-only clients (mcp-remote bridge)

If your client only speaks stdio, bridge it to the remote server with mcp-remote:

npx mcp-remote https://mcp.uptimeglobe.com --header "Authorization: Bearer sk_live_YOUR_KEY"

Authentication & scopes

OAuth (OAuth 2.1 + PKCE) is the one-click path: the client registers dynamically, you sign in and consent in the browser, and a short-lived token (auto-refreshed) is issued bound to your user + workspace. You grant scopes on the consent screen, capped by your role. OAuth connections can perform real-user actions (e.g. acknowledging an incident) that API keys cannot.

Or authenticate with a scoped API key. Create one in the dashboard under Settings → API keys, choose exactly the permissions the agent needs, and pass it as a Bearer token. The key is shown only once at creation — copy it immediately; it can't be retrieved later (only revoked). Each key belongs to one tenant (workspace).

MCP access requires a paid plan. A free-plan key authenticates but is rejected at the MCP server with plan_upgrade_required.

Scopes are per-resource × {read, write} across the six resources below. Billing, members, and API-key management are never grantable to a key. A read-only key cannot even see the write tools; the API re-checks every call. Secret fields (Slack tokens, webhooks, …) are always redacted to *** on read.

Tool reference

40 tools total. Each tools/call is forwarded to the Uptime Globe API and enforced against the key's scopes; a key only ever sees the tools its scopes allow.

Monitors (3 read / 6 write)

Incidents (2 read / 6 write)

Channels (2 read / 3 write)

Notification rules (2 read / 3 write)

Maintenance windows (2 read / 3 write)

Status pages (3 read / 5 write)