Connect Claude Code
Prerequisites
Section titled “Prerequisites”- Claude Code installed (current stable)
- A UptimeMonitoring account (sign in with GitHub at app.uptimemonitoring.com)
- (Only for the API-key alternative below) an
umk_live_key — see Authentication
Connect
Section titled “Connect”Add the UptimeMonitoring remote HTTP MCP server:
claude mcp add --transport http uptimemonitoring https://api.uptimemonitoring.com/mcpThen in Claude Code run /mcp — Claude Code opens your browser to authorize via GitHub and stores the access token automatically. No key to manage or paste.
Alternative: API key (CI / headless / automation)
Section titled “Alternative: API key (CI / headless / automation)”Use this in non-interactive environments where a browser OAuth flow isn’t possible. The same umk_live_ key also powers the REST API and the assert-healthy GitHub Action.
claude mcp add --transport http uptimemonitoring https://api.uptimemonitoring.com/mcp \ --header "Authorization: Bearer umk_live_..."Replace umk_live_... with your actual API key.
Verify
Section titled “Verify”In Claude Code, type /mcp and confirm uptimemonitoring appears with status connected. Then ask:
list my monitors
You should see a tool call to list_monitors and a list of your monitors (or an empty result if you don’t have any yet).
Common errors
Section titled “Common errors”| Symptom | Cause | Fix |
|---|---|---|
401 Unauthorized (API-key method) | Key is wrong, missing, or not umk_live_-prefixed | Confirm the key from Authentication starts with umk_live_ and is pasted in full |
| Browser didn’t open / auth didn’t finish | OAuth flow was interrupted | Re-run /mcp in Claude Code; it re-initiates the OAuth flow |
Tools missing after /mcp | MCP server registered but Claude Code hasn’t reloaded | Restart Claude Code fully |
| Connection refused / DNS error | Wrong host in the server URL | The endpoint is https://api.uptimemonitoring.com/mcp, not the marketing host |