For the complete documentation index, see llms.txt. This page is also available as Markdown.

incident.io

Connect incident.io to analyze operations and manage incidents from Agent Mode

Connect incident.io to investigate incident history, alerts, on-call coverage, and service ownership, then take response and follow-up actions.

This connector is for Agent Mode. To send monitor notifications to incident.io, configure an incident.io Destination.

What You Can Do

Read and investigate

Show incidents affecting the payments service in the last 30 days and summarize recurring root causes and outstanding follow-ups.

Who is on call for platform right now, and which alerts caused the most overnight responder work this month?

Take action

Declare a high-severity incident for the checkout degradation shown in this investigation and include the affected service and evidence.

Acknowledge the page for this incident, update its status and severity, and create follow-ups for the remediation items we identified.

Available tools include incident and escalation management as well as alert, schedule, catalog, and investigation analysis.

Setup

  1. An incident.io admin enables Settings → MCP in incident.io.

  2. A groundcover workspace admin goes to Integrations → Connectors → Org Connectors, selects incident.io, and enables it.

  3. The admin clicks Connect, completes OAuth, and reviews the tool restrictions.

  4. Each user goes to Integrations → Connectors → My Connections, selects incident.io, and clicks Connect.

  5. Complete the incident.io OAuth flow.

Agent Mode acts with the connected user's incident.io permissions, subject to groundcover's tool restrictions. Write actions may require approval. incident.io OAuth access expires periodically, so users may need to authorize again.

Last updated