Language:JapaneseEnglish

incident-io Claude Code Plugin

Author
incident.io
Category
Monitoring
Topics
Monitoring & Observability · Project Management & Collaboration
First cataloged
2026-09-18 (UTC)
Explanation last updated
2026-10-14 (UTC)
Source (GitHub) last updated
2026-10-15 (UTC) (today)

The explanation below is AI-generated. Please verify it against the sources.

This is a Claude plugin that connects the assistant to incident. io, a platform for managing software incidents and on-call operations. It bundles the official incident. io MCP server, which authenticates through OAuth the first time a tool is used, giving the assistant access to a workspace's incident, on-call, and documentation data. It also includes a skill that reviews the health of the plugin setup itself. The plugin does not store a team's operational content; that content is expected to remain in the team's own repositories.

About the service

incident.io is a cloud-based software reliability and incident management platform. According to its homepage, it combines on-call routing, AI-assisted incident investigation, incident response coordination, and customer-facing status pages, drawing on a model it calls Nexus that is built from an organization's incidents, systems, and telemetry. Customers mentioned on the page include large engineering organizations using it to coordinate incident response and communicate status to users.

What you can do with incident-io

  • Read and update incidents: status, severity, roles, custom fields, and look back at incident history
  • Check who is on call, manage schedule overrides and cover requests, and page people while confirming the page was received
  • Get answers about how systems are built, deployed, and run from existing architecture documentation
  • Walk through an interview process to write and keep architecture documentation current
  • Find, edit, and review postmortem documents, comparing their claims against what actually happened
  • Query logs, metrics, traces, dashboards, and databases to gather evidence for an incident investigation
  • Write new skills from team knowledge and refine existing ones using recorded usage feedback
  • Check the health of the plugin/connector setup, including sync failures, without making changes itself
  • Scaffold and register new plugins or connectors and hand off to the skill that should own the task
  • Configure how responses are phrased, including ending each reply with a clear next step

Sources

History of incident-io

  • Claude Code Plugin Added incident-io

Back to list