Skip to main content
Connecting PagerDuty lets Claude read incidents and on-call schedules during incident work in any channel where the connector is on. Claude connects with its own credential, not a person’s. Pair this connector with the PagerDuty plugin from Anthropic’s plugin marketplace so Claude knows how to call the API. This connector calls PagerDuty’s HTTP API. It isn’t an MCP server or a member’s personal claude.ai connector.

​
Create the credential in PagerDuty

Generate a general-access read-only API key. A read-write key lets Claude acknowledge and resolve incidents. If you use one, turn the connector on only in a private incident channel. Creating a general-access key requires the PagerDuty Admin or Account Owner role; non-admins only see User Token keys, which also work but inherit that user’s permissions. PagerDuty’s own guide for creating the credential is at support.pagerduty.com.

​
Add the connector

Go to Organization settings > Claude Tag > Connectors, click Add, and select PagerDuty. Fill in these fields in the connect form. PagerDuty accounts on the EU service region use api.eu.pagerduty.com instead. If the connect form offers to include the PagerDuty plugin, leave that box selected; otherwise add the plugin on the Skills and plugins tab. The first credential you add for a service from the Connectors tab is on in every workspace and channel as soon as you save it. To give it narrower reach, see where a new connector applies before you save the connector. Click Connect to save the connector. The Agent Proxy injects the credential at the network boundary; the model and the sandbox are not given the key. See how Agent Proxy works.

​
Verify the connection

In a channel where the connector is on, in a new thread:
PagerDuty appears in the list once the connector is live. New threads pick up the connector on their own; in an existing thread, ask Claude to use the service by name.