An astronaut overseeing a futuristic data hub

Connect FireHydrant to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run your incident response directly from your AI chat interface.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 12 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 12 available through FireHydrant.

  1. 01

    List services

    This capability pulls your entire service catalog so your agent knows which components are in your environment.

  2. 02

    Add incident note

    Use this to post a new note directly to an incident timeline.

  3. 03

    Create incident

    This capability lets your agent declare a brand new incident in FireHydrant.

  4. 04

    Get incident

    This capability retrieves specific details about a single incident.

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 12 available through FireHydrant.

  1. 05

    Get service

    Use this to get deep-dive details on a specific service in your catalog.

  2. 06

    List change events

    This capability lists recent change events to help you identify what might have caused an outage.

  3. 07

    List incidents

    This capability provides a list of all current incidents.

  4. 08

    List runbooks

    Use this to see which automated runbooks are available for your response.

Capability set03 / 03

09-12

4 capabilities in this set.

Part of 12 available through FireHydrant.

  1. 09

    List teams

    This capability retrieves a list of all responder teams.

  2. 10

    Update incident

    Use this to modify existing incident fields or status.

  3. 11

    Get team

    This capability fetches specific details for a responder team.

  4. 12

    List retrospectives

    This capability pulls a list of past retrospectives for post-incident review.

Real work

What teams actually run

01

Rapid Incident Response

Declare a new incident and notify responder teams immediately when a threshold is hit.

02

Outage Investigation

Ask your agent to list recent change events to see if a deployment caused the current issue.

03

Stakeholder Communication

Post status updates to the incident timeline to keep everyone on the same page.

04

Post-Mortem Prep

Retrieve past retrospectives to gather data for your next incident review.

Automate a task

Put FireHydrant to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

FireHydrant works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put FireHydrant to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

952ms average. Fast in production.

FireHydrant is checked daily against the live service.

Daily averagePeak 1074ms
Oct 3Today
Fastest day
804ms
Slowest day
1074ms
14-day trend
Stable+4%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 12 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of FireHydrant, so you can see the experience inside your AI.

It does not authenticate your account with FireHydrant. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

FireHydrant Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_Z9fBTFG9bYGC52Uaccytuw08nwfsGKdNijiOjVX5/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — FireHydrant capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "firehydrant-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_Z9fBTFG9bYGC52Uaccytuw08nwfsGKdNijiOjVX5/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up FireHydrant in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work FireHydrant owners hand off.

This MCP is built for technical teams who manage high-availability systems and need to act fast during outages.

  • 01

    SREs & DevOps Engineers

    They use the agent to declare incidents and fetch service data during active outages.

  • 02

    Incident Commanders

    They hand off timeline updates and team coordination tasks to the AI.

  • 03

    Engineering Managers

    They use the agent to get quick summaries of active incidents and recent changes.

FAQ

Questions FireHydrant owners ask.

  • 01

    How do I connect my FireHydrant account?

    You subscribe to the MCP on Vinkius and then enter your FireHydrant API Key, which you can find in your FireHydrant settings under API Keys.

  • 02

    Which AI clients can I use with this MCP?

    You can use this MCP with any compatible client, including Claude, Cursor, and Windsurf.

  • 03

    Can I actually create incidents through my AI agent?

    Yes, you can declare new incidents directly by telling your agent the severity and name of the issue.

  • 04

    Does this replace the FireHydrant dashboard?

    It doesn't replace it, but it gives you a way to perform key actions like updating timelines and checking services without leaving your coding or chat environment.

  • 05

    Where is the data hosted?

    Vinkius hosts and manages the MCP, so you don't have to worry about running the connection yourself.

  • 06

    How do I declare a new incident using the agent?

    You can use the 'create_incident' capability. 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.

  • 07

    Can I see recent infrastructure changes using this server?

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

  • 08

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

    Use the 'add_incident_note' capability. 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.

Connect FireHydrant to Claude, Cursor, ChatGPT & more