incident-io

Makes your agent fluent in incident.io: responding to and investigating incidents, working with on-call schedules and escalations, and authoring the operational content — runbooks, skills, and plugins — that incident.io investigations draw on.

The plugin bundles the official incident.io MCP server (https://mcp.incident.io/mcp), so installing it connects your agent to your incident.io workspace through a standard OAuth flow the first time a tool is used.

Run these skills on Opus/Sol level or higher. Smaller models follow their workflows unreliably.

Skills

Skill	What it does
architecture	Answers questions about how your systems are built, deployed and run, using your architecture docs.
architecture-author	Interviews you to write and maintain the architecture docs that say what each system is, where it runs and what it depends on.
doctor	Reviews the health of your setup: sync failures, skills that load but don't get followed, and feedback worth acting on. It reports what to fix and never edits anything.
extensions	The place to start. Reads your current plugins and connectors, works out whether a plugin or a connector solves your problem, scaffolds and registers a plugin, then hands off to the skill that owns the rest.
on-call	Shows who is on call, manages overrides and cover requests on your schedules, and pages people and checks whether a page reached them.
skill-authoring	Writes new skills from your team's knowledge, verifies them before they ship, and improves existing skills from the usage feedback we record.
talking-to-the-user	Sets how the incident.io skills talk to you, including one clear next step at the end of each reply.
telemetry	Queries your logs, metrics, traces, dashboards and databases to find evidence for an answer.

Connections

Every connection these skills call, and where it comes from in each environment:

Connection	Coding agent on your machine	incident.io hosted agents
incident.io	The bundled MCP server (.mcp.json), authenticated over OAuth on first use	Native tools with the same capabilities

Skills may also use provider tools the session already has (a Notion search, a wiki search) — those are the session's, not dependencies of this plugin.

Where your content lives

This plugin carries incident.io's guidance, not your content. Runbooks, architecture notes, and other operational knowledge belong in your own repositories, where they live next to the code they describe and are reviewed like it. The skills here help you write that content well and keep it current.

Privacy

This plugin connects to your incident.io account through the bundled MCP server. See the incident.io privacy policy.