create-incident
Create an incident
Create a new incident
Open an incident, see what is already running, pull the retrospective attached to it and write a field back — from the same place the outage is being discussed.
LABSCO SUMMARY
The retrospective tools are what make it worth connecting — list-retros-by-incident returns a retrospective's fields and update-retrospective-field writes one back, so a write-up drafted in conversation lands in the record instead of being retyped into it. That write takes unstyled HTML, which is the detail to settle before anything automated goes near it. Every tool takes a single request parameter, so what a call can filter, page or set is governed by the FireHydrant API shape rather than by anything the tool signature reveals.
A FireHydrant client covering the incident record and its retrospective: listing and creating incidents, listing alerts including Signals and third-party alerts, and reading and updating retrospective fields.
A FireHydrant API key, supplied with --api-key when the server starts.
One command — npx firehydrant-mcp start --api-key ...
USE CASES
Check what has fired, then open the incident record without switching tools.
Fetch the retrospective's fields for the incident, then write the drafted text straight into the one it belongs in.
Read the current incidents and the alerts behind them so a duplicate record does not get raised.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create-incidentCreate an incident
Create a new incident
list-alertsList alerts
Retrieve all alerts, including Signals alerts and third-party
list-incidentsList incidents
List all of the incidents in the organization
list-retros-by-incidentLists all retrospectives (RCAs) for an incident. Among other things, this is useful for:
update-retrospective-fieldUpdates a field in a retrospective (RCA) for an incident. Among other things, this is useful for:
The value should be unstyled HTML.
BEFORE YOU INSTALL
5 tools when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"firehydrant-mcp": {
"command": "npx",
"args": [
"firehydrant-mcp",
"start",
"--api-key",
"<YOUR_API_KEY>"
]
}
}
}npx firehydrant-mcp start --api-key ...