Who it is for
SRE and on-call teams running incident response through incident.io.
AI Connectors · Developer Tools
incident.io
Incident declaration, on-call schedules, and response analytics
Overview
What incident.io does
incident.io handles incident response: declaring and triaging incidents, paging, on-call rotations, follow-up tracking, and a service catalogue underneath it. The connector's stated reach covers the whole workspace, both the operational side during an incident and the review side afterwards.
The description names trend analysis across incidents, escalation response rates, and alert noise, plus telemetry queries against connected observability tools and structured operational reviews. Thirty-five tools are published, one of the larger surfaces in this category, which fits a product with several distinct object types. Connection requires an incident.io workspace, since the endpoint answers nothing without one.
Tool surface
The server returns 401 rather than a tool list, so the thirty-five published tools cannot be sorted into the paging and acknowledgement actions on one side and the analytics reads on the other.
Availability
Where incident.io is listed
incident.io is listed in the Claude connectors directory only. incident.io has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them.
The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one.
Claude listing
In the Claude connectors directory
incident.io publishes 35 tools to Claude, deeper than 84.6% of the 1,253 Claude-listed connectors.
The median Claude-listed connector filed under Developer Tools publishes 13, so this one runs 22 tools above its bucket's median and ranks 17th of 95 by tool count.
It falls in the 21-50 tools band, which holds 20% of the Claude directory.
incident.io publishes a remote MCP endpoint. Claude connects to it over HTTP; there is nothing to install locally.
Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there.
- Publisher
- incident.io
- Verification
- Verified partner (37.8% of the Claude directory)
- Filed under
- Developer Tools
- Endpoint
-
https://mcp.incident.io/mcp - Documentation
- Publisher setup docs
- Published tools
- 35 · 21-50 tools band
- Depth rank in Developer Tools
- 17 of 95
- Snapshot
- August 2026
incident.io carries partner verification in the Claude directory, which 474 of 1,253 listings do (37.8%). That is a review step past self-publishing, not an Anthropic-built server.
In the publisher's words
How incident.io describes it
Manage your full incident.io workspace from one place. Declare and triage incidents, ack pages, check who's on call, and track follow-ups - without switching tools. Analyze incident trends, escalation response rates, and alert noise across your organization. Browse your catalog, query telemetry from connected observability tools, and run structured operational reviews. Everything your team needs to stay on top of things, without the tab juggling.
Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it.
Nearby
Other Developer Tools connectors
Aiven MCP
Provision and manage Aiven data services
Claude · ChatGPT
Base44
AI app and website building from a description
Claude · ChatGPT
ElevenLabs
Create and configure ElevenLabs voice agents
Claude
Eraser
Diagram and technical document creation inside an Eraser workspace
Claude
Garchi CMS
Manage headless CMS content through an MCP connection
ChatGPT
Harness.io
CI/CD pipelines, feature flags, and cloud cost data in one connector
Claude
This is an independent catalogue entry compiled by Node8 from incident.io's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with incident.io, and inclusion here is not an endorsement.
Want your company reachable inside ChatGPT and Claude?
Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot.