4,000+ servers built on MCP Fusion
Vinkius
CursorIDE
Why use FireHydrant MCP Server with Cursor?

Bring Incident Management
to Cursor

Create your Vinkius account to connect FireHydrant to Cursor and start using all 12 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Add Incident NoteCreate IncidentGet IncidentGet ServiceGet TeamList Change EventsList IncidentsList RetrospectivesList RunbooksList ServicesList TeamsUpdate Incident
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
FireHydrant

What is the 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.

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.

How it works

  1. Subscribe to this server through the Vinkius Marketplace
  2. Enter your FireHydrant API Key (found in your Settings > API Keys)
  3. Start managing your incident response from Claude, Cursor, or any MCP client

Who is this for?

  • SREs & DevOps Engineers — quickly declare incidents and fetch service details during high-pressure outages.
  • Incident Commanders — automate the gathering of team information and timeline updates through simple AI commands.
  • Engineering Managers — get an overview of active incidents and recent change events to keep stakeholders informed.

Built-in capabilities (12)

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

Why Cursor?

Cursor's Agent mode turns FireHydrant into an in-editor superpower. Ask Cursor to generate code using live data from FireHydrant and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

  • Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

  • Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

  • MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

  • VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

FireHydrant in Cursor

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run FireHydrant with Vinkius?

The FireHydrant connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 12 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

FireHydrant
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect FireHydrant using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

FireHydrant and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect FireHydrant to Cursor through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures FireHydrant for Cursor

Every request between Cursor and FireHydrant is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

05

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

06

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

07

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

08

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

09

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Explore More MCP Servers

View all →