Official remote incident.io MCP server. Lets AI agents query incidents, alerts and on-call schedules and manage escalations after you sign in with OAuth or an API key.
Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://mcp.incident.io/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http incident.io-mcp https://mcp.incident.io/mcpRun in a terminal.
{ "mcpServers": { "incident.io-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.incident.io/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchThis server asks you to sign in when you connect. Your agent handles that.
From the publisher
README is not crawled yet. No repository on file.
Official remote incident.io MCP server. Lets AI agents query incidents, alerts and on-call schedules and manage escalations after you sign in with OAuth or an API key.
{ "mcpServers": { "incident.io-mcp": { "url": "https://mcp.incident.io/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Incident.io MCP is reached over HTTP.
Last checked 2026-11-18. Official remote incident.io MCP server. Lets AI agents query incidents, alerts and on-call schedules and manage escalations after you sign in with OAuth or an API key.