Vinkius

Incident.io MCP. Map who is on call and what the issue is.

Incident.io connects your AI client directly to incident response data. Use this MCP to automatically list open incidents, check on-call rotations, and map required roles and teams instantly. It lets you manage the entire lifecycle of an outage—from initial alert to resolution report—without leaving your agent's chat window.

Incident.io MCP is compatible with Claude Claude
Incident.io MCP is compatible with ChatGPT ChatGPT
Incident.io MCP is compatible with Cursor Cursor
Incident.io MCP is compatible with Gemini Gemini
Incident.io MCP is compatible with Windsurf Windsurf
Incident.io MCP is compatible with VS Code VS Code
Incident.io MCP is compatible with JetBrains JetBrains
Incident.io MCP is compatible with Vercel Vercel
See Vinkius in Action

Give Claude and any AI agent real-world access

List all active incidents

Your agent can pull a list of every current or historical incident recorded in the system.

Determine on-call coverage

It retrieves all defined on-call schedules, telling you exactly who is responsible for what time period.

Gather team and user context

The MCP accesses full lists of users and teams so your agent knows who reported the issue or who should be notified.

Map incident parameters

Your client can read predefined roles, severity levels, and catalog types to ensure proper classification when creating reports.

Check specific incident details

The agent pulls the full history and context for a single incident ID when you ask it to look up that specific case.

Waiting for input…

AI Agent
Incident.io

What AI agents can do with Incident.io: 10 Incident Management Tools

These tools let your agent read all the core data from Incident.io, giving you complete context on incidents, users, teams, and scheduling.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Incident.io MCP

Get Incident

Pulls full details and history for a single specified incident.

List Catalog Types

Retrieves all defined types of catalog information used by the system.

List Custom Fields

Lists every custom field available for incident documentation.

List Incident Roles

Shows all predefined roles that can be assigned during an incident response.

List Incident Types

Retrieves a list of standard incident classifications used across the platform.

List Incidents

Pulls a comprehensive list of all incidents recorded in the system, active or closed.

List Schedules

Displays all configured on-call rotations and schedules for teams.

List Severities

Lists the defined levels of severity that can be assigned to an incident.

List Teams

Retrieves a list of all internal teams within the organization.

List Users

Pulls a directory of every user account associated with Incident.io.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Incident.io MCP is compatible with Claude

Claude AI

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

3

Start a conversation

Open a new chat. The Incident.io integration is available immediately — no restart needed.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on each call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Incident.io, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 5,200+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Connections are secured and governed automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog weekly
Incident.io MCP server cover

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.

VINKIUS CLOUD

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on each call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Incident responses used to feel like a scavenger hunt.

When something breaks, finding out who owns the problem or who can fix it is hell. You open Incident.io's dashboard, then you have to click over to check the team roster. Then you jump again to see who’s on call this week. You end up bouncing between three different screens and copying names back and forth into your notes.

With this MCP connected through Vinkius, you simply ask your agent: 'Who's responsible for the main database service right now?' The agent runs multiple background checks—checking roles, schedules, and teams—and hands you one clean answer. It turns a 10-minute manual process into an immediate chat response.

Incident.io MCP: Instant context on every alert.

You no longer need to manually check the incident details, then switch tabs to look up the relevant user ID, and finally open another document to see what severity level that user normally handles. The agent pulls all three pieces of data together in one go.

The result is pure speed. You get a single source of truth for everything happening during an outage. It's not just about getting information; it's about accelerating the moment you need context the most.

What Incident.io MCP does for your AI

Managing a major outage means juggling multiple dashboards: one for active alerts, another for team contact info, and yet a third just for who is currently on call. This MCP lets your AI client pull all that information together in a single request. You can ask your agent to find every open incident, check which roles are defined, or verify the current on-call schedule—all through one chat command.

It's built specifically for SRE and IT Ops teams who need fast context during a crisis. If you connect this MCP via Vinkius, your AI client instantly gains access to Incident.io’s full API suite. You can get incident details, list all available users and teams, or check the system's predefined incident types.

This means automating complex workflows—like triaging an alert and knowing exactly who needs to jump on it—is routine, not complicated.

Built · Hosted · Managed by Vinkius Incident.io MCP - Manage Incident Response Workflow
Server ID 019d75b8-fd34-7366-bcf0-c1bc53558e7f
Vinkius Inspector
Compliance Grade A+
Score 100/100
Vinkius Inspector Badge — Score 100/100

Frequently asked questions about Incident.io MCP

Can Incident.io MCP list all open incidents? +

Yes, the list_incidents tool lets your agent pull a comprehensive list of every incident recorded in the system, whether it's active or closed.

How do I find out who is on call using Incident.io MCP? +

You use the list_schedules tool. This allows your agent to check all configured rotations and tell you exactly which team members are covering duty right now.

Does the MCP help me find user details for a specific incident? +

Yes, after getting an incident ID via get_incident, your agent can cross-reference it with list_users to pull up contact or team information about involved parties.

What kind of metadata can I retrieve using Incident.io MCP? +

You can read all the system's standards, including predefined incident types (list_incident_types), severity levels (list_severities), and custom data fields (list_custom_fields).

Can Incident.io MCP list all available teams? +

Absolutely. The list_teams tool gives your agent a full roster of every team in the organization, which is useful for reporting and assignment.