How do I declare a new incident using the agent?

You can use the 'create_incident' tool. Simply provide a name and optionally a summary and severity level. The agent will trigger the declaration in FireHydrant and return the new incident details.

Can I see recent infrastructure changes using this server?

Yes! The 'list_change_events' tool retrieves a history of recent changes. This is extremely useful for identifying potential root causes during an active incident investigation.

How do I add a status update to an ongoing incident?

Use the 'add_incident_note' tool. You'll need the Incident ID and the text of your update. The note will be immediately posted to the incident's timeline for all responders to see.

FireHydrant MCP Server for Claude Desktop 12 tools — connect in under 2 minutes

Name: FireHydrant
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 12 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install FireHydrant and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "firehydrant": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About FireHydrant MCP Server

Connect your FireHydrant account to any AI agent and automate your incident management workflows through the Model Context Protocol (MCP). FireHydrant provides a comprehensive platform for declaring incidents, managing service catalogs, and coordinating team responses. Now, you can manage your site reliability and incident response directly through natural conversation.

Claude Desktop is the definitive way to connect FireHydrant to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Incident Management — Declare new incidents, list active ones, and update milestones or fields instantly.
Service Catalog — Access and list all defined services to understand impact and dependencies during an outage.
Team Coordination — List and manage responder teams to ensure the right people are assigned to every incident.
Timeline Updates — Post notes and status updates directly to an incident's timeline from your chat interface.
Runbook Execution — List active runbooks to understand the automated workflows available for your response.
Post-Incident Analysis — Retrieve retrospectives and post-incident reviews to facilitate learning and improvement.
Change Tracking — List change events to identify recent infrastructure or code changes that might have triggered an incident.

The FireHydrant MCP Server exposes 12 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect FireHydrant to Claude Desktop via MCP

Follow these steps to integrate the FireHydrant MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using FireHydrant

Look for the 🔌 icon in the chat — your 12 tools are now available

Why Use Claude Desktop with the FireHydrant MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with FireHydrant through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

FireHydrant + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the FireHydrant MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

FireHydrant MCP Tools for Claude Desktop (12)

These 12 tools become available when you connect FireHydrant to Claude Desktop via MCP:

add_incident_note

Add note to incident

create_incident

Create a new incident

get_incident

Get incident details

get_service

Get service details

get_team

Get team details

list_change_events

List change events

list_incidents

List incidents

list_retrospectives

List retrospectives

list_runbooks

List active runbooks

list_services

List service catalog

list_teams

List responder teams

update_incident

Update an incident

Example Prompts for FireHydrant in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with FireHydrant immediately.

"List all currently active incidents in FireHydrant."

"Declare a new sev-2 incident: 'Redis Connection Spikes'."

"Add a note to incident 'inc_123': 'Investigating potential cache invalidation issue'."

Troubleshooting FireHydrant MCP Server with Claude Desktop

Common issues when connecting FireHydrant to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

FireHydrant + Claude Desktop FAQ

Common questions about integrating FireHydrant MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.