How to Use the Incident.io MCP in Cursor

Q: How do I configure the Incident.io MCP Server in Cursor?

Add the server configuration to your global /.cursor/mcp.json or your project's .cursor/mcp.json file. Once saved, enable Agent mode in the chat panel to let Cursor invoke the tools.

Q: How does Cursor use Incident.io data during active debugging?

Your agent queries listincidents to find the active bug. It then reads the incident details to pinpoint which files in your workspace are likely causing the production failure.

Generate code and resolve outages using live Incident.io context inside Cursor.

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 Cursor

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Debug production issues in Cursor with live incident context

The `get_incident` tool pulls live production outage details directly into your Cursor composer. When you are writing a hotfix, your agent reads the active error logs and incident descriptions to understand what needs fixing. It matches the code you are editing against the actual failure report. You do not need to switch back and forth between your browser and your editor to check progress. The `list_incidents` tool keeps your workspace updated with the current status of the outage. This keeps your focus entirely on the code.

Map code ownership to active on-call schedules

The `list_schedules` tool connects your codebase directories to the engineers currently on call. Cursor uses this tool alongside `list_users` to suggest reviewers for your urgent pull requests. It identifies who is active so you do not assign a critical patch to someone who is asleep. It also queries `list_teams` to find the exact engineering group responsible for the failing service. This MCP Server automates the administrative side of incident response while you write the fix inside your editor.

Configure custom incident metadata inside Cursor

The `list_custom_fields` tool lets your agent inspect how your organization structures its incident data. When building internal automation scripts, Cursor reads these fields to ensure your code matches your production schema. You avoid API errors caused by outdated field names. It uses `list_incident_types` and `list_severities` to validate your local configuration files before you commit them. The agent checks that your automated alert routing rules align with actual incident definitions. This keeps your infrastructure-as-code files accurate.

Setup guide

Set up Incident.io 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 Incident.io 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 Incident.io transactions." If the MCP tools are loaded correctly, Cursor will call the Incident.io tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/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 Cursor

Add the server configuration to your global `~/.cursor/mcp.json` or your project's `.cursor/mcp.json` file. Once saved, enable Agent mode in the chat panel to let Cursor invoke the tools.

No, this server is read-only to prevent accidental modifications during high-stress triage. It uses `get_incident` to fetch details, but you must use the web UI or Slack to make updates.

Your agent queries `list_incidents` to find the active bug. It then reads the incident details to pinpoint which files in your workspace are likely causing the production failure.

No scripts are needed. The MCP Server exposes standard tools like `list_catalog_types` out of the box, which Cursor calls automatically when you ask about your incident structure.

Your API key is stored as an environment variable in your local environment or managed securely via Vinkius MCP host. Cursor only receives the output of tools like `list_users` and never has direct access to your raw credentials.

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