2,500+ MCP servers ready to use
Vinkius

FireHydrant MCP Server for VS Code Copilot 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "firehydrant": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
FireHydrant
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.

GitHub Copilot Agent mode brings FireHydrant data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the FireHydrant MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using FireHydrant

Ask Copilot: "Using FireHydrant, help me...". 12 tools available

Why Use VS Code Copilot with the FireHydrant MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with FireHydrant through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

FireHydrant + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the FireHydrant MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

FireHydrant MCP Tools for VS Code Copilot (12)

These 12 tools become available when you connect FireHydrant to VS Code Copilot via MCP:

01

add_incident_note

Add note to incident

02

create_incident

Create a new incident

03

get_incident

Get incident details

04

get_service

Get service details

05

get_team

Get team details

06

list_change_events

List change events

07

list_incidents

List incidents

08

list_retrospectives

List retrospectives

09

list_runbooks

List active runbooks

10

list_services

List service catalog

11

list_teams

List responder teams

12

update_incident

Update an incident

Example Prompts for FireHydrant in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with FireHydrant immediately.

01

"List all currently active incidents in FireHydrant."

02

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

03

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

Troubleshooting FireHydrant MCP Server with VS Code Copilot

Common issues when connecting FireHydrant to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

FireHydrant + VS Code Copilot FAQ

Common questions about integrating FireHydrant MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect FireHydrant to VS Code Copilot

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.