How to Use the FireHydrant MCP in Cursor

Q: How do I configure the FireHydrant MCP Server in Cursor?

Create an mcp.json file in your .cursor directory and define the FireHydrant server configuration. Once saved, enable Agent mode in your chat window to start using the tools.

Q: Can the Cursor agent automatically resolve my FireHydrant incidents?

Yes, the agent can call updateincident to change the incident status to resolved once your code changes are merged. This keeps your incident lifecycle perfectly synced with your git workflow.

Q: How can I view past post-mortems while coding?

You can ask the agent to run listretrospectives to pull up historical incident documentation. This helps you learn how previous on-call engineers fixed similar bugs in the codebase.

Code and debug your incident responses directly inside Cursor with live production context.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect FireHydrant MCP to Cursor

Create your Vinkius account to connect FireHydrant to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup FireHydrant with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Debug production issues directly in Cursor

The FireHydrant MCP Server exposes `create_incident` to let you trigger incident response workflows right from your editor when tests fail or logs show errors. You don't have to leave your code to report a critical issue to the team. When you are actively fixing a bug, the agent uses `update_incident` and `add_incident_note` to log your progress. This keeps the rest of the engineering organization updated while you focus entirely on writing the hotfix.

Map your local codebase to FireHydrant services using the MCP Server

Keeping track of which file belongs to which service is difficult in massive repositories. The `get_service` and `list_services` tools allow your agent to map your current directory structure to your official service catalog. If you need to know who to contact about an upstream dependency, the agent runs `get_team` or `list_teams` to pull up-to-date on-call details. This brings operational ownership data directly into your coding environment.

Correlate recent changes with active incidents

Finding the exact commit that broke production is easier when you can see what changed. The `list_change_events` tool pulls recent deployments and infrastructure updates directly inside Cursor. By analyzing these change events alongside active incident data from `list_incidents`, your agent can suggest the exact lines of code that need to be reverted. This dramatically reduces your mean time to resolution during critical events.

Setup guide

Set up FireHydrant MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the FireHydrant MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent FireHydrant transactions." If the MCP tools are loaded correctly, Cursor will call the FireHydrant tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "firehydrant-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by FireHydrant. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect FireHydrant now

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 Cursor

Create an `mcp.json` file in your `.cursor` directory and define the FireHydrant server configuration. Once saved, enable Agent mode in your chat window to start using the tools.

Yes, the agent can call `update_incident` to change the incident status to resolved once your code changes are merged. This keeps your incident lifecycle perfectly synced with your git workflow.

No, the MCP server runs securely on the Vinkius platform, so your editor connects directly to the managed endpoint. This ensures your local development machine doesn't suffer from performance overhead.

You can ask the agent to run `list_retrospectives` to pull up historical incident documentation. This helps you learn how previous on-call engineers fixed similar bugs in the codebase.

This integration only accesses incident metadata, service schemas, change logs, and team directories. All API calls are isolated within a zero-trust sandbox, ensuring your code and incident data remain secure.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript