incident.io Remote MCP Server MCP server

incident.io's officially supported remote MCP server exposes incidents, alerts, on-call schedules, escalations, follow-ups, catalog, status page drafts, AI investigations, synced runbooks, and cross-platform telemetry queries as MCP tools. Interactive use authenticates via OAuth (PKCE public client); automated systems can use a Bearer API key instead.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by incident.io

MCP endpoint (Streamable HTTP)

https://mcp.incident.io/mcp

Vendor documentation

What you can do with it

Query incident history and aggregate stats by severity or team.
Check who is on call and manage schedule overrides.
Acknowledge or decline pages and create escalations.
Create, update, and merge incidents with follow-ups.
Query logs, metrics, and traces across connected observability platforms.

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add incident-io --url https://mcp.incident.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable incident-io in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "incident-io": {
      "url": "https://mcp.incident.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "incident-io": {
      "type": "streamableHttp",
      "url": "https://mcp.incident.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start incident-io and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "incident-io": {
      "url": "https://mcp.incident.io/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "incident-io": {
      "serverUrl": "https://mcp.incident.io/mcp"
    }
  }
}

See all 957

Do you run incident.io Remote MCP Server?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing