# Paged at 2 a.m.? Start with the timeline.

Source: https://corespeed.io/integrations/pagerduty

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.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect PagerDuty after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## 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.

You ask your agent: "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."

It calls CoreSpeed:

- `pagerduty__browse_incidents`: ok, 486 ms
- `pagerduty__browse_change_events`: ok, 412 ms
- `pagerduty__browse_schedules`: ok, 377 ms

It reads from: PagerDuty.

### Incident brief: #4182 started after a deploy.

The checkout error rate rose 6 minutes after a deploy to the checkout service. Reid is on call and has not acknowledged yet.

**Timeline**

- 02:41 Deploy to checkout, from the change events.
- 02:47 First alert, error rate above 5%.
- 02:52 Incident still triggered, no responder yet.

**Still open**

- Whether to roll back the deploy or page Parker.

_Illustrative incident and schedule · Nothing changed in PagerDuty_

All connectors: https://corespeed.io/docs/connectors

## From the page to the person who fixes it

Requests you can make once PagerDuty is connected. The data is fictional.

### See what is paging

Triggered and acknowledged · High urgency, all your teams

- Triggered: Checkout API error rate
- Acknowledged: Search latency above SLO
- Read only · Nothing acknowledged

### Find who is on call

Platform primary · Schedules and escalation policies

- On call now: Reid, until Monday 9:00
- Next: Mira
- From the schedule, on request

### Hold the resolve

A change, waiting · CoreSpeed approvals

- Tool: Manage incidents
- Rule: Ask before changing an incident
- Ask

Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md)

## 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 guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### What do I connect PagerDuty with?

A User API Token from your PagerDuty profile. Account-level keys are refused, and access follows that user's role.

### Can my agent change incidents?

Yes, with a read-write token. Creating, acknowledging, resolving or adding a note goes through separate manage calls, which approvals can hold for a person.

### Does it work with an EU PagerDuty account?

Not today. CoreSpeed connects to PagerDuty's hosted server for the US service region, so the token must come from a US account.

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/pagerduty

## Related pages

- [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents.
- [Datadog for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/datadog): Bring Datadog monitors, logs, traces and incidents into your agent. Turn an alert into a timeline and a likely cause.
- [App integrations for Claude Code, Codex, and Cursor](https://corespeed.io/integrations): Connect Gmail, Slack, Notion, GitHub, and more to Claude Code, Codex, Cursor, and other MCP clients. Manage private and shared connections.
- [Neon for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/neon): Let your agent read your Neon Postgres: projects, branches, schemas, and slow queries. Hold any SQL that could change data for a person.
- [Sentry for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/sentry): Bring Sentry issues, events and stack traces into your agent. Find the error that matters and the likely cause.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- PagerDuty: MCP server: https://support.pagerduty.com/main/docs/pagerduty-mcp-server
- PagerDuty: API access keys: https://support.pagerduty.com/main/docs/api-access-keys

Reviewed 2026-11-14.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)
