For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.mcpbundles.com/bundle/firehydrant
Skill page: https://www.mcpbundles.com/skills/firehydrant
Tools: 41
Live probe refreshed Nov 21, 2026 · Endpoint host mcp.mcpbundles.com
AI Skill
SKILL.md
Domain knowledge for FireHydrant — workflow patterns, data models, and gotchas for your AI agent.
FireHydrant
Incident management platform for declaring, triaging, automating, and reviewing incidents across services and teams. Covers the full incident lifecycle from alert to post-mortem.
Entity Hierarchy
The data model has three layers: catalog (what you own), incident (what's happening), and retrospective (what happened).
Catalog (steady-state configuration)
Services — things that can break (microservices, infrastructure components). Each has an owner team and environment links. Search by name with query. Open a service by id for full details.
Teams — groups of people who respond. Linked to services, on-call schedules, and incident roles.
Users — individual responders.
Environments — deployment targets (production, staging). Incidents are scoped to environments.
Infrastructures — broader infra components (AWS region, data center).
Functionalities — user-facing capabilities a service provides ("checkout flow", "search").
Incident Configuration
Severities — ordered severity levels (SEV1–SEV5 or custom). Drives SLA timers and escalation.
Priorities — urgency ordering, separate from severity.
Incident Roles — responsibilities during response (Incident Commander, Communications Lead).
Incident Tags — freeform labels for filtering and reporting.
Phases — lifecycle stages an incident moves through (detected → acknowledged → mitigated → resolved).
Severity Matrix — conditions × impacts grid that auto-assigns severity. Query conditions and impacts separately.
Automation
Runbooks — step-by-step automation playbooks attached to incidents. Each runbook has actions (individual steps) and executions (historical runs). Audits track who changed runbook definitions.
Checklist Templates — manual task checklists for common incident procedures.
Task Lists — incident-scoped lists of assigned work items.
Signals On-Call — who is currently on call and receiving alerts.
Incident Operations
Incidents — the core entity. Each has severity, priority, type, affected services, environments, and assigned teams/roles. Filter by status (open/in_progress/resolved/closed), severity (SEV1-SEV5), or search by query. Open an incident by id for the full timeline.
Changes — deployment and configuration change records linked to the service catalog. Change Events are the individual events within a change.
Tickets — external tracking tickets linked to incidents. Ticket Tags and Ticketing Priorities configure the ticketing system. Ticketing Projects organize tickets.
Custom Field Definitions — schema for custom data on incidents.
Entitlements — account-level feature flags and plan limits.
NUNC Connections — status page connections for public incident communication.
Workflows
Triage an alert: list alerts → find the relevant alert → list incidents to see if one already exists → check services and on-call schedules.
Assess impact: list services and functionalities to understand what's affected → query severity matrix conditions/impacts to see auto-severity logic → list environments to scope the blast radius.
Review response capacity: list teams → list users → check signals on-call for current responders → list incident roles for assignment needs.
Audit automation: list runbooks → drill into runbook executions for recent runs → review runbook audits for definition changes → list checklist templates for manual procedures.
Post-incident analysis: list post-mortem reports → review post-mortem questions for standard retrospective structure → pull mean-time reports for MTTA/MTTR trends.
Change correlation: list changes and change events around an incident timeframe to identify causal deployments.
Gotchas
Rate limit: 50 requests per 10 seconds (300/min); back off when responses indicate throttling.
Pagination: most lists use page index + page size; responses include pagination metadata.
Measurement definitions sit under lifecycle measurement resources, not the API root.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms
FireHydrant
Add to your AI client, then sign in once when you connect.
FireHydrant is an incident management platform designed to streamline incident response, automate tasks, and improve team collaboration during outages. Use it to coordinate responses, analyze incidents, and enhance reliability practices.
This listing identifies a third-party integration. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
Showing 41 of 41 tools from the public preview. Connect the server to inspect the full live tool list.
Firehydrant41
Firehydrant Get Incident
read
firehydrant_get_incident
Get a specific incident by ID — full details including name, severity, current phase, started/resolved timestamps, impacted services, milestones, and role assignments. Requires 'incident_id'.
Firehydrant Get Incident — Get a specific incident by ID — full details including name, severity, current phase, started/resolved timestamps, impacted services, milestones, and role assignments. Requires 'incident_id'.
Firehydrant Get Service — Get a specific service by ID — full details including name, description, owner team, tier, external resources, and linked functionalities. Requires 'service_id'.
Firehydrant List Alerts — Retrieve a list of alerts that have been triggered in the system. Use this to monitor and respond to active alerts efficiently. Returns detailed information about each alert, such as severity, status, and originating service.
Firehydrant List Changes — List all recent changes within your system, as tracked by FireHydrant. Ideal for reviewing and auditing changes made to your infrastructure. Returns information like change ID, description, and affected services.
Firehydrant List Changes Events — Retrieve a list of change events recorded in FireHydrant. Use this to analyze recent system changes and their impact. Returns details such as event ID, summary, and timestamp.
Firehydrant List Checklist Templates — Access a collection of checklist templates for incident management processes. Use this to ensure consistency in handling similar incidents with predefined steps. Returns a variety of templates, each with a set of recommended tasks.
Firehydrant List Custom Fields Definitions — Get all custom field definitions available in your setup. Use this to tailor incident records with specific data points or when setting up new custom fields. Returns field IDs and definitions. No parameters required.
Firehydrant List Entitlements — Retrieve all entitlements currently available in your FireHydrant account. Use this to assess permission structures and access controls. Returns details on each entitlement including ID and description.
Frequently Asked Questions
What is the FireHydrant MCP server?
FireHydrant is an incident management platform designed to streamline incident response, automate tasks, and improve team collaboration during outages. Use it to coordinate responses, analyze incidents, and enhance reliability practices. It provides 41 tools that AI agents can use through the Model Context Protocol (MCP).
How do I connect FireHydrant to my AI agent?
Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/firehydrant. Authentication is handled automatically.
Firehydrant List Environments — Retrieve a list of all environments within your FireHydrant account. Use this to view and manage the environments where your services are deployed. Returns details for each environment, such as environment IDs and names.
Firehydrant List Functionalities — Access a complete list of functionalities supported by your organization. Use this to understand what functionalities are covered by your operations. Returns data such as functionality ID and description.
Firehydrant List Incident Roles — Retrieve a full list of incident roles available in FireHydrant. Use this to understand and configure roles for effective incident management. Returns detailed information for each role such as role ID and description, helping you define team members' responsibilities.
Firehydrant List Incidents — Get a complete list of all incidents recorded in FireHydrant. Essential for reviewing past incidents and managing resolutions. Provides details such as incident ID, status, and summary.
Firehydrant List Incident Tags — Get a list of all incident tags configured in your FireHydrant account. Utilize this to quickly categorize incidents and streamline searches. Returns tag details like ID and name, useful for tagging incidents effectively.
Firehydrant List Incident Types — Fetch all incident types defined in your system. Use this to align incidents with predefined categories, ensuring consistent incident tracking and reporting. Returns information such as type ID and description.
Firehydrant List Infrastructures — Access a list of infrastructures configured in your environment. Utilize during audits or infrastructure planning to ensure accuracy and coverage. Returns infrastructure IDs, names, and types. No parameters are necessary.
Firehydrant List Integrations — Retrieve a list of all integrations available in FireHydrant. This is useful when managing or setting up third-party tool integrations for automated incident response. Returns integration details like ID, name, and connection status.
Firehydrant List Measurement Definitions — Get all measurement definitions for lifecycle tracking. Utilize this when setting up or reviewing your lifecycle metrics to understand predefined metrics. Returns a list with measurement IDs and criteria. No parameters required.
Firehydrant List Nunc Connections — Retrieve a list of all NUNC connections. Use this during incident analysis or setup to view current integrations and external service connections. Returns details including connection ID and status. No parameters required.
Firehydrant List Phases — Access a list of lifecycle phases implemented within your incident management workflow. Employ this to review or update phases during lifecycle reviews or process planning. Returns phases with phase ID and name. No parameters necessary.
Firehydrant List Post Mortems Questions — Access a collection of questions typically used in post-mortem processes. Use this to ensure thorough incident reviews by covering all essential areas of investigation. Returns a list of standard questions that can be tailored to specific incidents.
Firehydrant List Post Mortems Reports — Retrieve a list of post-mortem reports from the incident management process. Use this when you need to analyze past incidents to improve future response strategies. Returns detailed information about each report, including summaries and findings.
Firehydrant List Priorities — List all priority levels defined in your incident management configuration. Use this when configuring incidents to ensure correct priority levels are set. Responses include priority IDs and descriptions. No parameters needed.
Firehydrant List Reports — Access mean time reports across incidents in FireHydrant. Utilize this for performance analysis and optimization of response time. Returns metrics like mean time to acknowledge (MTTA) and mean time to resolve (MTTR) for selected periods.
Firehydrant List Runbook Actions — Retrieve a list of actions available in your runbooks. Use this to automate specific tasks during incident response efficiently. Returns action details such as action ID, name, and type, which are essential for designing automated workflows.
Firehydrant List Runbook Audits — Fetch audit logs for all runbook actions. This is crucial for compliance and reviewing historical changes. Returns audit entries with detailed information such as changes made, user responsible, and timestamps.
Showing the first 25 tools — full list and schemas: Directory API.
How many tools does FireHydrant provide?
FireHydrant provides 41 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.
What authentication does FireHydrant require?
FireHydrant uses API Key. FireHydrant requires credentials. Connect via MCPBundles and authentication is handled automatically.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.
More in developer tools
Other MCP servers in this category from the directory index