MCP Gateway · Claude
Connect PagerDuty to Claude
Incident managers, support leads and executives need to know what happened, who is covering, and what customers were told. Claude can answer from PagerDuty without anyone learning its screens. Each person connects once through the organization's custom connector and only reaches the PagerDuty tools their role allows.
- Category
- Infrastructure
- Tools
- 64
- Authentication
- API key
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run PagerDuty MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every PagerDuty call inspected and logged.
Set up
Add PagerDuty to Claude in 4 steps
- 01
Add PagerDuty from the catalog
An admin finds PagerDuty in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
PagerDuty authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use PagerDuty
Give teams the
mcp:connectscope on the PagerDuty server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds PagerDuty to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use PagerDuty from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, PagerDuty's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with PagerDuty
Summarize an incident for leadership
Ask Claude for a plain-language summary of last night's incident. It reads the incident and its notes and writes a few paragraphs on impact, cause and follow-up.
Check holiday on-call coverage
Before a holiday weekend, Claude reads the schedule and the people on it, so you can confirm someone is covering every shift.
See what customers were told
Claude finds the status page post for an incident and lists its updates in order, so account teams can repeat the same message to customers.
list_status_pagesget_status_page_postlist_status_page_post_updates
Tools
64 tools
Each PagerDuty tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
list_alert_grouping_settings
List all alert grouping settings with optional filtering.
get_alert_grouping_setting
Get details for a specific alert grouping setting.
list_alerts_from_incident
List alerts for a specific incident.
get_alert_from_incident
Get a specific alert from an incident.
list_change_events
List all change events with optional filtering.
get_change_event
Get details about a specific change event.
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every PagerDuty call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the PagerDuty tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to PagerDuty can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can managers read PagerDuty in Claude without changing anything?
Do PagerDuty conversations in Claude count toward budgets?
How do Claude users get PagerDuty?
Are PagerDuty calls from Claude logged?
Connect more