Monitoring

Incident.io MCP Server

Use Studio chat to drive this server — credentials stay in your workspace.

Incident.io provides a source connector for Airbyte to synchronize incident and operational data using the Incident.io API, enabling efficient tracking and resolution of incidents. It is primarily used for operational monitoring and incident response management.

14 tools
Agent guide included
API Key
Start Chatting

Opens MCPBundles Studio with this server selected. After sign-in, chat and run tools from the same thread.

Browse all tools

AI Skill
SKILL.md

Domain knowledge for Incident.io — workflow patterns, data models, and gotchas for your AI agent.

Incident.io

Incident.io provides incident and operational data APIs for tracking and resolving incidents. It is used for operational monitoring and incident response management.

Data Model

  • Actions — actions that can be triggered during incidents.
  • Alerts — incoming alerts that may create incidents.
  • Catalog Types — catalog item types (e.g. runbooks).
  • Custom Fields — custom attributes on incidents.
  • Follow Ups — post-incident follow-up tasks.
  • Incident Roles — roles (e.g. incident commander) on incidents.
  • Incident Statuses — status definitions (investigating, resolved, etc.).
  • Incident Timestamps — milestone timestamps.
  • Incident Updates — status updates and timeline entries.
  • Incidents — incident records.
  • Schedules — on-call schedules.
  • Severities — severity levels.
  • Users — team members.
  • Workflows — automation workflows.

Tools in this Server (14)

Incident List Actions

Retrieve a list of available actions for incidents, enabling effective action tracking and management. Use this when you need to see all possible acti...

Incident List Alerts

List all alerts generated for incidents, providing crucial insights for proactive monitoring and alert management. Ideal for teams needing to review c...

Incident List Catalog Types

Fetch a list of catalog types associated with incidents to understand categorization and classification. Ideal for reviewing and managing catalog type...

Incident List Custom Fields

Get a list of custom fields configured for incidents, aiding in personalized incident tracking. Use when needing to view and manage customized data po...

Incident List Follow Ups

List follow-up actions scheduled after incidents to ensure complete resolutions. This is used when tracking post-incident activities or when auditing ...

Incident List Incident Roles

Obtain a list of incident roles to define responsibilities during incident management. Use when setting up or reviewing role assignments for incident ...

Incident List Incidents

Retrieve a list of all incidents currently tracked in Incident.io. This is useful for real-time incident monitoring and historical data analysis. It r...

Incident List Incident Statuses

Get a list of possible statuses an incident can have, ensuring clarity in tracking incident positions. This is useful for understanding and configurin...

Incident List Incident Timestamps

Retrieve timestamps related to incidents to track key event occurrences during incident management. Use for auditing and reviewing incident timelines....

Incident List Incident Updates

Gather a list of updates for incidents, helping in tracking progress and changes over time. Use this when needing a historical view of actions and upd...

Incident List Schedules

Fetch a list of operational schedules relevant to incident response management. Use this to view and manage on-call rotations and scheduling patterns....

Incident List Severities

Retrieve a list of incident severities defined in your Incident.io account. Use this tool when you need to understand the categorization of incidents ...

Incident List Users

Fetch a list of users involved in incident management to understand personnel assignments. Useful for reviewing access and role allocation in incident...

Incident List Workflows

List available workflows associated with incidents, aiding in streamlining resolution processes. Use when defining or evaluating the workflow processe...

Frequently Asked Questions

What is the Incident.io MCP server?

Incident.io provides a source connector for Airbyte to synchronize incident and operational data using the Incident.io API, enabling efficient tracking and resolution of incidents. It is primarily used for operational monitoring and incident response management. It provides 14 tools that AI agents can use through the Model Context Protocol (MCP).

How do I connect Incident.io to my AI agent?

Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/incident. Authentication is handled automatically.

How many tools does Incident.io provide?

Incident.io provides 14 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.

What authentication does Incident.io require?

Incident.io uses API Key. Incident.io requires credentials. Connect via MCPBundles and authentication is handled automatically.

Setup Instructions

Connect Incident.io to any MCP client in minutes

https://mcp.mcpbundles.com/bundle/incident

What is MCP?

Model Context Protocol lets AI tools call external capabilities securely through a single URL. This bundle groups tools behind an MCP endpoint that many clients can use.

Use this bundle in 3 steps

  1. Copy the MCP URL above
  2. Open your AI tool and add a new MCP/connector
  3. Paste the URL and follow any auth prompts

Claude Desktop Users

Skip the manual setup! Use the .mcpb file format for one-click installation. Check the Claude Desktop tab for setup instructions.

Pick your tool tab for exact steps

Select ChatGPT, Cursor, Claude Code, or another tab for copy-paste config.

Ready to chat with Incident.io?

Same flow: Studio opens on this server after sign-in. Keep chatting to call tools from the conversation.

Incident.io MCP Server & Skill — 14 Tools