# incident.io MCP server

> Work with incidents, on-call schedules, alerts and follow-ups in incident.io from your AI assistant.

- Listing: https://mcp.tc/i/incident-io
- Connect: use the server's own URL `https://mcp.incident.io/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Observability & Incidents](https://mcp.tc/c/observability)
- Vendor: incident.io
- Homepage: <https://incident.io>

## About

Connects an AI assistant to incident.io, a software reliability platform covering on-call, incident response, investigations and status pages. The server gives access to incidents, on-call schedules, alerts and follow-ups in your incident.io organization.

It runs as a hosted streamable HTTP endpoint at https://mcp.incident.io/mcp. Users sign in with OAuth using their incident.io account. Nothing needs to be installed locally.

## What it can do

- Look up incidents in your incident.io organization
- Check on-call schedules and who is on call
- Review alerts
- Track incident follow-ups

## Example prompts

- "Show me the open incidents right now"
- "Who is on call for the platform team this week?"
- "List the follow-ups still open from last week's incidents"
- "What alerts fired in the last few hours?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http incident-io https://mcp.incident.io/mcp
```

2. Start Claude Code, type `/mcp`, pick **incident-io** and choose **Authenticate**. A browser window opens for the incident.io sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **incident.io** and paste this URL:

```url
https://mcp.incident.io/mcp
```

3. Click **Add**, then **Connect**, and sign in when incident.io asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=incident.io&connectorUrl=https%3A%2F%2Fmcp.incident.io%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.incident.io/mcp` and click **Add**.

3. Click **Connect** and sign in when incident.io asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.incident.io/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to incident.io to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=incident-io&config=eyJ1cmwiOiJodHRwczovL21jcC5pbmNpZGVudC5pby9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "incident-io": {
      "url": "https://mcp.incident.io/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=incident-io&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.incident.io%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"incident-io","type":"http","url":"https://mcp.incident.io/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "incident-io": {
      "type": "http",
      "url": "https://mcp.incident.io/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "incident-io": {
      "serverUrl": "https://mcp.incident.io/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add incident-io --url https://mcp.incident.io/mcp
codex mcp login incident-io
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.incident-io]
url = "https://mcp.incident.io/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http incident-io https://mcp.incident.io/mcp
```

Then, inside Gemini CLI, run `/mcp auth incident-io` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "incident-io": {
      "type": "http",
      "url": "https://mcp.incident.io/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.incident.io/mcp`.

## Details

- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/incident-io (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report