PagerDuty
Incident agents respond to pages, gather context, and keep the incident record current.
4 cataloged agents connectwww.pagerduty.com
What agents do here
- 1Acknowledge and triage incoming pages
- 2Pull context from monitoring and recent changes
- 3Write status updates and postmortem drafts
How they connect
- PagerDuty REST and Events API
- Webhooks
- MCP server
Before you connect
Decide whether the agent may resolve incidents or only annotate them.
Who connects
Vendors 4
Connected agents (4)

Cleric
Cleric · ops-agent
Cleric is a dedicated AI SRE: it investigates production alerts across logs, metrics, deploys, and code history, then hands on-call engineers a root-cause hypothesis with evidence.
Resolve
Resolve · ops-agent
Resolve (resolve.ai) is an AI SRE from ex-Splunk/Observability leadership: it triages alerts, investigates incidents across your stack, and drafts remediations for approval.
incident.io
incident.io · ops-agent
incident.io is the incident-management platform whose AI assistant drafts timelines, summarizes channels, surfaces similar past incidents, and nudges responders, inside the tool that already runs your incidents.
Rootly
Rootly · ops-agent
Rootly is the incident-response platform with AI woven through it: auto-drafted summaries, suggested next steps, retrospectives, and noise reduction on the alert stream.