How to Use the Incident.io MCP in VS Code Copilot

Q: How do we share the Incident.io MCP configuration in VS Code Copilot?

Create a .vscode/mcp.json file in your repository root and commit it to Git. Every team member with VS Code Copilot will instantly get access to the same incident tools.

Q: Can VS Code Copilot help assign on-call responders using Incident.io?

Yes. Copilot queries listschedules to see who is currently on shift. It then uses listusers to identify the correct engineer to contact for the active incident.

Q: Does this VS Code Copilot integration support custom fields?

Yes, it uses listcustomfields to fetch your team's specific metadata definitions. This allows Copilot to understand your custom classification system when parsing active alerts.

Drive team-wide incident response directly from VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Incident.io MCP to VS Code Copilot

Create your Vinkius account to connect Incident.io to VS Code Copilot 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 Incident.io with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate incident response inside VS Code Copilot

The `list_incidents` tool fetches active production issues and displays them directly inside your Copilot Chat panel. Your team can triage ongoing events without leaving the editor. It allows developers to quickly see what is broken and who is working on it. By using `get_incident`, your agent pulls specific technical details about a failure. This lets you generate debugging steps based on actual production error descriptions instead of guessing. It keeps your entire team aligned during a critical outage.

Audit team assignments with this MCP Server

The `list_teams` tool queries your organizational structure to see which group is assigned to an active issue. Copilot uses this alongside `list_incident_roles` to verify if the correct engineers are leading the response effort. It helps managers keep track of resource allocation during complex incidents. It also pulls roster data with `list_users` to see who is available to assist. This prevents you from pinging off-duty developers. The entire team shares this configuration through a committed workspace file.

Standardize alert classifications across your codebase

The `list_severities` tool brings your official Incident.io severity levels directly into your development workflow. When writing alert rules or logging configurations, Copilot checks these levels to ensure your code matches company policy. You avoid using non-standard severity tags in your software. It uses `list_incident_types` and `list_catalog_types` to validate your telemetry configurations. The agent ensures that your custom metrics align with your incident categories. This prevents missing alerts when your code goes to production.

Setup guide

Set up Incident.io MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Incident.io MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Incident.io tools listed. Try asking: "List my recent Incident.io transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "incidentio-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 Incident.io. 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 Incident.io 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 Incident.io MCP in VS Code Copilot

Create a `.vscode/mcp.json` file in your repository root and commit it to Git. Every team member with VS Code Copilot will instantly get access to the same incident tools.

Yes. Copilot queries `list_schedules` to see who is currently on shift. It then uses `list_users` to identify the correct engineer to contact for the active incident.

Yes, it uses `list_custom_fields` to fetch your team's specific metadata definitions. This allows Copilot to understand your custom classification system when parsing active alerts.

No local installation is required if you use Vinkius to host the MCP Server. Your team only needs to point their `.vscode/mcp.json` configuration to the secure Vinkius endpoint.

The MCP Server only accesses user directories and incident logs through secure, encrypted API calls. Vinkius executes these requests in isolated, ephemeral sandboxes, ensuring your employee and incident data is never cached or leaked.

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