stackgate.ai
All integrations

Incident.io

Connect Claude, ChatGPT or Cursor to incident.io via MCP. Read incidents, updates, on-call schedules, and post-mortems with an API key.

Manual setup 8 tools

Example questions

Try asking your AI client

  • Which incident.io incidents are still open?

  • Did last night's checkout incident ever get a post-mortem?

  • Who is on call for Platform this weekend?

  • Write a draft timeline summary for Amalie - do not page anyone.

  • Which incidents this month were severity 1?

Overview

Connect incident.io so AI clients can read incidents, timeline updates, on-call schedules, severities, custom fields, and post-mortem summaries.

This integration is read-first. Declaring incidents, paging responders, or resolving incidents is not included.

Prerequisites

  • An incident.io organisation
  • Permission to create API keys (typically an owner or administrator)
  • A stackgate.ai account

Getting credentials

  1. Sign in to incident.io.
  2. Open Settings → API keys (https://app.incident.io/~/settings/api-keys).
  3. Create a key with viewer (or incidents.view plus schedules.view) permissions for the organisation you want to connect.
  4. Copy the token immediately. incident.io shows it once.
  5. In stackgate.ai, open My Integrations → Incident.io.
  6. Paste the API key and save. stackgate.ai calls /v1/identity to verify the key and store the organisation slug from the dashboard URL.
  7. Optionally use Edit tool access to keep the connection read-only.

See the incident.io API introduction.

Using with AI clients

  • Dedicated endpoint: POST /mcp/incident-io with a Sanctum bearer token
  • Private gateway: one config for all integrations - use incident-io__* namespaced tools

Example prompts:

  • "List active incidents in incident.io."
  • "Show incident INC-42 and its latest updates."
  • "Who is on call on the platform schedule?"
  • "List post-mortems still in review."

Troubleshooting

  • 422 integration not configured - complete the API key form in My Integrations.
  • 401 Unauthorized - create a new API key in incident.io and update My Integrations.
  • 403 Forbidden - the key is missing incidents.view or schedules.view. Create a viewer key for that organisation.
  • 429 Too many requests - list and show incident endpoints allow 60 requests per minute. Retry after a short delay.
  • Empty post-mortems - list_postmortems returns document metadata only. Open the document_url in incident.io for the full write-up.

Security and revocation

Disconnect in My Integrations to delete the stored key from stackgate.ai. Also revoke the key under Settings → API keys in incident.io. Credentials are encrypted at rest. Tool calls are audit logged as metadata (tool name and status), not raw incident payloads.

Available tools

  • list_incidents

    List incidents for the connected organisation. Supports status, status category, and severity filters plus cursor pagination.

  • get_incident

    Get a single incident by ID, including status, severity, roles, and custom field entries.

  • list_incident_updates

    List timeline updates for an incident (status changes, commander notes, and merge events).

  • list_schedules

    List on-call schedules for the organisation.

  • get_schedule

    Get a single on-call schedule by ID, including rotations and current coverage when returned by the API.

  • list_severities

    List severity levels configured for the organisation.

  • list_custom_fields

    List custom field metadata (IDs, names, types) used on incidents.

  • list_postmortems

    List post-mortem documents (summaries) for the organisation. Returns metadata and document URLs, not full Markdown content.

MCP endpoint: https://stackgate.ai/mcp/incident-io (HTTP) or via the private gateway.

Create account Documentation