See and manage everything in incident.io
Manage your full incident.io workspace from one place. Declare and triage incidents, ack pages, check who's on call, and track follow-ups - without switching tools. More
MCP connector Server URL https://mcp.incident.io/mcpCopy Login OAuth Tools Reads data89 action_ alert_ alert_ alert_ alert_ alert_ alert_ analysis_ catalog_ catalog_ catalog_ change_ change_ chat_ chat_ code_ code_ cover_ custom_ dashboard_ dashboard_ document_ document_ duration_ escalation_ escalation_ escalation_ escalation_ escalation_ extension_ extension_ extension_ extension_ extension_ external_ external_ follow_ follow_ glossary_ help_ incident_ incident_ incident_ incident_ insights_ insights_ insights_ insights_ insights_ investigation_ kubernetes_ kubernetes_ kubernetes_ log_ log_ maintenance_ maintenance_ memory_ metric_ nexus_ notification_ postmortem_ postmortem_ postmortem_ postmortem_ profile_ profile_ profile_ read_ resource_ resource_ schedule_ schedule_ skill_ skill_ span_ span_ sql_ sql_ sql_ sql_ suggestion_ team_ team_ telemetry_ telemetry_ time_ trace_ user_
Changes data26 action_ alert_ alert_ cover_ custom_ extension_ extension_ extension_ extension_ feedback follow_ glossary_ glossary_ incident_ insights_ insights_ insights_ insights_ insights_ investigation_ maintenance_ maintenance_ notification_ postmortem_ schedule_ status_
Deletes or can't be undone30 action_ action_ action_ alert_ alert_ alert_ alert_ ask cover_ cover_ escalation_ escalation_ extension_ extension_ follow_ glossary_ incident_ incident_ incident_ incident_ incident_ insights_ investigation_ investigation_ maintenance_ notification_ notification_ notification_ postmortem_ schedule_
Skills 10 in the ChatGPT listing
architecture Answer questions about how the organisation builds, deploys, and runs its software — what a system is, where it runs, what it depends on, and the real names of things (cloud projects, clusters, namespaces, hostnames, buckets) — from architecture docs wherever they live. Architecture author Write and maintain architecture docs — the documents that say what each system is, where it runs, what it depends on, and the real names of things (cloud projects, clusters, namespaces, hostnames, buckets). doctor Review the health of your incident.io agent estate — plugins, skills, connections — and say what to fix, without fixing anything itself. extensions Set up, explain and troubleshoot incident.io extensions: the plugins of skills and the connectors (MCP servers, HTTP APIs) that give incident.io's agents an organisation's own knowledge and tools. incidents Reading and changing incidents in incident.io: status, severity, roles, fields, updates, channel messages and the AI investigation. On call Who is on call in incident.io and how they get paged: schedules, rotas and shifts, overrides, cover requests, escalation paths, and pages (escalations). postmortem Work with an incident's postmortem document — the write-up a team produces after an incident. Skill authoring Create and improve the skills in your own plugins — the ones incident.io's agents and your coding agents load. Talking to the user How the incident.io skills speak to the person in the session: what the user hears and what goes in the record, ending each reply with one next step, keeping a fixed milestone list through a multi-step job, and using the user's words instead of the skills' own vocabulary. telemetry Query an organization's observability data — logs, metrics, traces, profiles, dashboards, Kubernetes, SQL databases — with the incident.io telemetry tools. 
Railway#162
Datadog#35
Sentry#39
Cloudflare Developer Platform#45