Skip to content
Incident IO logo

Incident IO MCP server

Which MCP servers are Incident IO's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-08

← Back to Incident IO

Whose server it is
  • Addresshttps://mcp.incident.io/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on incident.io when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

When we asked itchecked 2026-10-26
  • Staterequires sign-inchecked 2026-10-26

On 2026-10-26 the server answered and asked for a sign-in with a Incident IO account (OAuth). It shows its tool list only to signed-in users, so we list none here.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "incident": {
      "type": "http",
      "url": "https://mcp.incident.io/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http incident https://mcp.incident.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.incident.io/mcp as a custom connector in the settings.

The first time it connects, the client opens a Incident IO sign-in.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.