How do I connect this MCP to my AI client?

You connect once through the Vinkius interface. Vinkius hosts the MCP and manages the connection so it is ready to use in clients like Claude or Cursor.

Do I need to provide my own Incident.io API key?

Yes, you will need to provide your credentials so the MCP can act on your behalf within your Incident.io account.

Can my agent see my on-call schedules?

Yes, the MCP includes a capability specifically to list all on-call schedules.

What kind of clients can use this MCP?

Any MCP-compatible client like Claude, Cursor, or Windsurf can use this to interact with your incident data.

Does this MCP allow me to create incidents?

This specific MCP focuses on retrieving and listing data such as incidents, roles, schedules, and users.

How do I get Incident.io API credentials?

Log in to your Incident.io dashboard, navigate to Settings > API keys, and click 'Add new' to generate a Bearer Token.

Which version of the API is used?

This MCP uses Incident.io API v2, the latest stable version for comprehensive incident management.

Can I see on-call schedules?

Yes, the list_schedules capability provides access to on-call schedules and rotation information.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Incident.io to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Let your agent handle the heavy lifting of incident response.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Incident.io.

01
Get incident
This capability pulls the full details for a specific incident you identify.
02
List catalog types
Use this to see all the different catalog types defined in your account.
03
List severities
This capability returns a list of all incident severities currently configured.
04
List custom fields
Get a list of all custom fields used within your incident records.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Incident.io.

05
List incident roles
This capability retrieves the various incident roles available in your setup.
06
List incidents
Use this to pull a list of all incidents recorded in the system.
07
List incident types
This capability provides a list of all defined incident types.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Incident.io.

08
List schedules
Get a list of all on-call schedules managed through Incident.io.
09
List teams
This capability returns a list of all teams in your organization.
10
List users
Use this to retrieve a list of all users in the system.

Real work

What teams actually run

Rapid Incident Triage

Ask your agent for the details of a specific incident to understand the impact immediately.

On-call Verification

Check who is currently on call by asking the agent to pull the active schedule.

Workflow Auditing

Use the agent to list all incident types and severities to ensure your setup is correct.

Team Mapping

Identify which users and teams are involved in the response by querying the system.

Automate a task

Put Incident.io to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Incident.io works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Incident.io to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

963ms average. Fast in production.

Incident.io is checked daily against the live service.

Daily averagePeak 1195ms

Oct 3Today

Fastest day: 756ms
Slowest day: 1195ms
14-day trend: Stable-4%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Incident.io, so you can see the experience inside your AI.

It does not authenticate your account with Incident.io. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Incident.io Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_SYXytajPn2E8oSQTe6uxrJcvhwsU2x1pHkOPCe4y/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Incident.io capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "incidentio-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_SYXytajPn2E8oSQTe6uxrJcvhwsU2x1pHkOPCe4y/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Incident.io in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Incident.io owners hand off.

This MCP is built for technical teams that rely on Incident.io to coordinate their response to system failures.

01
SREs
They use the agent to quickly pull incident data and check on-call status during outages.
02
Incident Commanders
They use the agent to verify roles and incident details while managing a response.
03
DevOps Engineers
They use the agent to audit incident configurations and team structures.

FAQ

Questions Incident.io owners ask.

01
How do I connect this MCP to my AI client?
You connect once through the Vinkius interface. Vinkius hosts the MCP and manages the connection so it is ready to use in clients like Claude or Cursor.
02
Do I need to provide my own Incident.io API key?
Yes, you will need to provide your credentials so the MCP can act on your behalf within your Incident.io account.
03
Can my agent see my on-call schedules?
Yes, the MCP includes a capability specifically to list all on-call schedules.
04
What kind of clients can use this MCP?
Any MCP-compatible client like Claude, Cursor, or Windsurf can use this to interact with your incident data.
05
Does this MCP allow me to create incidents?
This specific MCP focuses on retrieving and listing data such as incidents, roles, schedules, and users.
06
How do I get Incident.io API credentials?
Log in to your Incident.io dashboard, navigate to Settings > API keys, and click 'Add new' to generate a Bearer Token.
07
Which version of the API is used?
This MCP uses Incident.io API v2, the latest stable version for comprehensive incident management.
08
Can I see on-call schedules?
Yes, the list_schedules capability provides access to on-call schedules and rotation information.

Explore

More in Collaboration

Connect Incident.io to Claude, Cursor, ChatGPT & more

Your AI does the work. We keep it safe and sound.

Each Connector runs inside its own sealed environment.

One switch stops every agent. Instantly.

Spending limits that pause instead of surprise.

We ship only the actions that matter.

01-04

Get incident

List catalog types

List severities

List custom fields

05-07

List incident roles

List incidents

List incident types

08-10

List schedules

List teams

List users

What teams actually run

Rapid Incident Triage

On-call Verification

Workflow Auditing

Team Mapping

Building your own app? The connector is yours to use.

Incident.io Connector

Claude Desktop

SREs

Incident Commanders

DevOps Engineers

How do I connect this MCP to my AI client?

Do I need to provide my own Incident.io API key?

Can my agent see my on-call schedules?

What kind of clients can use this MCP?

Does this MCP allow me to create incidents?

How do I get Incident.io API credentials?

Which version of the API is used?

Can I see on-call schedules?

Better Stack AI Connector

PagerDuty Incident Trigger AI Connector

Teambition AI Connector

Argo Workflows AI Connector

Suggestions

Opsgenie AI Connector

Collection Emergency Response Workflow AI Connector

n8n (AI Workflow Automation) AI Connector

Make (Workflow Automation) AI Connector