Skip to content
Vinkius

Incident.io Connector for AI agents.

10 live capabilities

Automate incident response and on-call scheduling for SRE teams.

Live agent request Incident.io / Connector

Waiting for input…

AI Agent

Why people use Incident.io

Incident.io for SRE Incident Response Automation

With this Connector, your AI agent becomes the central hub for that information. Instead of manual hunting, you can just ask for the current on-call schedule or a list of all high-severity incidents. It pulls that data instantly from the API, giving you a clear picture of the situation in seconds. You get to spend your energy fixing the bug, not searching for the right contact.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get a hands-free way to query and manage your incident response data.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    The 'Who's on call?' panic

    An engineer gets paged and asks the agent to check list_schedules for the database team to see who's active.

  2. Real-world use case 02

    The 'What's the status?' request

    A manager asks for a summary of all high-severity issues, and the agent uses list_incidents and list_severities.

  3. Real-world use case 03

    The 'Who is doing what?' check

    An Incident Commander asks the agent to list the roles for a specific incident to see if a comms lead is assigned.

Complete set · 10capabilities

The complete Incident.io capability set.

These are the exact actions your AI can choose when you ask it to work with Incident.io.

Capability set01 / 03

01—04

4 capabilities in this set.

Part of 10 available through Incident.io.

  1. 01 Capability

    Get incident

    Pull up the full details for a specific incident. This is useful for getting a deep dive into a single issue's history.

  2. 02 Capability

    List catalog types

    Shows all the defined catalog types in your system. Use this to see the categories of issues you're tracking.

  3. 03 Capability

    List custom fields

    Lists every custom field you've set up. This helps your agent know exactly what data points it can query for you.

  4. 04 Capability

    List incident roles

    Lists all the incident roles you've defined. It helps in understanding who needs to do what during a response.

Capability set02 / 03

05—07

3 capabilities in this set.

Part of 10 available through Incident.io.

  1. 05 Capability

    List incident types

    Shows all the incident types you use. This is great for categorizing and filtering ongoing issues.

  2. 06 Capability

    List incidents

    Lists all incidents currently in your system. Use this to get a high-level view of everything that needs attention.

  3. 07 Capability

    List schedules

    Lists all on-call schedules. This is the fastest way to see who's currently on the clock.

Capability set03 / 03

08—10

3 capabilities in this set.

Part of 10 available through Incident.io.

  1. 08 Capability

    List severities

    Lists all defined incident severities. This helps the agent understand the priority levels of different issues.

  2. 09 Capability

    List teams

    Lists all the teams in your organization. It helps in identifying the correct group to notify.

  3. 10 Capability

    List users

    Lists all the users in your system. Use this to verify who has access or is part of the response group.

Set up in minutes

One URL. Then ask Incident.io to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Incident.io from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_SYXytajPn2E8oSQTe6uxrJcvhwsU2x1pHkOPCe4y/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it Incident.io, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable Incident.io for the conversation.

Where the request belongs

Work Incident.io can move forward.

Built around the request

This is for the SRE or DevOps engineer who is tired of being the human router during an outage, constantly copy-pasting info from a dashboard to a Slack channel.

01

Site Reliability Engineer

Quickly identifies on-call schedules and incident severities to coordinate the right people.

02

Incident Commander

Tracks custom fields and roles to ensure every part of the response plan is being followed.

03

DevOps Manager

Monitors all active incidents and team status to provide high-level updates to stakeholders.

Build the capability set

Add more capabilities.

Each Connector adds new actions and data without changing how you work.

Browse Connectors
Better Stack logo
01 10 capabilities

Better Stack

Automate incident management via Better Stack. monitor uptime, manage incidents, and control on-call schedules securely from your AI agent.

View Connector
PagerDuty Incident Trigger logo
02 1 capability

PagerDuty Incident Trigger

This MCP does exactly one thing: it triggers incidents in PagerDuty. That's its only function, and nothing else. Incredible for giving your AI agents the power to wake up engineers.

View Connector
SigNoz (Datadog Alternative) logo
03 5 capabilities

SigNoz (Datadog Alternative)

Monitor infrastructure and manage alert rules via SigNoz. list, create, and update observability alerts directly from your AI agent.

View Connector
PagerDuty logo
04 11 capabilities

PagerDuty

Manage incidents, services, on-call schedules, and escalation policies via PagerDuty. trigger, acknowledge, and resolve alerts from any AI agent.

View Connector
Opsgenie logo
05 11 capabilities

Opsgenie

Automate incident management via Opsgenie. manage alerts, track on-calls, and coordinate incidents directly from any AI agent.

View Connector
Sentry logo
06 10 capabilities

Sentry

Grant your AI agent full access to Sentry's Application Performance Monitoring capabilities to track raw exceptions, resolve error logs, and inspect crash stack traces dynamically.

View Connector

Bring your own AI

Change the model, client or framework. Keep Incident.io connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about Incident.io.

The practical details behind the request, access and result.

Can the Incident.io MCP help me find out who is on call?

Yes, it pulls live schedules directly from your Incident.io account. This lets your agent tell you exactly who is responsible for a service in real time.

How does Incident.io MCP help with SRE workflows?

It automates the data retrieval part of incident response. Instead of clicking through dashboards, your agent can pull incident lists and severities instantly.

Can I use Incident.io MCP to see my team's roles?

Yes, it can list all defined incident roles. This helps ensure everyone knows their specific responsibilities during a response.

Does Incident.io MCP show me my custom incident fields?

It does. The Connector can list all defined custom fields, allowing your agent to understand and retrieve the specific data points your team tracks.

Can the Incident.io MCP list all active incidents at once?

Yes, it can fetch a full list of all incidents. This is great for getting a high-level overview of what's currently happening in production.

Is Incident.io MCP good for incident response coordination?

It's a great capability for coordination because it provides a fast way to query live data, like on-call schedules and team info, during a crisis.

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 Connector 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.

One connection away

Give your agent a direct line to Incident.io.

Connect Incident.io once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available