Skip to content
upcertain

Docs

Use Upcertain in Cursor

Cursor's agent can read your monitors and incidents through Upcertain's MCP server, so production health is one question away while you edit.

Updated 25 October 2026 · By the Upcertain team

Sign in (recommended)

Add this to ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one project:

{
  "mcpServers": {
    "upcertain": { "url": "https://upcertain.com/api/mcp" }
  }
}

Open Cursor's MCP settings and choose Connect next to upcertain. 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

{
  "mcpServers": {
    "upcertain": {
      "url": "https://upcertain.com/api/mcp",
      "headers": { "Authorization": "Bearer <your API key>" }
    }
  }
}

Owners and admins create keys under Settings, API & MCP. Do not commit a project mcp.json that contains a key.

Also works in VS Code

code --add-mcp '{"name":"upcertain","type":"http","url":"https://upcertain.com/api/mcp"}'

Things to ask in the editor

  • "Is the endpoint this file serves monitored? If not, add a monitor for it." (read-write)
  • "Show the last three incidents on the checkout API and their causes."
  • "Which monitors have the lowest 7-day uptime?"

Troubleshooting

  • 401 or a sign-in loop: remove the server, add it again and reconnect. Check that the connection was not removed under Connected apps.
  • Write tools refused: a read-only connection or key lists every tool but refuses the ones that make changes. Reconnect with read-write if your role allows it.
  • Too many requests: tool calls share the API's limit of 60 a minute per key or connected app.

Related