IntegrationsPagerDuty integration
Paged at 2 a.m.?Start with the timeline.
Connect PagerDuty to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent reads incidents, alerts, on-call schedules, services and change events, and builds a timeline for whoever is paged. CoreSpeed proxies PagerDuty's own hosted MCP server with your User API Token, and acknowledging, resolving or adding a note is a separate call approvals can hold.
From the pageto the person who fixes it.
Requests you can make once PagerDuty is connected. The data is fictional.
- PagerDutyIncidents · high urgency
- #4182Checkout API error rate above 5%Triggered
- #4179Search latency above SLOAcknowledged
- #4171Nightly export job failedResolved
See what is paging
Read only · Nothing acknowledged
- PagerDutySchedules
Platform primary · this week
- On call now: Reid, until Monday 9:00.
- Then Mira, through Friday.
- Escalates to Parker after 15 minutes.
Find who is on call
From the schedule, on request
Approval requestWaiting
Claude Code for Drew
pagerduty__manage_incidents
“Resolve #4182 and add the timeline as a note.”
Policy: Ask before changing any PagerDuty incident.
ApproveDeny
Hold the resolve
Ask
Read the incident.Find the change behind it.
Have your agent read the open incident, line it up with recent change events, and name who is on call. You get the brief before anyone acts.
Reads fromPagerDuty
All connectors →List the triggered high-urgency incidents in PagerDuty. For the checkout one, read the recent change events and tell me who is on call. Do not acknowledge anything.
pagerduty__browse_incidentsok
1 triggered, high urgency
Keep your agent.Bring your work.
One CoreSpeed account, across compatible agents.
- 1
Set up CoreSpeed
Give your agent the setup line. It adds CoreSpeed and signs you in.
- 2
Connect PagerDuty
Paste an API key from your PagerDuty dashboard.
- 3
Start with one task
Ask for a summary, a brief, or a draft. Review the answer.
Setup guidesClaude CodeCodexCursor