Skip to main content

for claude.ai, claude code and claude desktop

Connect Claude to your uptime monitoring

Claude is the client this server was built against first. In claude.ai and Claude Desktop the connector is one click and a consent screen. In Claude Code it is one command and a sign-in. Connected that way, Claude sees all 31 tools, and every one that changes something stops and asks you before it runs. A plan without connectors still gets the read tools through mcp-remote and a scoped token.

Start free

claude.ai: one click

Open Settings, then Connectors, then Add custom connector, and paste https://mcp.uptimepage.dev/mcp. Claude discovers the server, registers itself, and sends you to the Uptimepage login you already have. The consent screen names the organization the connection will be bound to, lists every ability being granted in plain words, and shows where you go after Approve: claude.ai. Pick how long the connection lives (30 to 365 days, no never) and approve. Tools appear in the chat with nothing to paste.

Claude Code: one command

Run claude mcp add --transport http uptimepage https://mcp.uptimepage.dev/mcp, then type /mcp inside a session and choose the server to sign in. The browser opens on the same consent screen, and the connection comes back to the terminal on a loopback port. From then on the tools are available in every session in that scope, and a write shows its confirmation prompt right there in the terminal, with the check result for a monitor about to be created.

Claude Desktop: Connectors, or mcp-remote

On a plan with connectors, Claude Desktop has the same Settings, Connectors entry as claude.ai: add the URL there and sign in through the same consent screen. Without it, bridge the endpoint with mcp-remote and a token you mint in the app under Settings, then API tokens: org-bound, expiring, and read-only. targets:read, status_page:read and incidents:read cover 14 of the 16 read tools; the channel inventory and variable keys need channels:read and variables:read. Leave write scopes off a token that lives in a config file on a shared machine; the OAuth path is where writes belong, because each one is confirmed in the moment.

What Claude can do once connected

Claude negotiates elicitation at connect time, so the server lists all 31 tools: 16 that read and 15 that act. Ask what is down and Claude calls get_org_health, then get_monitor_history for the one that matters, and reads the DNS, connect, TLS and first-byte timings apart. Ask it to cover a new service and it proposes the monitors, runs each check once, and shows you the result inside the confirmation before anything is saved. There is no remember-my-choice: every write is its own approval.

Three prompts to start with

"Is anything down right now, and since when?" pulls the org health and the worst failing monitors with their open incidents. "Why was the checkout flow failing at 3am?" reads the browser flow runs step by step and names the step it stopped on. "Watch api.example.com, its certificate and its domain, and alert the on-call Slack channel" creates three monitors behind one confirmation and binds the channel you already made by name.

Which organization Claude sees

A connection is bound to one organization, fixed at the moment you approve, from whichever org was active in the app. The consent screen names it. To connect a different org, switch to it in the app first, then reconnect; get_org_usage tells Claude which one it is bound to, which is the quickest answer to why a monitor seems missing. The connection sees only that org, whatever else you belong to.

Claude Desktop config (claude_desktop_config.json)

{
  "mcpServers": {
    "uptimepage": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.uptimepage.dev/mcp",
        "--header", "Authorization: Bearer sm_live_YOUR_TOKEN"
      ]
    }
  }
}

FAQ

Does the claude.ai connector need an API token?
No. Add the server URL under Settings, Connectors, in claude.ai or Claude Desktop, and Claude registers itself, sends you to the Uptimepage login you already have, and mints an org-bound token behind the consent screen. A token is only for a plan without connectors, where Claude Desktop reaches the server through mcp-remote.
Can Claude change my monitors?
Only if two things are true: the connection was granted a write scope on the consent screen, and you approve that specific action when Claude proposes it. Claude shows the confirmation, including the trial check result for a monitor about to be created. Read scopes alone let it answer questions and nothing more.
Which organization does the connection see?
The one that was active in the app when you approved. The consent screen names it, and get_org_usage repeats it later. To connect another org, switch to it in the app first and add the connector again.
How long does the connection last?
As long as you chose on the consent screen: 30, 60, 90 or 365 days, default 90. There is no never. The access token itself is short-lived and refreshes on its own inside that window.

At a glance

  • Server URL https://mcp.uptimepage.dev/mcp
  • claude.ai Settings, Connectors, add custom connector
  • Claude Code claude mcp add --transport http
  • Claude Desktop Connectors, or mcp-remote with a token
  • Sign-in OAuth consent, your existing login
  • Confirmations shown, so all 31 tools are offered
  • OAuth connection lifetime 30 to 365 days, your pick
  • Price to start free, no card

Links

Start in under 5 minutes.

Start free

features · pricing · notes