Connectors / Incident Management
Incident Management MCP connectors for Claude, ChatGPT and Cursor
5+ Incident Management connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.
https://api.elaichi.ai/mcp
The same for every user.
-
Their own access. An agent never gets more than the person it acts for.
-
One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.
The connectors
Incident Management connectors in the catalog
Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.
6 connectors
-
Better Stack Hosted sign-in 96 tools
-
Chronosphere Hosted sign-in 2 tools
-
FireHydrant Hosted sign-in 438 tools
-
Freshservice Hosted sign-in 394 tools
-
Freshstatus Hosted sign-in 38 tools
-
PagerDuty Bring your own OAuth app 157 tools
No Incident Management connector by that name
It may sit under another category, or not be in the catalog yet — any documented API can become a connector.
In practice
What teams do with Incident Management connectors
Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.
Engineering
-
Find out who is on call right now
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
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
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
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
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
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
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
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
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
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
Look up a Chronosphere team by its ID to confirm its name and description before moving people, dashboards, or alert ownership between groups.
Once it is connected
Things to ask
Each of these is answered against the access the person asking already has, in the Incident Management account you connected.
-
List Better Stack monitors with availability below 99% this week.
-
List every Chronosphere team and its members.
-
List all open FireHydrant incidents from the last seven days.
-
Show open Freshservice tickets raised in the last week.
-
List all services currently showing degraded status.
-
Who is on call this weekend across payments schedules?
The tools
What an agent can call in Incident Management
- Connectors
- 5+
- Tools
- 1,125
- Hosted sign-in
- 5
in the Incident Management catalog
callable the moment you connect
connect with nothing to register
Of those 1,125 tools, 15% delete something. Restricting an agent to reads is not a promise here, it is 494 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.
- Read 44%
- 494 tools · list, get, search
- Write 34%
- 379 tools · create, update, send
- Delete 15%
- 172 tools · delete, remove, archive
- Other 7%
- 80 tools · vendor-specific verbs
One endpoint
https://api.elaichi.ai/mcp
Every connector above answers here.
Every Incident Management connector, by depth
Tool counts are what the connector exposes today; the split is what those tools do.
Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.
| Connector | Tools | Read · write · delete | Sign-in |
|---|---|---|---|
| FireHydrant | 438 | Hosted | |
| Freshservice | 394 | Hosted | |
| PagerDuty | 157 | Your own app | |
| Better Stack | 96 | Hosted | |
| Freshstatus | 38 | Hosted | |
| Chronosphere | 2 | Hosted |
FAQ
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.
Nearby
Teams that connect Incident Management usually connect these too
Put Incident Management connectors in front of your team
14 days on Gold, no credit card. Connect one and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.