incident.io
Incidents, on-call, follow-ups
About incident.io
incident.io is an incident management platform covering response, on-call, and status pages. Its remote MCP server lets assistants declare and triage incidents, acknowledge pages, check on-call schedules, and track follow-ups across the whole workspace.
Connection details
https://mcp.incident.io/mcp- Transport
- Streamable HTTP
- Authentication
- OAuth
Setup
claude mcp add incident-io --transport http https://mcp.incident.io/mcpFrequently asked questions
What is the incident.io remote MCP server?
The incident.io remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.incident.io/mcp, so AI assistants can connect to it without installing or running anything locally. incident.io is an incident management platform covering response, on-call, and status pages. Its remote MCP server lets assistants declare and triage incidents, acknowledge pages, check on-call schedules, and track follow-ups across the whole workspace.
How do I connect to the incident.io MCP server?
Add the endpoint https://mcp.incident.io/mcp to any MCP-compatible client such as Claude Code, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Does the incident.io MCP server require authentication?
Yes. incident.io uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Which transport does the incident.io MCP server use?
incident.io exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.
.svg)
%20-%20Sarah%20Xu.svg){kind=icon}