Vanta's official remote MCP server — query controls, tests, vendors, vulnerabilities and policies across SOC 2 and ISO 27001, and remediate failing tests from your agent.
incident.ioMCP Server
by incident.io
Released
Summary
incident.io's official hosted MCP server — reach incidents, alerts, on-call schedules, the catalog and workflows from Claude, Cursor or any MCP client over OAuth.
Features
- Hosted at https://mcp.incident.io/mcp — no local setup, no repo to clone
- User OAuth inherits your own permissions; API keys for unattended internal tools
- Read incidents, alerts, on-call schedules, the catalog and workflows
- Tools that call incident.io's own Agent, exposing its intelligence layer over MCP
- Works with Claude Desktop, Claude Code, Cursor and MCP proxies such as Cloudflare's
- AI SRE (private beta) can run production investigations against live telemetry
Installation
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Description
incident.io runs the whole lifecycle of an outage: declaring the incident, paging the right on-call engineer, keeping the timeline, and turning the aftermath into follow-ups. Its official MCP server makes that history and that live state available to an agent, so questions that normally mean clicking through a dashboard — "how many database incidents did we have last quarter?", "who is on call for payments tonight?", "draft my handover from this week's incidents" — get answered against the real record.
Hosted, with nothing to install. The server lives at https://mcp.incident.io/mcp. There is no repository to clone and no process to keep running: point a client at the URL and authenticate. In Claude Code that is claude mcp add incident-io --transport http https://mcp.incident.io/mcp, which prompts for browser authorisation on first use; Codex and other clients take the same URL in their own config format.
Two ways to authenticate. User-based OAuth is the default and the right choice for a human at an editor — the agent inherits exactly your permissions, no more. An API key is the alternative when something internal and unattended needs to connect. Setup happens in incident.io's own Settings and takes under a minute.
What it exposes. Incidents, alerts, on-call schedules, the catalog and workflows, plus tools that talk to incident.io's own Agent — so the intelligence layer the product already runs is reachable over MCP rather than being locked to the UI. Customers in the AI SRE private beta can additionally have it run production investigations against live telemetry and logs.
The server entered public beta on 31 March 2026 and is available to all paying customers. It works with Claude Desktop, Claude Code, Cursor and any MCP-compatible client, including proxies such as Cloudflare's.
Related MCP Servers
Attio's official hosted MCP server — search, read and write your CRM records, lists, notes, tasks, meetings and emails from any MCP client over OAuth.
Fireflies.ai's official remote MCP server — 19 tools for searching meeting transcripts and summaries, pulling action items and analytics, and cutting soundbites from recorded calls.
4 views
ClickUp's official remote MCP server — around 40 tools across tasks, search, Docs, Chat and time tracking, over OAuth 2.1 with PKCE.
2 views