incident.io
Give the Sazabi agent tools to browse incidents, alerts, and on-call schedules from your incident.io organization.
About
incident.io is an MCP connector that gives the Sazabi agent tools to browse incidents, alerts, and on-call schedules. incident.io hosts an MCP server at https://mcp.incident.io/mcp and authenticates via OAuth with dynamic client registration — you approve access once in the browser and Sazabi stores the token. Because incident.io's authorization server does not issue refresh tokens, the connection expires after approximately 28 days and requires reconnection.
What the agent can do:
- Browse active and historical incidents
- View alert policies and firing alerts
- Check on-call schedules and escalation paths
- Search incident timelines and postmortems
Prerequisites
- An active incident.io account
- Responder or higher role in your incident.io organization
- An incident.io admin to open the bottom-left gear menu, choose MCP Server, and add
app.sazabi.comto your allowed redirect domains; otherwise authorization fails with a 404
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find incident.io in Settings > MCP connectors.
Authorize
Start the connection; Sazabi redirects you to incident.io to authorize, then back. Confirm your incident.io admin has already added app.sazabi.com to the MCP Server allowed redirect domains before starting.
Set up with the CLI
You can also connect incident.io with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).
incident.io authenticates over OAuth, so the CLI opens a browser to complete authorization:
sazabi mcp-connectors connect incident-ioAdd --read-only to restrict the connector to read-only tools, or --project-id <project> to target a specific project. In --json mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the connection is authorized (OAuth) or the key/header is correct (token auth).
Troubleshooting
No tools discovered — Disconnect and reconnect from Settings > MCP connectors; confirm app.sazabi.com is in the incident.io MCP Server allowed redirect domains.
Connection shows needs attention — The authorization token may have expired (incident.io tokens last approximately 28 days with no automatic refresh); reconnect from Settings > MCP connectors.