Skip to main content
MCP server CX Codex

Incident.io — Claude Code MCP server: features and setup

Use an AI assistant to handle incidents, review alerts, check on-call schedules, and perform operational analysis with Incident.io.

no license updated 2026-10-29

Open on GitHub

What Incident.io does

Incident.io lets an assistant work with incidents, examine alerts, and look up on-call schedules. It also supports operational analysis. These tasks become available through requests to the assistant.

The server works with Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, and Gemini CLI. Checking the rota can help answer who is on call. Connect the server to a supported client to access these functions from its assistant.

What it helps with

  • review alerts tied to incidents
  • check who is on call
  • manage incidents through an AI assistant
  • run operational analysis

Example prompts for the agent

  • Check who is on call now.
  • Review the incident alerts and summarize the key points.
  • Help me analyze this operational incident.

How to install Incident.io

Install

The MCP registry has no launch command for it: see the repository README

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about Incident.io

How do I install Incident.io in Claude Code?

Connect the Incident.io MCP server to Claude Code. There is no installation command for this method.

What does Incident.io do?

It lets an AI assistant manage incidents, review alerts, check on-call schedules, and perform operational analysis.

Which clients work with Incident.io?

It works with Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, and Gemini CLI.

Similar MCP servers

All MCP servers for DevOps and infrastructure →

Project sponsors

Companies that keep this analytics open