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.
Give Claude and any AI agent real-world access
Your agent can pull a list of every current or historical incident recorded in the system.
It retrieves all defined on-call schedules, telling you exactly who is responsible for what time period.
The MCP accesses full lists of users and teams so your agent knows who reported the issue or who should be notified.
Your client can read predefined roles, severity levels, and catalog types to ensure proper classification when creating reports.
The agent pulls the full history and context for a single incident ID when you ask it to look up that specific case.
Ask an AI about this
Waiting for input…
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 MCPGet 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.
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
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
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
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.
019d75b8-fd34-7366-bcf0-c1bc53558e7f How to set up Incident.io MCP
The bottom line is your AI client gets all the necessary IT Ops data it needs from Incident.io without needing dozens of manual clicks across different dashboards.
Tell your AI client, 'Check on-call schedules for us.'
The MCP executes the list_schedules tool and gathers related context like defined incident roles.
Your agent compiles this data into a clean, summarized report that you can read or pass to another system.
Who uses Incident.io MCP
This MCP is for the Site Reliability Engineer (SRE) who's tired of jumping between ticketing systems, Slack channels, and on-call calendars during a major outage. It’s built for IT Operations Analysts and Incident Managers who need instant context to keep things moving fast.
Uses this MCP to automate incident triaging, pulling together the list of open incidents, checking which teams are responsible, and verifying if the correct severity level was assigned.
Relies on it to maintain a real-time overview of all active events. They use it to confirm who is currently on call and what roles need to be engaged for immediate response.
Uses the MCP to audit incident records, checking system metadata like custom fields or predefined catalog types before escalating an issue.
Benefits of connecting Incident.io MCP
You don't have to manually cross-reference roles with schedules. By using list_incident_roles and list_schedules, your agent instantly tells you which team owns an incident based on its type or severity, saving critical minutes during a crisis.
Stop switching between user directories and ticketing pages. The MCP’s ability to run list_users alongside get_incident means your AI client can immediately identify the reporter's contact info while simultaneously pulling up the full incident history.
Classification is key when time is short. You can check all predefined standards by calling list_incident_types, list_severities, and list_catalog_types. This ensures that every report you file uses consistent, accurate data points.
The MCP lets your agent pull a full picture of the environment. If you need to know what information is available for future reports, use list_custom_fields and list_teams to see exactly what metadata you can capture.
You get context on demand. Instead of having to search through endless dashboards, asking your agent to run list_incidents or get_incident gives you a filtered, summarized view of only the most relevant information right when you need it.
Incident.io MCP use cases
Triaging an unexpected alert
An employee gets paged at 3 AM. They ask their agent to 'What do I do about this?' The agent runs list_incidents, finds the specific ID, uses get_incident for details, then checks list_schedules to name the primary on-call engineer immediately.
Auditing incident data quality
A compliance team needs to verify that all recent incidents were correctly categorized. They ask their agent to run list_incident_types, compare it against the system's defined roles (list_incident_roles), and ensure no critical fields were missed using list_custom_fields.
Preparing a post-mortem report
After an outage, the manager asks their agent to pull all relevant data. The agent runs list_teams, compiles a list of involved users (list_users), and gathers incident metadata using get_incident to build a comprehensive timeline for stakeholders.
Verifying team access during an outage
A user can't access the dashboard. They ask their agent to list all active teams (list_teams) and cross-reference that with the incident roles (list_incident_roles) to figure out which department should handle the permission issue.
Incident.io MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Relying on dashboards alone
A human spends 15 minutes clicking through Incident.io's web UI, going from the 'Dashboard' to 'Schedules,' then searching for a specific 'User ID.' This is slow and prone to missing context.
Tell your agent directly: 'Who owns this incident?' The agent calls get_incident and automatically cross-references that with list_schedules and list_teams, giving you the answer in three seconds.
Manually correlating roles
A team member sees an alert for a 'Database Issue' but has no idea which role owns it. They must search through multiple wikis and internal emails to find out.
Ask your agent, 'What is the primary role for database incidents?' The MCP calls list_incident_roles immediately and tells you the correct responsible team.
Forgetting required context
Writing a manual report that misses key details because the person writing it isn't aware of all available metadata fields.
Ask your agent to check what data is available: 'What custom fields should I be tracking?' The MCP uses list_custom_fields and list_catalog_types to provide a complete list.
When to use Incident.io MCP
Use this MCP if your primary need is real-time, contextual data gathering during an active incident. If you constantly find yourself jumping between different Incident.io views—the user roster, the schedule page, and the incident timeline—this tool solves that coordination problem by giving your AI client a single API gateway to all those details.
Don't use this if you are building a highly complex data transformation pipeline that requires deep write access or conditional logic outside of simple read operations. If your goal is merely sending scheduled emails based on an incident status change, a dedicated messaging service MCP might be better suited. This MCP excels at reading and compiling information; it's not designed to manage the entire workflow state itself.
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.