Connect PagerDuty to Claude Code

Let Claude triage, acknowledge, and resolve incidents in PagerDuty. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect PagerDuty to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect PagerDuty, you add a PagerDuty MCP server: a small hosted service that exposes PagerDuty's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own PagerDuty account. No API keys pasted into config files.

claude mcp add --transport http pagerduty https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in PagerDuty once connected?

Full read-write PagerDuty access lets Claude triage a noisy alert, acknowledge and reassign an incident, post a status note your responders see, escalate to the next on-call, and adjust a schedule override once you approve. The incident handling that used to mean tab-switching happens where the incident already lives.

Acknowledge an incident and reassign it to the right on-call responder
Resolve an incident once mitigation is confirmed
Add a status note or timeline entry visible to responders
Trigger an escalation to the next level when an incident stalls
Create a schedule override to cover a gap in on-call coverage
Snooze a low-priority incident for a set window

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same PagerDuty access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the PagerDuty API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when PagerDuty changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build PagerDuty connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same PagerDuty connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own PagerDuty account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on PagerDuty's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to PagerDuty?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the PagerDuty account it signs in with. Revoking access is one click in PagerDuty.

More on the PagerDuty connector

PagerDuty connector for claude.ai GitHub + Claude Code GitLab + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us