Skip to main content

incident.io

incident.io appears twice in the catalog, and the two entries do different things:

  • incident.io with an Official badge — this page. incident.io's own hosted MCP server, connected over OAuth.
  • incident.io with a By Willow badge — the built-in connector, connected with an incident.io API key.

Which one do you want​

If you needUse
An agent to change on-call config — edit an escalation path or schedule, or create an overrideBy Willow connector
Anything incident.io's server does that their public API does not expose, such as their AI and investigation featuresOfficial server
Incident, alert, escalation, and catalog readsEither

The official server's on-call surface is read-only, which is the gap the Willow connector was built to close. Running both is fine and reasonably common: the reads overlap, and each one covers something the other cannot.

note

The Willow connector is built on incident.io's public REST API, so it can only offer what that API exposes. Their MCP server additionally surfaces capabilities it computes itself, which no connector can reproduce — for those, the official server is the only route. Check their MCP documentation for the current list, since it changes on their side.

Setting up​

  1. In Willow, go to MCP Servers → + Add MCP server and find the incident.io card with the Official badge.

  2. Click + Use, then complete the OAuth prompt as an incident.io user with access to the data you want the agent to reach.

The endpoint is https://mcp.incident.io/mcp over HTTP. Willow registers itself with incident.io automatically, so there is no app to create first — unlike the API key the built-in connector needs.

tip

Because this server authenticates per user over OAuth, incident.io attributes actions to the person who connected. The built-in connector uses a shared API key, so incident.io attributes its actions to the key. Worth keeping in mind when you are deciding which one an audit trail should run through.

Additional Resources​

On this page