incident.io MCP Connector
Connect Sazabi to incident.io through MCP to browse incidents, alerts, and on-call schedules.
The incident.io MCP connector lets Chat browse incidents, alerts, and on-call information. This provides valuable context during investigations by letting Chat see related incidents and runbooks.
About the incident.io MCP connector
The incident.io MCP connector gives Chat read-only access to your incident.io account. With this connector, Chat can:
- Browse incidents and their timelines
- View alerts and on-call schedules
- Access runbooks and playbooks
- Review incident history and details
Prerequisites
Before connecting incident.io via MCP, make sure you have:
- A Sazabi account with admin permissions.
- An incident.io account with API access.
Connecting incident.io
Open MCP Connectors
Go to Settings -> MCP Connectors in the Sazabi dashboard.
Select incident.io
Find incident.io in the list of available connectors and click Connect.
Authorize access
You will be redirected to incident.io to authorize Sazabi. Review the requested permissions and click Authorize.
Verify connection
After authorization, you will be returned to Sazabi. The incident.io connector should show as connected with available tools listed.
Available tools
Once connected, the incident.io MCP connector provides read-only tools to Chat for:
- Browsing incidents and timelines
- Viewing alerts and on-call schedules
- Accessing runbooks
- Reviewing incident history
Usage examples
With the incident.io MCP connector, you can ask Sazabi to:
Show me recent incidents
What does the runbook say about database failover?
Who is on call for the backend team?
Find incidents related to the payment serviceTroubleshooting
Connection failed
If the OAuth flow fails:
- Verify you have API access enabled in incident.io.
- Check that your incident.io plan supports API integrations.
- Try disconnecting and reconnecting.
Cannot access incidents
If incident access fails:
- Verify the incident.io connector is still connected.
- Check that you have permission to view incidents.
- Try disconnecting and reconnecting to refresh access.