Merge Unified's FireHydrant integration Merge Agent Handler's FireHydrant MCP server

Connect your AI Agents to FireHydrant in minutes

Merge lets you securely connect your agents to FireHydrant and thousands of tools instantly

Start building for free

Read docs

FireHydrant

Learn more about Merge Agent Handler

Available tools

list_environments

List environments with optional search query. Supports pagination.

create_environment

Create a new environment with a name and optional description.

get_environment

Get environment details by ID.

update_environment

Update an environment's name or description.

delete_environment

Delete an environment by ID.

list_incidents

List incidents with optional filters by status or search query. Supports pagination.

create_incident

Create a new incident with name, optional summary, severity, and team assignments.

get_incident

Get incident details by ID.

update_incident

Update an incident's name, summary, severity, or status.

resolve_incident

Resolve an incident by ID.

delete_incident

Delete (archive) an incident by ID.

list_runbooks

List runbooks with optional search query. Supports pagination.

get_runbook

Get runbook details by ID.

list_services

List services with optional search query. Supports pagination.

create_service

Create a new service with a name and optional description.

get_service

Get service details by ID.

update_service

Update a service's name or description.

delete_service

Delete a service by ID.

list_severities

List all available severities. Supports pagination.

list_incident_tasks

List tasks for an incident with pagination.

create_incident_task

Create a new task for an incident.

get_incident_task

Get details for a specific task in an incident.

update_incident_task

Update a task in an incident.

delete_incident_task

Delete a task from an incident.

list_teams

List teams with optional search query. Supports pagination.

create_team

Create a new team with a name and optional description.

get_team

Get team details by ID.

update_team

Update a team's name or description.

delete_team

Delete a team by ID.

list_users

List users with optional search query. Supports pagination.

get_user

Get user details by ID.

validate_credential

Validate FireHydrant API credentials.

View all tools by creating a free account See more tools

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}

Copy Code

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }

Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}

Copy Code

FAQs on using Merge's FireHydrant MCP server

What is a FireHydrant MCP?

It's an MCP server that connects your agents to FireHydrant's incident management platform via tools. Your agents can invoke these tools to create and update incidents, trigger runbooks, assign tasks to responders, query service health, and more.

FireHydrant offers an official MCP server, but you can also use one from a third-party platform, like Merge Agent Handler.

How can I use the FireHydrant MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

Alert-to-incident automation: An agent monitors an alerting system like PagerDuty or Datadog and automatically opens a FireHydrant incident when a threshold is crossed, pre-populating severity, affected services, and the initial task list

Slack-driven incident updates: An agent listens for commands in a Slack incident channel and updates the corresponding FireHydrant incident's status, severity, or summary without requiring responders to switch tools

Post-incident report generation: After an incident resolves, an agent pulls the full incident timeline and task history from FireHydrant and drafts a post-mortem summary in Notion or Confluence

On-call coordination: An agent detects a new high-severity incident in FireHydrant, looks up the current on-call schedule, and sends a direct message to the responsible team in Slack or Microsoft Teams

What are popular tools for FireHydrant's MCP server?

Here are some of the most commonly used tools:

create_incident: opens a new FireHydrant incident with specified severity, affected services, and summary. Useful for agents that need to trigger incident response automatically based on signals from an external monitoring system

list_incidents: retrieves active or historical incidents with optional filters for status, severity, or service. Call this when an agent needs to check current incident load before escalating or to build a weekly summary report

resolve_incident: marks an open incident as resolved and records a resolution note. Good for workflows where an agent confirms a fix in a deployment system and then closes the corresponding incident automatically

list_runbooks: fetches the available runbooks in the FireHydrant account. Helpful when an agent needs to identify the right runbook for a given incident type before guiding a responder through next steps

create_incident_task: adds a task to an active incident with an assigned owner and due time. Use this when an agent is coordinating multi-step response actions across different team members

list_services: returns the registered services in FireHydrant, including ownership and environment details. Call this when an agent needs to determine which team owns an affected service during triage

What makes Merge Agent Handler's FireHydrant MCP server better than alternative FireHydrant MCP servers?

Several factors make Merge Agent Handler's FireHydrant MCP server a stronger choice than building your own or using an alternative:

Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For FireHydrant, this means you can prevent incident descriptions containing customer PII, internal IP details, or severity classifications from being exposed to an agent with broad read access

Managed authentication and credentials: Merge stores and refreshes FireHydrant credentials on your behalf. You never expose raw API keys or OAuth tokens to an agent or manage token rotation manually

Real-time observability and audit trail: Every tool call made against FireHydrant is logged with timestamp, tool name, input parameters, and response metadata. You can audit exactly what an agent read or wrote without instrumenting anything yourself

Tool Packs and controlled access: Tool Packs let you bundle specific FireHydrant tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's FireHydrant MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account.

2. Install the Merge CLI by running pipx install merge-api, then run merge configure to link the CLI to your Merge account and merge login to authenticate your session.

3. Register the Agent Handler MCP server with Claude Code by running claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp, then open Claude Code and run /mcp to confirm agent-handler appears with a connected status.

4. Select agent-handler from the MCP list. This opens a browser window where you select which integrations to authenticate. Choose FireHydrant and complete the auth flow. Merge stores and manages the credentials going forward.

5. Open a Claude Code session and start querying FireHydrant data directly. The first time you use a FireHydrant tool, a Magic Link may appear to complete connector authentication.

If you want to connect Merge Agent Handler's FireHydrant MCP with internal or customer-facing agentic products, you can follow the steps in our docs.