4,500+ servers built on MCP Fusion
Vinkius
Incident.io logo
Vinkius
Windsurf logo

How to Use the Incident.io MCP in Windsurf

Stop hunting for incident data. Let Windsurf query Incident.io directly to pull the right on-call schedules and incident details.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Incident.io MCP on Cursor AI Code Editor MCP Client Incident.io MCP on Claude Desktop App MCP Integration Incident.io MCP on OpenAI Agents SDK MCP Compatible Incident.io MCP on Visual Studio Code MCP Extension Client Incident.io MCP on GitHub Copilot AI Agent MCP Integration Incident.io MCP on Google Gemini AI MCP Integration Incident.io MCP on Lovable AI Development MCP Client Incident.io MCP on Mistral AI Agents MCP Compatible Incident.io MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
Windsurf

Connect Incident.io MCP to Windsurf

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

Auto-sync incident contexts in Windsurf

Windsurf Cascade scans your current codebase and identifies where things broke. It uses `get_incident` to pull the exact status from your dashboard without leaving the editor. Then it pulls the latest `list_severities` and `list_incident_types` to ensure your fix aligns with the current priority levels.

Manage on-call rotations via Windsurf

Stop context switching between your browser and your IDE. Windsurf uses `list_schedules` to tell you exactly who is on call right now. It cross-references that with `list_users` so you know who to ping when a production alert hits your terminal.

Map custom fields for Incident.io

Your incident metadata lives in specific fields that matter to your team. Windsurf queries `list_custom_fields` so your agent understands the unique schema of your organization. This MCP server ensures that every piece of data pulled into your environment matches the definitions set in your incident management platform.

Setup guide

Set up Incident.io MCP in Windsurf

Prerequisites

  • Windsurf IDE installed (macOS, Windows, or Linux)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Open MCP configuration

    Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.

  2. 2

    Add the Incident.io MCP

    Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.

  3. 3

    Refresh MCPs

    Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.

  4. 4

    Verify in Cascade

    Start a new Cascade conversation and ask something like "Show my Incident.io payment history." If connected, Cascade will call the Incident.io tools directly. You will see a green dot next to the server name in the MCP panel.

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

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.

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 Windsurf

The server acts as a bridge. It connects your Windsurf session to the Incident.io API, allowing your agent to read live incident data on demand.
No. Your API key remains local to your machine. Vinkius handles the connection layer, and Windsurf only gets the data you explicitly ask for.
Not at all. The tools only execute when your agent calls them. It stays idle in the background until you need a status update.
The server queries the live API. You get the latest custom field definitions immediately every time your agent runs a tool.
Your incident reports and user lists stay within your local session. The MCP server treats this sensitive information as ephemeral traffic.

Start using the Incident.io MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for Incident.io. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.