MCP Gateway · Claude Cowork
Connect PagerDuty to Claude Cowork
Reliability work outside an incident takes time: quarterly incident reviews, on-call rotas for new teams, overrides for holidays. Cowork can work through those tasks in PagerDuty from start to finish. The PagerDuty server reaches Cowork through the synced plugin marketplace, and Speakeasy's agent hooks allow or deny each prompt before a step runs.
- Category
- Infrastructure
- Tools
- 64
- Authentication
- API key
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the PagerDuty server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use PagerDuty from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with PagerDuty
Prepare a quarterly incident review
Cowork lists the quarter's incidents, reads each one and its log entries, and builds a review document grouped by service with timelines and recurring causes.
Set up on-call for a new team
When a new team takes on production services, Cowork creates the team in PagerDuty, adds its members, and builds an on-call schedule that rotates through them.
Plan holiday cover with overrides
Give Cowork the list of who is away. It finds the affected schedules and creates an override for each shift that needs a different person.
Tools
64 tools
Each PagerDuty tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
How are Cowork sessions that use PagerDuty attributed?
How do PagerDuty plugin changes reach Cowork?
How do Claude Cowork users get PagerDuty?
Are PagerDuty calls from Claude Cowork logged?
Connect more