Is this an official incident.io MCP server?

No. It is Memtro's MCP server with Memtro's incident.io connector behind it: the connector reads incident.io through its API with the credentials you connect on Dashboard → Connections, and incident.io publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in incident.io?

Not yet. Today every incident.io tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Engineering and operations

incident.io MCP server

incident.io in any MCP client, through Memtro: incident.io does not publish this server. Memtro's incident.io connector reads incident.io through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only incident.io: incidents with severity, status, roles and timeline, follow-ups and actions, on-call schedules and who is on now, and the user directory.

Reads

incidentio_incidentsList incident.io incidents, newest first: filter by status category (triage, live/active, learning/post-incident, paused, closed, declined, canceled…
incidentio_incidentOne incident by id or reference (INC-123) in full: summary, roles, every timestamp, the update log and timeline (newest last)…
incidentio_follow_upsFollow-ups across incidents (default: outstanding ones), optionally for one incident id or filtered by assignee name/email.
incidentio_oncallOn-call schedules: who is on call right now (and next) per schedule.
incidentio_usersIncident.io users (responders): name, email, role.

Connect it

First connect incident.io on Dashboard → Connections, then add Memtro to your client once. The incident.io tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared incident.io connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Which incidents are live right now and who is leading them?
› Summarise INC-412 with its timeline
› What follow-ups are still outstanding from last month's incidents?
› Who is on call for the platform schedule tonight?
› How many major incidents did we have this quarter and how long did they take to resolve?
› Which incidents mention the payments database?

Questions

Is this an official incident.io MCP server?: No. It is Memtro's MCP server with Memtro's incident.io connector behind it: the connector reads incident.io through its API with the credentials you connect on Dashboard → Connections, and incident.io publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in incident.io?: Not yet. Today every incident.io tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.