Connectors · Service desk & support
PagerDuty MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to PagerDuty and the rest of your systems. It gives your agent 451 PagerDuty actions (221 reads, 157 writes and 73 that wait for a confirmation) and holds the PagerDuty credential itself, so the agent never does. It paces PagerDuty's limits and records every call.
100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcpdo { action: "pagerduty.users.list", intent: "check which PagerDuty account is connected"}# List users. · read · 1 upstream call- 451actionsin one signed file
- 221readlook, never change
- 157writecreate and update
- 73wait for a yesdestructive, confirmed first
Set up
Connect PagerDuty in three steps.
- 01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp - 02
Connect PagerDuty.
Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
api_keyPagerDuty REST API key (Authorizationfrom_emailEmail of a PagerDuty user on this account (sent as the From header, which PagerDuty requires on incident writes)
account { op: "connections.requirements", service: "pagerduty" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "pagerduty.users.list" }# list users. · read · 1 upstream callcheck { action: "pagerduty.users.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
PagerDuty at a glance
- Sign-in
- Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
- You provide
api_keyfrom_email- Limits we pace to
- 900 calls a minute, per connection
- API covered
- PagerDuty API 2
api.pagerduty.com - Built from
- PagerDuty's documentation, read 15 September 2026OpenAPI spec (GitHub)
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 218 of 221 reads, for up to an hour; a write clears what it affects
- Ready-made plans
- 10 in the store
- Shared entities
- 6, so ask can line PagerDuty up with your other systems
- Data
- Processed and stored in Sydney, Australia. No US region yet
Capabilities
What an AI agent can do in PagerDuty.
451 actions in 7 areas. Every one carries its effect, so a key can allow the reads and hold the rest.
- 221readlook, never change
- 157writecreate and update
- 73destructivewait for a confirmation
Configuration
19084 read · 73 write · 33 destructive
Get Paused Incident Reporting on Alerts. · List Event Orchestrations. · List Rulesets. · Create an Orchestration.
Incidents
6830 read · 29 write · 9 destructive
List alerts for an incident. · List incidents. · List notes for an incident. · List Incident Workflows.
Services
6530 read · 24 write · 11 destructive
List services. · Create an extension. · List extensions. · List Business Services.
Directory
6330 read · 20 write · 13 destructive
List users. · List teams. · Create a user. · Create a team.
Status
3121 read · 6 write · 4 destructive
List Status Dashboards. · Get a single Status Dashboard by `id`. · Get a single Status Dashboard by `url_slug`. · List Status Pages.
Oncall
1810 read · 5 write · 3 destructive
List users on call. · List audit records for an escalation policy. · List audit records for a schedule. · Create an escalation policy.
Analytics
1616 read · 0 write · 0 destructive
Get raw data - single incident. · Get raw data - multiple incidents. · Get raw incidents for a single responder_id. · Get raw user analytics data.
PagerDuty's own MCP server
PagerDuty's MCP server, or actionlake?
PagerDuty hosts a remote MCP server with OAuth; its earlier local server is archived.
Use PagerDuty's server when one person wants to work in PagerDuty from their own AI client. Use actionlake when you also want PagerDuty behind the same endpoint as your other systems: a key per agent with allowed actions and a spending cap, a named person's approval before destructive actions, a sealed record of every call, and one ask across PagerDuty and another system.
Source: PagerDuty's documentation, checked 22 October 2026.
Top actions
The PagerDuty API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 233 of PagerDuty's 239 action names are shared with at least one other connector, so an agent learns them once.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
pagerduty.users.listList users. | List users. | read | identity.user.list474 connectors |
pagerduty.teams.listList teams. | List teams. | read | identity.group.list262 connectors |
pagerduty.incidents_alerts.listList alerts for an incident. | List alerts for an incident. | read | monitoring.alert.list51 connectors |
pagerduty.incidents.listList incidents. | List incidents. | read | monitoring.incident.list19 connectors |
pagerduty.services.listList services. | List services. | read | monitoring.service.list12 connectors |
pagerduty.users.createCreate a user. | Create a user. | write | identity.user.create262 connectors |
pagerduty.teams.createCreate a team. | Create a team. | write | identity.group.create205 connectors |
pagerduty.incidents_notes.listList notes for an incident. | List notes for an incident. | read | monitoring.incident_note.list11 connectors |
pagerduty.paused_incident_reports_alerts.listGet Paused Incident Reporting on Alerts. | Get Paused Incident Reporting on Alerts. | read | monitoring.alert.list51 connectors |
pagerduty.rulesets.listList Rulesets. | List Rulesets. | read | automation.workflow.list51 connectors |
pagerduty.users.deleteDelete a user. | Delete a user. | destructive | identity.user.delete253 connectors |
pagerduty.extensions.createCreate an extension. | Create an extension. | write | automation.webhook.create209 connectors |
Try it
Prompts to paste into Claude.
Each one names the PagerDuty actions it will call, so you know what it reads and what it changes before you send it.
- Readread
Which PagerDuty incidents are open, and how long has each been open?
calls
pagerduty.incidents.list - Planwrite
Stand up a new service with an escalation policy in PagerDuty.
calls
pagerduty.escalation_policies.createpagerduty.services.createpagerduty.tags.createpagerduty.change_tags.createpagerduty.services_custom_fields_values.replace+1 more - Planread
Audit extensions and webhook subscriptions in PagerDuty.
calls
pagerduty.extensions.listpagerduty.webhook_subscriptions.listpagerduty.webhook_subscriptions_oauth_clients.listpagerduty.workflows_integrations.listpagerduty.workflows_integrations_connections.list - Writewrite
Create a user in PagerDuty. Show me exactly what you will send before you save it.
calls
pagerduty.users.create
The plan store
Ready-made plans for PagerDuty.
10 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design.
Pull the weekly reliability metrics
Use it when Someone needs the weekly or monthly reliability numbers for services, teams and escalation policies in one pull.
Audit extensions and webhook subscriptions
Use it when An admin wants an inventory of every outbound integration, webhook and extension configured on the account.
Triage open incidents and note the alert load
Use it when An on-call engineer wants every open incident annotated with its current alert load before a handover.
Snooze noisy incidents after approval
Use it when A flood of low-urgency pages needs silencing for a while and a human must sign off before anything goes quiet.
A person decides
Snooze number of incidents low-urgency incidents for duration seconds.
Open a maintenance window for a deploy
Use it when A planned deploy or migration needs alerting suppressed on a service for a fixed window.
A person decides
Open a maintenance window on name, suppressing its alerts for the requested period.
Run a remediation automation against an incident
Use it when A known remediation script should be run against an open incident and the result recorded on the incident.
A person decides
Run automation action action id against incident incident id on service service id.
Cover an on-call gap with an override
Use it when Someone is unavailable for a shift and a named replacement must be put on call for that window.
A person decides
Add an on-call override on name between since and until (number of overrides overrides already exist).
Stand up a new service with an escalation policy
Use it when A new component or microservice needs a PagerDuty service, an escalation policy and inventory tags created together.
Post a customer update to the status page
Use it when Customers need a fresh update posted on an existing status page incident during an outage.
A person decides
Publish this customer-facing update on status page post post id.
Remove a leaver from a team and its notifications
Use it when Someone has left the team or the company and must stop receiving that team's pages.
A person decides
Remove name from team team id and unsubscribe them from its notifications.
account { op: "plans.install", slug: "pagerduty-weekly-reliability-report" }
# then ask for it by name; a schedule can run it on a timetableGovernance for PagerDuty
Destructive actions wait for a yes.
73 PagerDuty actions are destructive. The first 10:
- Delete a user.
pagerduty.users.delete - Delete a team.
pagerduty.teams.delete - Delete a Ruleset.
pagerduty.rulesets.delete - Delete an Incident Workflow.
pagerduty.incident_workflows.delete - Delete an Orchestration.
pagerduty.event_orchestrations.delete - Delete an extension.
pagerduty.extensions.delete - Delete a webhook subscription.
pagerduty.webhook_subscriptions.delete - Delete a service.
pagerduty.services.delete - Delete a Business Service.
pagerduty.business_services.delete - Delete an Alert Grouping Setting.
pagerduty.alert_grouping_settings.delete
A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.
Delete a user.?
intent: the user asked me to delete a user.
account { op: "keys.create", name: "pagerduty-agent", allowed_actions: ["pagerduty.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "pagerduty.users.delete", approver: "[email protected]" }, { match: "pagerduty.teams.delete", approver: "[email protected]" }, { match: "pagerduty.rulesets.delete", approver: "[email protected]" } ]}Cost
What PagerDuty costs on actionlake.
Every PagerDuty action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call PagerDuty refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
- 1upstream call per actionall 451 PagerDuty actions
- 451actions pageeach page of a long list is one call
- 218reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every PagerDuty action.
451 actions by area: the id your agent calls, what it does, and its effect.
Configuration190
pagerduty.event_orchestrations.createCreate an Orchestration.writepagerduty.event_orchestrations.listList Event Orchestrations.readpagerduty.paused_incident_reports_alerts.listGet Paused Incident Reporting on Alerts.readpagerduty.rulesets.listList Rulesets.readpagerduty.automation_actions_actions.createCreate an Automation Action.writepagerduty.automation_actions_actions.deleteDelete an Automation Action.destructive- and 184 more in this area
Incidents68
pagerduty.incident_workflows.listList Incident Workflows.readpagerduty.incidents.listList incidents.readpagerduty.incidents_alerts.listList alerts for an incident.readpagerduty.incidents_notes.listList notes for an incident.readpagerduty.alert_grouping_settings.createCreate an Alert Grouping Setting.writepagerduty.alert_grouping_settings.deleteDelete an Alert Grouping Setting.destructive- and 62 more in this area
Services65
pagerduty.business_services.listList Business Services.readpagerduty.extensions.createCreate an extension.writepagerduty.extensions.listList extensions.readpagerduty.services.listList services.readpagerduty.addons.createInstall an Add-on.writepagerduty.addons.deleteDelete an Add-on.destructive- and 59 more in this area
Directory63
pagerduty.teams.createCreate a team.writepagerduty.teams.listList teams.readpagerduty.users.createCreate a user.writepagerduty.users.listList users.readpagerduty.abilities.getTest an ability.readpagerduty.abilities.listList abilities.read- and 57 more in this area
Status31
pagerduty.status_dashboards.getGet a single Status Dashboard by `id`.readpagerduty.status_dashboards.listList Status Dashboards.readpagerduty.status_dashboards_url_slugs.getGet a single Status Dashboard by `url_slug`.readpagerduty.status_pages.listList Status Pages.readpagerduty.status_dashboards_service_impacts.listGet impacted Business Services for a Status Dashboard by `id`.readpagerduty.status_dashboards_url_slugs_service_impacts.listGet impacted Business Services for a Status Dashboard by `url_slug`.read- and 25 more in this area
Oncall18
pagerduty.escalation_policies.createCreate an escalation policy.writepagerduty.escalation_policies_audit_records.listList audit records for an escalation policy.readpagerduty.schedules_audit_records.listList audit records for a schedule.readpagerduty.schedules_users.listList users on call.readpagerduty.escalation_policies.deleteDelete an escalation policy.destructivepagerduty.escalation_policies.getGet an escalation policy.read- and 12 more in this area
Analytics16
pagerduty.analytics_raw_incidents.getGet raw data - single incident.readpagerduty.analytics_raw_incidents.queryGet raw data - multiple incidents.readpagerduty.analytics_raw_responders_incidents.queryGet raw incidents for a single responder_id.readpagerduty.analytics_raw_users.queryGet raw user analytics data.readpagerduty.analytics_metrics_incidents_all.queryGet aggregated incident data.readpagerduty.analytics_metrics_incidents_escalation_policies.queryGet aggregated escalation policy data.read- and 10 more in this area
This index shows a sample of each area. All 451 actions, with their inputs and prices, are in the catalogue, which a free sandbox key can search.
Questions
The PagerDuty MCP server, answered.
Is there a PagerDuty MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 451 PagerDuty actions across configuration, incidents, services and directory, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by PagerDuty.
Does PagerDuty have its own MCP server?
PagerDuty hosts a remote MCP server with OAuth; its earlier local server is archived. (PagerDuty's documentation, checked 22 October 2026.) Use PagerDuty's server when one person wants to work in PagerDuty from their own AI client. Use actionlake when you also want PagerDuty behind the same endpoint as your other systems: a key per agent with allowed actions and a spending cap, a named person's approval before destructive actions, a sealed record of every call, and one ask across PagerDuty and another system.
What do I need to connect PagerDuty?
PagerDuty REST API key (Authorization and Email of a PagerDuty user on this account (sent as the From header, which PagerDuty requires on incident writes). The free call account { op: "connections.requirements", service: "pagerduty" } lists exactly what to paste.
Can an AI agent delete or change things in PagerDuty?
Only if its key allows it, and only with an explicit confirmation. 73 PagerDuty actions are destructive, including delete a user., delete a team. and delete a Ruleset.. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.
Will an AI agent use up my PagerDuty API limit?
actionlake paces every call to the limits in the PagerDuty service file: 900 calls a minute per connection. Repeated reads are answered from cache (218 PagerDuty actions can be), which never reaches PagerDuty.
What does a PagerDuty action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (451 PagerDuty actions page). Cache hits, searches, dry runs and calls PagerDuty refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
Which PagerDuty API does it cover?
The PagerDuty API 2 at api.pagerduty.com. It is built from PagerDuty's documentation as read on 15 September 2026. 451 actions in 7 areas, each one in the signed service file (version 1.0.0).
Does actionlake keep my PagerDuty data, and where?
actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your PagerDuty credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.
Which AI clients can use it?
Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.
Give your agent PagerDuty today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.
