Skip to content
upcertain

Docs

Use Upcertain from Claude Code

Claude Code can check whether the service you are changing is healthy, look up the incident from last night, or add monitors for an endpoint you just shipped.

Updated 25 October 2026 · By the Upcertain team

Add the server

claude mcp add --transport http upcertain https://upcertain.com/api/mcp

Then start Claude Code, run /mcp, select upcertain and choose Authenticate. Your browser opens Upcertain, where you pick the workspace and read-only or read-write access. Your account needs the Team or Business plan.

With an API key

For scripts, CI or a machine without a browser, an owner or admin creates an API key under Settings, API & MCP and you pass it as a header:

claude mcp add --transport http upcertain https://upcertain.com/api/mcp --header "Authorization: Bearer <your API key>"

Keep the key out of version control. A read-only key cannot change monitors or incidents.

Useful while coding

  • "Before I deploy, are any monitors for the API down or flapping today?"
  • "What caused last night's incident on auth-service, and how long did it last?"
  • "I just added /v2/health. Create an HTTP monitor for it every minute, expecting 200." (read-write)
  • "Pause the monitor for the staging site while I migrate it." (read-write)

Tools available

Read tools: list_monitors, get_monitor, get_uptime, list_incidents, get_incident, list_status_pages. Read-write tools: create_monitor, pause_monitor, resume_monitor, acknowledge_incident. Arguments and limits are on the MCP server page.

Scope

Add the server with --scope user to use it in every project, or leave the default to keep it in the current project only. Remove it with claude mcp remove upcertain, and disconnect the sign-in under Settings, API & MCP, Connected apps.

Related