# incident.io MCP connector The incident.io connector brings incidents, alerts, follow-up actions, on-call cover requests, and your service catalog to Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person can ask about and update live incidents inside their own incident.io access. Source: https://elaichi.ai/connectors/incident-io/ ## Facts | | | | --- | --- | | Application | incident.io | | Category | Incident Management | | AI tools | 91 | | Authentication | Connects over OAuth | | Bring your own OAuth app | No | | Native MCP | Yes. incident.io builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top | | Support for its tools | help@incident.io | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once incident.io is connected - Which alerts fired overnight and which are still unresolved? - List the open actions on the checkout latency incident. - Show pending cover requests for this weekend's on-call shifts. ## Connect incident.io in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick incident.io. 2. Optionally set Share with, then press Connect. 3. Approve it in incident.io. incident.io's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which incident.io tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## incident.io MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## incident.io MCP connector for ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## incident.io MCP connector for Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect incident.io to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a incident.io tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with incident.io through Elaichi ### Catch up on an incident fast Engineering. Ask what an incident.io incident is about, what has happened so far, and what is still open, without scrolling the whole timeline. The answer comes from the live record, not from memory. ### Triage overnight alerts in one pass Platform. List the alerts that fired overnight, see which sources they came from, attach the related ones to an existing incident, and resolve the noise. Spin up a new incident from an alert when it turns out to be real. ### Keep follow-up actions honest Engineering. Create the actions agreed on the call, update them as work lands, and list what is still unassigned before the review meeting. ### Give customers a straight answer Support. Ask whether a customer-facing service has an open incident right now and what the current status says, so the reply to the customer matches what engineering actually knows. ### Sort out cover for the weekend On-call. Raise a cover request when you cannot take a shift, see who else has asked, and approve or decline requests from your team without opening the schedule. ### See alert trends before the review Leadership. Pull alert statistics for the quarter, break them down by tag or source, and ask the telemetry questions you want answered before the operational review starts. ## Elaichi vs Zapier MCP vs Composio for incident.io All three can connect incident.io to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay. | What to check | Elaichi | Zapier MCP | Composio | | --- | --- | --- | --- | | Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. | | Control over incident.io tools | Allow or restrict single incident.io tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. | | Record of calls | One audit entry per incident.io call. | A History tab of tool calls. | A log of every tool call. | | Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. | | Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. | Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## Frequently asked questions ### How do I connect incident.io to Claude? Connect incident.io in Elaichi first: pick it from the catalog, and incident.io shows its own approval screen asking you to allow access to your account, since it connects over OAuth. There is no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and incident.io is ready in Claude. ### Does incident.io work with ChatGPT and Cursor as well as Claude? Yes. Once incident.io is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect incident.io once and every client picks it up. ### What can an AI agent actually do with my incident.io data? With incident.io connected, an agent can tell you what an incident is about and what is still open, list and resolve alerts, attach alerts to incidents or open a new incident from one, and create or update follow-up actions. It can also look up services in your catalog, handle on-call cover requests, and pull alert statistics. Short, concrete asks such as "list unresolved alerts from the payments source" work better than long paragraphs. ### Does connecting incident.io give the AI access to every incident and alert? No. Every call to incident.io runs as the person who signed in, so the agent sees only the incidents, alerts, and catalog entries that person can already see in incident.io. Elaichi can narrow that further for a team, for example read-only on incidents, but it can never widen it beyond what incident.io itself allows that person. ### Can my team share one incident.io connection? Yes. One person connects incident.io in Elaichi and shares the connection with a team, and nobody else on the team ever handles a token or a login. Each person still signs in to Elaichi as themselves, so the audit log records who resolved an alert or updated an action, not just that the shared connection did. ### Can I stop an agent from deleting or changing things in incident.io? Yes. Restrictions in Elaichi apply per action, so you can allow reading incidents and alerts while blocking deleting actions or resolving alerts for a given team. A restricted action is never advertised to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it in incident.io. ### What happens to an incident.io connection when someone leaves? Offboarding a person in Elaichi ends their access to incident.io through every client at once, including Claude, ChatGPT, and Cursor. A connection they shared keeps working for everyone else on the team. If you want to remove incident.io entirely, disconnecting it once in Elaichi removes it from every client. ### Does the incident.io MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. incident.io is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs. ### Is Elaichi an alternative to Zapier MCP for incident.io? Yes. Both let Claude, ChatGPT or Cursor use incident.io. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every incident.io call. ### How is Elaichi different from Composio for incident.io? Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to incident.io: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call. ## All 91 incident.io tools Every tool below is callable through https://api.elaichi.ai/mcp once incident.io is connected, subject to the toolbox it is in and the restrictions on the caller. - **Action create** (Create). Create an action on an incident - **Action delete** (Delete). Delete an incident action - **Action list** (List). List incident actions - **Action update** (Update). Update an existing action - **Alert attach** (Action). Attach an existing alert to an incident - **Alert create incident** (Create). Declare an incident from one or more alerts - **Alert detach** (Action). Detach an alert from an incident - **Alert list** (List). Search and browse alerts - **Alert resolve** (Action). Resolve one or more firing alerts - **Alert show** (Action). Full alert details with linked incidents - **Alert source list** (List). List configured alert sources - **Alert stats** (Action). Alert counts with workload from linked incidents - **Alert tag apply** (Action). Add, remove, or replace tags on up to 50 alerts - **Alert tag list** (List). List the alert tags available to apply - **Analysis start** (Start). Start a structured operational analysis with playbooks and report template - **Ask** (Action). AI agent for on-call queries, schedule management, and general questions - **Ask incident** (Action). AI agent for incident investigation and management actions - **Ask telemetry** (Action). AI agent for querying logs, metrics, traces, and dashboards - **Catalog entry list** (List). Browse entries in a catalog type - **Catalog entry show** (Action). Full catalog entry with all attributes - **Catalog type list** (List). List catalog types (Service, Team, etc.) - **Cover request create** (Create). Ask for volunteers to cover a shift - **Cover request list** (List). List cover requests and how candidates responded - **Cover request manage** (Action). Cancel a cover request, accept an offer, or remind candidates - **Cover request respond** (Action). Respond to a cover request you're a candidate on - **Custom field values** (Action). Look up the values a custom field accepts - **Document search** (Search). Search your synced runbooks, guides, and post-mortems - **Document show** (Action). Read a synced document's full content - **Duration metrics stats** (Action). Time to acknowledge, time to resolve, and other duration metrics with percentiles - **Escalation create** (Create). Page a user or an escalation path - **Escalation list** (List). Search escalations (pages) - **Escalation path list** (List). List escalation paths - **Escalation path show** (Action). Who would be paged at each level - **Escalation respond** (Action). Acknowledge or decline a page - **Escalation show** (Action). Full escalation details with transition history - **Escalation stats** (Action). Paging counts by path, priority, time of day - **Extension connector list** (List). List connectors with their capabilities and connection health - **Extension plugin create** (Create). Load a plugin from a source-control repository - **Extension plugin list** (List). List plugins with their skills and sync state - **Extension plugin sync** (Sync). Re-sync a plugin from its source repository - **Extension plugin update** (Update). Enable, disable, rename, or change which skills agents load - **Extension skill feedback list** (List). Current feedback on a plugin's skills - **Extension skill feedback update** (Update). Dismiss or reopen a skill feedback issue - **Extension skill usage list** (List). List assessed skill loads, with the run behind each one - **Extension upload URL** (Upload). Get a URL to upload content that isn't in a readable repository - **Extension verify** (Verify). Test proposed extension content before landing it - **Extension verify show** (Verify). Show a verification's status and result - **External service list** (List). List the third-party services whose status pages we monitor - **External service status** (Action). Check a monitored vendor's current status and recent changes - **Feedback** (Action). Submit feedback about the tools - ...and 41 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.