incident.io plugin

incident.io's own plugin for coding agents. It bundles incident.io's agent skills with its official remote MCP server, so your agent can work with incidents, on-call and postmortems in your incident.io workspace, and help you write the runbooks, architecture docs and skills that incident.io investigations draw on. What its skills cover - Incidents: read and update status, severity, roles, custom fields and updates, and look back at past incidents - On-call: see who is on call, manage overrides and cover requests, and page people and check the page reached them - Postmortems: find, read, edit and review them, checking their claims against what actually happened - Your catalog and architecture: who owns a service, what it depends on, and how your systems are built, deployed and run - Telemetry: query logs, metrics, traces, dashboards and databases for evidence - Extensions: scaffold and register incident.io plugins, write and verify skills, and review the health of your setup How to install it In Claude Code, run /plugin install incident-io@claude-plugins-official, or add incident-io/skills as a marketplace and install incident-io from it. In Claude Desktop it's under Customize, then Plugins. It's also in Cursor's marketplace and the ChatGPT plugin directory for Codex, installs in VS Code with Chat: Install Plugin From Source, and adds to GitHub Copilot CLI from the incident-io/skills marketplace. The MCP server It includes incident.io's remote MCP server at mcp.incident.io/mcp. It asks you to sign in to incident.io the first time a tool is used, and acts as you, seeing what you'd see in the dashboard. The remote MCP server is on incident.io's Team, Pro and Enterprise plans, not the free Basic plan, and is turned on under Settings, then MCP. Good to know - incident.io recommends running these skills on a top model such as Claude Opus; smaller models follow them less reliably. - The doctor skill reports what to fix in your setup and never edits anything. - Status page updates are only drafted; a person reviews and publishes them. - The plugin carries incident.io's guidance, not your content: runbooks and architecture docs stay in your own repositories.

• “Who's on call for the platform team right now?”

  Copy

• “Show me INC-123 with the investigation findings and postmortem.”

  Copy

• “Update INC-123 to resolved.”

  Copy

• “Review the postmortem for INC-456 against what actually happened.”

  Copy

• “Help me get started with incident.io extensions.”

  Copy

• “Create a new plugin, then interview me to write our architecture docs.”

  Copy