How to Use the FireHydrant MCP in Claude
Run your incident response directly from Claude Desktop without jumping between terminal windows and browser tabs.
Works with every AI agent you already use
…and any MCP-compatible client
Connect FireHydrant MCP to Claude Desktop
Create your Vinkius account to connect FireHydrant to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.
Control incidents directly via the FireHydrant MCP Server
The FireHydrant MCP Server exposes `create_incident` to let your AI client declare outages the second alerts spike. You don't have to open a browser or copy-paste Slack alerts into a form. Just tell your agent what's broken, and it initiates the incident tracking process immediately. Once the incident is active, the agent uses `update_incident` to adjust severity levels or assign roles based on the current situation. You can also run `add_incident_note` to dump raw log outputs or error traces directly into the timeline, keeping everyone on your team updated in real time.
Pinpoint failing services and alert the right team
Finding the owner of a broken microservice during a high-severity outage takes too much time. The `get_service` and `list_services` tools let your agent pull service definitions and metadata directly into your chat. This replaces manual catalog lookups and prevents engineers from wasting minutes hunting down owners. After identifying the broken component, the agent runs `get_team` or `list_teams` to find the exact on-call rotation responsible for that service. You can immediately page the right people instead of guessing which team owns the database or the API gateway.
Gather retrospective context without manual digging
Writing post-mortems usually requires hunting through Slack channels, git commits, and deployment logs. The `list_change_events` tool pulls recent deployments and infrastructure changes directly into Claude Desktop to help you find the root cause. Your agent can then call `list_retrospectives` and `list_runbooks` to check how similar incidents were handled in the past. This lets you draft accurate incident timelines and action items without leaving your conversational workspace.
Set up FireHydrant MCP in Claude Web or Desktop
- 1
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
- 2
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcpReplace[YOUR_TOKEN_HERE]with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials. - 3
Start a conversation
Open a new chat. The FireHydrant MCP tools are available immediately — no restart needed.
Endpoint URL
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp No configuration file needed — paste the URL directly in the Claude web interface.
Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.
Why Choose Vinkius
Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.
Real-time monitoring
Live
visibility into every interaction
Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.
Built-in savings
60%
lower AI costs
Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.
Single dashboard
One
place for every integration
Every tool your AI connects to, managed from a single screen. One account, complete control.
Common questions about FireHydrant MCP in Claude Desktop
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
Start using the FireHydrant MCP today
We host it, we monitor it, we maintain it. You just paste one token.