incident.io

Claude Code

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

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

1. 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:

https://mcp.incident.io/mcp

1. 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:

Añadir a claude.ai (se abre en una pestaña nueva)

1. Check that the URL reads https://mcp.incident.io/mcp and click Add.
2. 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

Añadir a Cursor (se abre en una pestaña nueva)

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

{
  "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 (se abre en una pestaña nueva)

Or from a terminal:

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

Or commit it to the repo in .vscode/mcp.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):

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

1. 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

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

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

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

Gemini CLI

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.

{
  "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.

Insignia para README

[![incident.io on mcp.tc](https://mcp.tc/i/incident-io/badge.svg)](https://mcp.tc/i/incident-io)

<a href="https://mcp.tc/i/incident-io"><img src="https://mcp.tc/i/incident-io/badge.svg" alt="incident.io on mcp.tc" height="20"></a>

Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.

Tarjeta para web

<script src="https://mcp.tc/w/incident-io.js" async></script>

La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala cookies.

iframe

<iframe src="https://mcp.tc/embed/incident-io" title="incident.io on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.

JSON

La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, la URL propia del servidor, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).

https://mcp.tc/i/incident-io.json

Qué significa cada campo