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

How to Use the Incident.io MCP in Cline

Cline handles your incident triage by reading live Incident.io data and executing resolutions without human intervention.

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
Cline

Connect Incident.io MCP to Cline

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

Cline automates incident triage

Cline uses `list_incidents` to monitor active alerts. When a new high-severity issue appears, it fetches the details via `get_incident` to start the investigation. It then checks `list_teams` to identify the right group to escalate to, keeping your response time low.

Query catalog types in Cline

Your infrastructure catalog changes fast. Cline uses `list_catalog_types` to stay updated on what services are currently tracked in your incident platform. This prevents your agent from making assumptions about outdated service architectures during a live outage.

Assign roles through Cline

During an active incident, you need to know who is doing what. Cline calls `list_incident_roles` to pull the current setup for your response team. It makes sure you have the right eyes on the problem by querying the live status of your team members.

Setup guide

Set up Incident.io MCP in Cline

Prerequisites

  • VS Code with Cline extension installed
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Open Cline MCP settings

    Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.

  2. 2

    Add a remote server

    Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type incidentio-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.

  3. 3

    Enable the server

    After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.

  4. 4

    Start using tools

    Return to the Cline chat and ask: "Check my latest Incident.io refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings
{
  "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 Cline

Go to the MCP Servers tab in your Cline sidebar. Add the server URL provided by Vinkius, and the tools will appear automatically.
You provide the key to the MCP server. Cline never sees your raw credentials, only the data returned by the tools.
Cline can fetch the data needed for resolution. It reads `list_severities` and `list_incidents` so it can help you build the fix faster.
Yes. This MCP server enforces strict access controls. Your incident logs and user data are never stored or shared beyond your local VS Code instance.
The server only transmits incident metadata, user rosters, and schedule information. It never touches your actual source code or application secrets.

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.