# Incident Management MCP connectors for Claude, ChatGPT and Cursor 5+ Incident Management connectors in the Elaichi catalog, each callable through https://api.elaichi.ai/mcp once connected, under the same roles, restrictions and audit log as the rest of the catalog. Source: https://elaichi.ai/connectors/category/incident-management/ | | | | --- | --- | | Category | Incident Management | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | ## Incident Management connectors - [Better Stack](https://elaichi.ai/connectors/betterstack/) — 96 tools · hosted sign-in - [Chronosphere](https://elaichi.ai/connectors/chronosphere/) — 2 tools · hosted sign-in - [FireHydrant](https://elaichi.ai/connectors/firehydrant/) — 438 tools · hosted sign-in - [Freshservice](https://elaichi.ai/connectors/freshservice/) — 394 tools · hosted sign-in - [Freshstatus](https://elaichi.ai/connectors/freshstatus/) — 38 tools · hosted sign-in - [PagerDuty](https://elaichi.ai/connectors/pagerduty/) — 157 tools · bring your own OAuth app ## What teams do with Incident Management connectors ### Engineering - **Find out who is on call right now** (PagerDuty) — Ask who is on call for a given service or schedule and get the name straight from PagerDuty, including who picks up next, instead of hunting through rotations. - **Set up a monitor for a new service** (Better Stack) — Ask for a monitor on the new checkout URL, checking every minute, and put it in the right monitor group. It is created in Better Stack with the settings you described instead of clicked together by hand. - **Keep the status page current mid-incident** (Freshstatus) — From the incident channel, add a Freshstatus incident update in a few words and the public timeline reflects what the responders actually know right now. ### Support - **Check whether an outage is already open** (FireHydrant) — When customers start reporting problems, ask what active FireHydrant incidents exist right now and what they say, so the support desk answers with the same story engineering is telling. - **Open an incident from a customer report** (PagerDuty) — When a customer reports an outage, describe it in plain words and have an incident created on the right PagerDuty service, with the title and urgency set, without leaving the chat. - **Confirm whether a site is actually down** (Better Stack) — When a customer reports an outage, ask what the monitor for that page shows right now and how its response times have looked over the past hour, then reply with facts instead of a guess. ### IT operations - **Break a major incident into child tickets** (Freshservice) — When the VPN goes down, spin one parent ticket into child tickets for networking, identity and communications, and keep the whole thread linked. - **Answer 'what teams do we have' quickly** (Chronosphere) — Instead of exporting from Chronosphere by hand, ask for the current team list and drop it straight into a runbook, wiki page, or onboarding doc. - **Review every open incident across services** (PagerDuty) — Pull the list of open and acknowledged incidents across all PagerDuty services, grouped by service or urgency, and get a plain-language summary before the morning standup. ### Engineering management - **Summarize last week's incidents and alerts** (FireHydrant) — Ask for every FireHydrant incident from the past seven days, grouped by severity, or which alerts fired most often. The agent lists them from live records rather than a stale export. - **Check a team's details before a reorg** (Chronosphere) — Look up a Chronosphere team by its ID to confirm its name and description before moving people, dashboards, or alert ownership between groups. ## Things to ask once it is connected - "List Better Stack monitors with availability below 99% this week." (Better Stack) - "List every Chronosphere team and its members." (Chronosphere) - "List all open FireHydrant incidents from the last seven days." (FireHydrant) - "Show open Freshservice tickets raised in the last week." (Freshservice) - "List all services currently showing degraded status." (Freshstatus) - "Who is on call this weekend across payments schedules?" (PagerDuty) ## What an agent can call in Incident Management 1125 tools across the category. 5 of these connectors use hosted sign-in with nothing to register first; 1 ask you to bring your own OAuth app. ## Frequently asked questions ### How many Incident Management connectors does Elaichi have? 5+ Incident Management connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp. ### Can Claude, ChatGPT and Cursor all use Incident Management connectors? Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a Incident Management account once makes it reachable from every one of them. ### Do Incident Management connectors work with Gemini, Codex, Claude Code or other MCP clients? Yes. Incident Management connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp. ### Do Incident Management connectors need me to bring my own OAuth app? Most do not. 5 of the Incident Management connectors use Elaichi's hosted sign-in, with nothing to register. The other 1 ask you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start. ### Can I stop an agent from writing to Incident Management tools? Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a Incident Management connector is a matter of allowing the reads and leaving the writes out. ### Whose access does an agent get on a shared Incident Management connection? The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential. ## Related categories - [Ticketing](https://elaichi.ai/connectors/category/ticketing/) - [Helpdesk](https://elaichi.ai/connectors/category/helpdesk/) - [Application Development](https://elaichi.ai/connectors/category/application-development/) [Browse the full connector catalog](https://elaichi.ai/connectors/)