- TEAM LOOKUP
- DOC SEARCH
- TEAM DETAILS
- HUMAN ACTION
Short answer
How do I coordinate incident response with my AI?
You ask your AI to identify the correct responder teams or find specific runbooks. It pulls that data directly from FireHydrant so you can act immediately. You get the right people and the right instructions without switching tabs.
Incident outcomes
Where your incident data lands.
The AI handles the lookup work so you can focus on the fix.
TEAM LOOKUP
Identify responders
The AI identifies which teams are responsible for a specific service or component. You get a clear list of who needs to be in the incident.
DOC SEARCH
Find runbooks
Your AI finds the exact runbook needed for the current issue. You get the instructions you need to start remediation right away.
TEAM DETAILS
Get team info
The AI pulls specific details about a team's structure or ownership. This helps you understand exactly who is on call or responsible.
HUMAN ACTION
Execute the fix
The AI provides the data, but you make the decisions. You use the runbooks and team info to drive the actual incident resolution.
The workflow
What your AI does when an incident starts.
The AI acts as a bridge between your chat and your FireHydrant data.
Identify responders
The AI looks up all available responder groups to see who handles the affected service.
list_teamsGet team specifics
Once you pick a team, the AI pulls their specific details to confirm they are the right group.
get_teamLocate runbooks
The AI searches through your library to find the relevant procedures for the issue at hand.
list_runbooksSurface documentation
The AI presents the runbook content or links so you can follow the established protocol.
list_runbooks
Try it
Copy these to start.
Use these prompts to kick off your incident coordination.
Starting points
These are starting points. Swap out the team names or runbook titles with your actual FireHydrant data.
FireHydrant Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_Z9fBTFG9bYGC52Uaccytuw08nwfsGKdNijiOjVX5/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — FireHydrant capabilities are ready to use.
{
"mcpServers": {
"firehydrant-mcp": {
"url": "https://edge.vinkius.com/vk_preview_Z9fBTFG9bYGC52Uaccytuw08nwfsGKdNijiOjVX5/mcp"
}
}
}Which teams are responsible for the 'payment-gateway' service?
Show me the runbooks available for the 'database-outage' incident.
Get the details for the SRE response team.
List all runbooks related to 'auth-service' errors.
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect FireHydrant once, then ask.
One connection link is all it takes. Your credentials stay encrypted, and you can start using these tools in your preferred AI client immediately.
Connect FireHydrant to your AIFAQ
How the connector behaves
- 01
Can the AI trigger an incident in FireHydrant?
No. The AI can only read team and runbook data. You must trigger incidents manually in FireHydrant.
- 02
Can the AI change team membership?
No. The AI can list and get team information, but it cannot modify team settings or members.
- 03
Does the AI store my FireHydrant login?
No. Vinkius manages the connection securely, and your login stays encrypted.
- 04
Can I use this with Claude or Cursor?
Yes. Any MCP-compatible client works once you connect the FireHydrant MCP.
- 05
Can the AI delete a runbook?
No. The tools only allow the AI to list and retrieve runbook information.
More questions about FireHydrant? The Connector page answers them. See everything the FireHydrant Connector can do
Connect FireHydrant to Claude, Cursor, ChatGPT & more
