FireHydrant MCP connector
The FireHydrant connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and other MCP clients open, update and list FireHydrant incidents, alerts and change events, with each person working inside their own FireHydrant access and every action recorded.
- Connects with an API key
- Free 14-day trial
- No credit card
List all open FireHydrant incidents from the last seven days.
Working in FireHydrant with Elaichi
-
Get single FireHydrant change event by ID
-
List all FireHydrant change events
-
Get single FireHydrant incident by ID
How to connect FireHydrant to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
FireHydrant MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
FireHydrant MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
FireHydrant MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
FireHydrant MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
FireHydrant MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect FireHydrant to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with FireHydrant through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in FireHydrant is logged.
-
On-call engineering
Open an incident from a paging alert
When an alert fires, ask the agent to open a FireHydrant incident with the right title and severity instead of filling in the form under pressure. It can also tie the triggering alert to the new incident.
-
Incident command
Catch the incident up during the bridge
While the call is running, tell the agent what changed and it updates the FireHydrant incident with the new status, severity or summary. Nobody has to break away from the conversation to type it in.
-
Platform and SRE
Log a deploy as a change event
After a rollout, ask the agent to record a FireHydrant change event with what shipped and when, so the timeline is there when something breaks an hour later.
-
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.
-
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.
-
Release management
Line up changes against a failure
Ask which FireHydrant change events landed in the two hours before an incident opened, so the team can rule causes in or out quickly.
Try asking
- “List all open FireHydrant incidents from the last seven days.”
- “Which services had the most change events this month?”
- “Summarize yesterday's FireHydrant incidents by severity and owning team.”
What connecting FireHydrant gets you
6 screens from Elaichi, each doing one job for your FireHydrant account.
Ask Elaichi to work across your apps.
List all open FireHydrant incidents from the last seven days.
Which services had the most change events this month?
Summarize yesterday's FireHydrant incidents by severity and owning team.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about incidents, read the answer.
Plain language questions return live FireHydrant incidents, change events and services.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach FireHydrant.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
438 FireHydrant tools ready to call.
Incidents, change events and entitlements are covered without a line of custom code.
Toolboxes
Every team gets its own toolbox.
On call, engineering and support each see a FireHydrant toolbox scoped to them.
Shared connections
Teammates run incidents without a credential.
Each FireHydrant connection shows who added it and which teams and members share it.
Audit log
Every incident call has a name on it.
When, who, what happened, type and resource for each FireHydrant request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
FireHydrant digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch incidents
FireHydrant
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
FireHydrant
Queued
Automations
A schedule fires, a digest ships.
Six steps fetch FireHydrant incidents, group them, draft a digest, await approval, post back.
FireHydrant health
Refreshed 4 minutes ago · every 15 minutes · from the incidents collection
Incidents
1,284 ↓ 12%
Change events
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Incidents created
Last 14 days
By team
Share of activity
Production 34%
On call EMEA 27%
Support 21%
Platform 18%
Collections and dashboards
Incident health arrives before anyone asks.
Four metrics, 14 days of incidents created and a team breakdown, computed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for FireHydrant
All three can connect FireHydrant 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over FireHydrant tools | Allow or restrict single FireHydrant 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 FireHydrant 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 | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
FireHydrant tools for your AI agents
438 tools are ready to call through Elaichi's MCP endpoint the moment you connect FireHydrant, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 262 of 438 FireHydrant tools here. Connect FireHydrant and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect FireHydrant to Claude?
Connecting FireHydrant to Claude takes two steps. First, connect FireHydrant in Elaichi by pasting a FireHydrant API key when asked; there is no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and FireHydrant incidents, alerts and change events are available in your conversation.
Does FireHydrant work with ChatGPT and Cursor as well as Claude?
Yes. Once FireHydrant is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect FireHydrant once and every client you use gets it.
What can an AI agent actually do with my FireHydrant data?
With FireHydrant connected, an agent can open a new incident, update its severity, status or summary, and pull up any incident by name or list the ones currently open. It can record change events such as deploys and configuration changes, look up alerts and attach them to incidents, and read the processing log when you want to know how a signal was handled. Short, specific asks such as "open a sev2 for the checkout API" work better than long paragraphs, because the agent searches for the right FireHydrant action based on what you ask.
Does connecting FireHydrant give the AI access to every incident in my organization?
No. When you connect FireHydrant through Elaichi, the agent works with the access of the API key you provided and the person who signed in, so it sees the FireHydrant incidents, alerts and change events that person can already see and nothing more. Elaichi can narrow that access further, for example to reading only, but it can never widen it beyond what FireHydrant itself allows.
Can I stop an agent from deleting or changing incidents in FireHydrant?
Yes. Restrictions in Elaichi apply per action, so you can allow reading FireHydrant incidents and alerts while restricting deleting incidents, removing change events or editing alerts. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a FireHydrant connection when someone leaves?
When you offboard a person in Elaichi, their access to FireHydrant through every connected client ends at once. If they connected FireHydrant and shared it with a team, the shared connection keeps working for everyone else. Disconnecting FireHydrant once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the FireHydrant MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. FireHydrant 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, Microsoft Copilot, 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 FireHydrant?
Yes. Both let Claude, ChatGPT or Cursor use FireHydrant. 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 FireHydrant call.
How is Elaichi different from Composio for FireHydrant?
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 FireHydrant: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put FireHydrant in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot