# Incident.io MCP > 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. ## Overview - **Category:** collaboration - **Price:** Free - **Tags:** incident-response, sre, on-call-scheduling, workflow-automation, alerting, team-coordination ## Description 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. ## Tools ### 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. ## Prompt Examples **Prompt:** ``` List all ongoing incidents in Incident.io. ``` **Response:** ``` I'll fetch the list of current incidents for you. ``` **Prompt:** ``` Show me the on-call schedules for this week. ``` **Response:** ``` I'll retrieve the active on-call schedules from Incident.io. ``` **Prompt:** ``` Check the details for incident ID 'abc-123'. ``` **Response:** ``` I'll look up the full details and history for that specific incident. ``` ## Capabilities ### 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. ## 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. ## Benefits - 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. ## How It Works 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. 1. Tell your AI client, 'Check on-call schedules for us.' 2. The MCP executes the `list_schedules` tool and gathers related context like defined incident roles. 3. Your agent compiles this data into a clean, summarized report that you can read or pass to another system. ## Frequently Asked Questions **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.