Skip to content

FireHydrant MCP connector

The FireHydrant connector lets Claude, ChatGPT, Cursor 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.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect FireHydrant to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect FireHydrant once

  1. Open Connections, choose Add connection, and pick FireHydrant.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a FireHydrant API key. One person generates a token in FireHydrant and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

firehydrant
FireHydrant
Better Stack
Chronosphere
Freshservice
Freshstatus
incident.io
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

FireHydrant MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

FireHydrant MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Connect FireHydrant to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

Use cases

What teams do with FireHydrant through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • 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.”

See all 438 FireHydrant tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for FireHydrant, by what to check
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 $15 per user per month. 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.

AI tools

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.

Showing 262 of 438 FireHydrant tools here. Connect FireHydrant and call search_tools or tools/list over the MCP endpoint for the complete set.

See it in Elaichi

What connecting FireHydrant gets you

6 screens from the product, each doing one job for your FireHydrant account.

The agent

Ask about incidents, read the answer.

Plain language questions return live FireHydrant incidents, change events and services.

  • incidents
  • change events
  • services
  • entitlements

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 or Cursor

MCP clients

Claude, ChatGPT and Cursor reach FireHydrant.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

438 FireHydrant tools ready to call.

Incidents, change events and entitlements are covered without a line of custom code.

  • Create a FireHydrant change event
  • Delete a FireHydrant change event by ID
  • Get single FireHydrant change event by ID
  • List all FireHydrant change events
ElaichiTools
Tool Action Description
Create a FireHydrant change event Create Create a new change event in FireHydrant to record a system change such as a deployment or configuration update. Returns the created event including id, summary, starts_at, ends_at, environments, services, labels, and identities. Required: summary.
Delete a FireHydrant change event by ID Delete Delete a FireHydrant change event by id. Returns an empty 204 response on success.
Get single FireHydrant change event by ID Get Get a single FireHydrant change event by id. Returns the full event object including id, summary, description, starts_at, ends_at, environments, services, labels, identities, authors, attachments, and related_changes. Required: id.
List all FireHydrant change events List List change events for the FireHydrant organization. Returns: id, summary, starts_at, ends_at, environments, services, labels, identities. Note: attachments and related_changes are not included in list responses — fetch an individual event by id for complete detail.
Update a FireHydrant change event by ID Update Update an existing FireHydrant change event by id. Returns the updated event including id, summary, description, starts_at, ends_at, environments, services, labels, and identities. Required: id.

Toolboxes

Every team gets its own toolbox.

On call, engineering and support each see a FireHydrant toolbox scoped to them.

  • On call
  • Platform engineering
  • Support
  • SRE
ElaichiToolboxes
Name Source template Tools Created

On call toolbox

FireHydrant · active incidents and escalations

FireHydrant starter 18 Mar 4, 2026

Platform engineering toolbox

FireHydrant · services and change events

— 9 Mar 2, 2026

Support toolbox

FireHydrant · customer facing incident updates

— 24 Feb 27, 2026

SRE toolbox

FireHydrant · postmortems and reliability metrics

FireHydrant starter 6 Feb 19, 2026

Release engineering toolbox

FireHydrant · change events and deploys

— 31 Jan 30, 2026

Leadership toolbox

FireHydrant · incident trends and entitlements

— 12 Jan 22, 2026

Shared connections

Teammates run incidents without a credential.

Each FireHydrant connection shows who added it and which teams and members share it.

  • Production
  • On call EMEA
  • Support
  • Platform
ElaichiConnections
Connection Scope Status Access
FI

FireHydrant (Production)

Connected by Emily Carter

Personal • Active 1 team · 6 members
FI

FireHydrant (On call EMEA)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
FI

FireHydrant (Support)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
FI

FireHydrant (Platform)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
FI

FireHydrant (Staging)

Connected by Ryan Hayes

Personal • Active Not shared
FI

FireHydrant (Security)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every incident call has a name on it.

When, who, what happened, type and resource for each FireHydrant request.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

FireHydrant Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

FireHydrant Incidents Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

FireHydrant Incidents List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, a digest ships.

Six steps fetch FireHydrant incidents, group them, draft a digest, await approval, post back.

FireHydrant digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch incidents

    FireHydrant

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    FireHydrant

    Queued

Collections and dashboards

Incident health arrives before anyone asks.

Four metrics, 14 days of incidents created and a team breakdown, computed on schedule.

FireHydrant health

Refreshed 4 minutes ago · every 15 minutes · from the incidents collection

Live

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%

FAQ

Frequently asked questions

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, 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 my team share one FireHydrant connection?

Yes. One person connects FireHydrant in Elaichi and shares the connection with a team, and nobody else on that team ever sees or handles the FireHydrant API key. Each teammate still signs in to Elaichi as themselves, so every incident opened or updated through the shared FireHydrant connection is logged under the name of the person who did it.

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 blocking deleting incidents, removing change events or editing alerts. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt, accidental or otherwise, can reach it.

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 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor 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.