FireHydrant MCP Quickstart
Connect an AI assistant to FireHydrant to look up incidents, alerts and teams, and take action on incidents.
FireHydrant's hosted Model Context Protocol (MCP) server lets an AI assistant work with your FireHydrant data. You can ask it to find an incident, read its timeline, see who is on call for a team, or declare an incident and post updates, all from the assistant you already use.
Cloud-hosted vs. the local MCP server
FireHydrant already offers a local, open-source MCP server. This page is about a different one: a fully cloud-hosted MCP server that uses OAuth. You can use either, or both.
| Local MCP server | Cloud-hosted MCP server (this page) | |
|---|---|---|
| Where it runs | On your own machine, installed and run by you | Hosted by FireHydrant. Nothing to install or run |
| Authentication | A FireHydrant API key that you create and store in your client's config | OAuth. You sign in through the browser and approve access |
| Acts as | The API key you configured | You, with your own permissions |
| Tools | Mirrors FireHydrant's API | A curated set of tools built for assistants, with confirmations for high-impact actions |
| Updates | You update the package yourself | FireHydrant updates the server. Nothing to upgrade |
| Availability | Open source and available to use now | Beta, by request |
If you set up the local server before, it keeps working and this one doesn't replace it. To try the hosted one, you only need to add the server URL below to your client.
What you need
- A FireHydrant account in an organization with an active subscription and MCP enabled.
- An MCP client that supports OAuth sign-in (see Connect your client).
Server details
| URL | https://api.firehydrant.io/mcp |
|---|---|
| Transport | Streamable HTTP |
| Authentication | OAuth. You sign in with your normal FireHydrant login in the browser |
| Scopes | public, read |
You don't create or paste an API key. Your client opens a browser window, you sign in and approve access, and you're connected.
Connect your client
Claude Code
claude mcp add --transport http FireHydrant https://api.firehydrant.io/mcpThen run /mcp inside Claude Code, select FireHydrant, and choose Authenticate. Approve access in the browser.
Claude (claude.ai)
Add a custom connector in your connector settings using https://api.firehydrant.io/mcp, then sign in when prompted.
ChatGPT
Add a custom connector using https://api.firehydrant.io/mcp, then sign in when prompted.
Other clients
Only claude.ai and chatgpt.com are currently set up to connect automatically. Other clients may fail at sign-in with an "unknown client" error. We plan to support more clients. If there's one you need, tell us.
Check that it works
Ask your assistant something like:
- "List my active incidents."
- "Show me the latest alerts."
- "Who is on call for the Platform team?"
You should see the assistant call FireHydrant tools and answer with real data from your organization.
For more ideas, with prompts you can copy and paste, see What You Can Do with MCP.
What it can do
Your assistant finds and runs the tools below on its own. You don't call them by name.
Look things up (read-only)
| Tool | What it does |
|---|---|
list_incidents | Lists incidents. Filter by status, severity or a word in the name. |
get_incident | Everything about one incident: status, milestone, severity, type, tags, customer impact, roles, linked tickets and the latest AI summary. |
get_incident_events | Reads an incident's timeline: notes, updates, milestone changes, role assignments, alerts and more. Filter by event type and date range. |
get_incident_transcript | Reads what was said on an incident's meeting bridge, one line per utterance. |
list_alerts | Lists Signals alerts, newest first. Filter by status, a word in the summary, or linked incident. |
get_alert | Everything about one alert, including whether anyone acknowledged it and a timeline of what happened. |
list_users | Finds people by name or email. |
list_teams | Finds teams by name, or the teams a person belongs to. |
get_team | One team's members, who is on call now, the services it owns and its escalation policies. |
list_incident_roles | Lists the incident roles your organization uses, such as Commander or Scribe. |
list_incident_settings | Lists the severities, priorities, incident types and lifecycle milestones available in your organization. |
Take action (changes things)
| Tool | What it does | Who it can affect |
|---|---|---|
create_incident | Declares an incident and runs your incident runbooks. | Runbooks usually open a Slack channel and can page or invite responders. |
edit_incident | Changes an incident's name, summary, description, customer impact, severity, priority, type or tags. | Everyone on the incident sees the change. Renaming also renames the Slack channel, and changing severity, priority or type can start runbooks. |
post_update_to_incident | Posts an update to the timeline and can move the incident to another milestone. | Posted to the incident's Slack channel. Moving to a resolving or closing milestone has downstream effects. |
add_incident_note | Adds an internal note to the incident timeline. | Visible to everyone on the incident and posted to its Slack channel. Never goes to a status page. |
assign_role_to_incident | Assigns a person to a role on an incident. | The person gets a Slack message and is invited to the incident channel. |
create_page | Pages one person. | Sends a real notification to their phone or devices and creates an alert. |
These actions affect real incidents and real people, the same as doing them in the FireHydrant app.
Confirmations
For high-impact actions, the assistant should check with you before it acts. These actions are creating an incident, changing severity, priority or type, moving an incident to a new milestone and assigning a role.
- If your client supports it, FireHydrant shows a confirmation card that says exactly what will happen, with Confirm and Cancel.
- If the card is declined or your client can't show it, the assistant asks you in the chat and only continues if you explicitly say yes.
Review what the assistant says it is about to do before you confirm. Never approve an action you didn't ask for.
Permissions
The assistant can only see and do what your FireHydrant account is allowed to. It acts as you, with your permissions and not broader ones. Anything it does is attributed to you.
Troubleshooting
| Problem | Likely cause |
|---|---|
| "MCP is not enabled for this organization" | MCP isn't turned on for your organization yet. Request access from FireHydrant Support or your account team. |
| 401 or "Unauthorized" | Your sign-in expired or access was revoked. Re-authenticate in your client. |
| "Unknown client" when signing in | Your client isn't on the supported list yet. See Other clients. |
| Can read but can't make changes | Accounts without an active subscription can only use read tools, and your role must allow the action. |
| Only a few tools appear in the client | Expected. The assistant discovers the rest through search when it needs them. |
| Too many pages sent | Paging is rate-limited per account. If the assistant reports the limit, wait before trying again. |
Share your feedback
MCP is in beta, and your feedback directly shapes what we build next. Please let us know:
- What you tried to do and whether it worked
- Tools or data you wish the assistant could access
- Clients you want supported
- Anything confusing, slow or surprising
- Any other suggestions or desired improvements
Send feedback to FireHydrant Support or your account team.
Updated 16 minutes ago

