← Explore all mcp servers

INCIDENT OPERATIONS / incident.io

incident.io Remote MCP

Analyze incidents and alerts, inspect on-call schedules and manage incident and escalation workflows.

“Analyze incidents and alerts, inspect on-call schedules and manage incident and escalation workflows.”

01 / THE REASONING

Why this made the selection.

  • Analyze incidents and alerts, inspect on-call schedules and manage incident and escalation workflows.
  • The setup documentation makes this operating boundary explicit: OAuth acts as the consenting user; API keys act as service actors. Tools can acknowledge pages, change schedules and create or update incidents.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md
  • https://docs.incident.io/ai/remote-mcp

Our findings

  • OAuth acts as the consenting user; API keys act as service actors. Tools can acknowledge pages, change schedules and create or update incidents.
  • The prototype Go repository is superseded and unmaintained. Status-page tools draft updates but do not publish them; hosted access requires an eligible paid plan.

Not established by this review

  • No server installation, authentication, live tool execution or isolation test was performed.
  • Hosted implementation and deployment revision were not inspected; public connection documentation was reviewed.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Enable the remote server in Settings → MCP; connect https://mcp.incident.io/mcp and complete OAuth, or create a scoped API key for a service actor.
  2. Verify the connected account, available tools and target resource before authorizing mutations.

Before you start

  • A compatible remote HTTP MCP client.
  • OAuth acts as the consenting user; API keys act as service actors. Tools can acknowledge pages, change schedules and create or update incidents.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/incident-io/incidentio-mcp-golang/blob/a6b65421105c4ebc65bc7da6b55bdd1b236507dc/README.md

    Supports: description, setup, capabilities, review, limitations

  2. https://docs.incident.io/ai/remote-mcp

    Supports: description, install, access, limitations, bestFor, review

Evidence & Ask