--- title: "PagerDuty MCP server for AI agents - actionlake" description: "Give Claude 451 PagerDuty actions through one MCP server: configuration, incidents, services. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/pagerduty updated: 2026-10-10 --- 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. [Connect PagerDuty free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 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/mcp` the first call ``` do { action: "pagerduty.users.list", intent: "check which PagerDuty account is connected" } # List users. · read · 1 upstream call ``` - 451 actions in one signed file - 221 read look, never change - 157 write create and update - 73 wait for a yes destructive, confirmed first Set up ## Connect PagerDuty in three steps. 1. 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` 2. 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_key` PagerDuty REST API key (Authorization - `from_email` Email 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 ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "pagerduty.users.list" } # list users. · read · 1 upstream call check { 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_key` `from_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 2026[OpenAPI spec (GitHub)](https://raw.githubusercontent.com/PagerDuty/api-schema/main/reference/REST/openapiv3.json) **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. - **221** read look, never change - **157** write create and update - **73** destructive wait for a confirmation 1. ### Configuration 190 84 read · 73 write · 33 destructive Get Paused Incident Reporting on Alerts. · List Event Orchestrations. · List Rulesets. · Create an Orchestration. 2. ### Incidents 68 30 read · 29 write · 9 destructive List alerts for an incident. · List incidents. · List notes for an incident. · List Incident Workflows. 3. ### Services 65 30 read · 24 write · 11 destructive List services. · Create an extension. · List extensions. · List Business Services. 4. ### Directory 63 30 read · 20 write · 13 destructive List users. · List teams. · Create a user. · Create a team. 5. ### Status 31 21 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. 6. ### Oncall 18 10 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. 7. ### Analytics 16 16 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](https://github.com/PagerDuty/pagerduty-mcp-server), 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.list` List users. | List users. | read | `identity.user.list` 474 connectors | | `pagerduty.teams.list` List teams. | List teams. | read | `identity.group.list` 262 connectors | | `pagerduty.incidents_alerts.list` List alerts for an incident. | List alerts for an incident. | read | `monitoring.alert.list` 51 connectors | | `pagerduty.incidents.list` List incidents. | List incidents. | read | `monitoring.incident.list` 19 connectors | | `pagerduty.services.list` List services. | List services. | read | `monitoring.service.list` 12 connectors | | `pagerduty.users.create` Create a user. | Create a user. | write | `identity.user.create` 262 connectors | | `pagerduty.teams.create` Create a team. | Create a team. | write | `identity.group.create` 205 connectors | | `pagerduty.incidents_notes.list` List notes for an incident. | List notes for an incident. | read | `monitoring.incident_note.list` 11 connectors | | `pagerduty.paused_incident_reports_alerts.list` Get Paused Incident Reporting on Alerts. | Get Paused Incident Reporting on Alerts. | read | `monitoring.alert.list` 51 connectors | | `pagerduty.rulesets.list` List Rulesets. | List Rulesets. | read | `automation.workflow.list` 51 connectors | | `pagerduty.users.delete` Delete a user. | Delete a user. | destructive | `identity.user.delete` 253 connectors | | `pagerduty.extensions.create` Create an extension. | Create an extension. | write | `automation.webhook.create` 209 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. 1. Read read Which PagerDuty incidents are open, and how long has each been open? calls `pagerduty.incidents.list` 2. Plan write Stand up a new service with an escalation policy in PagerDuty. calls `pagerduty.escalation_policies.create` `pagerduty.services.create` `pagerduty.tags.create` `pagerduty.change_tags.create` `pagerduty.services_custom_fields_values.replace` +1 more 3. Plan read Audit extensions and webhook subscriptions in PagerDuty. calls `pagerduty.extensions.list` `pagerduty.webhook_subscriptions.list` `pagerduty.webhook_subscriptions_oauth_clients.list` `pagerduty.workflows_integrations.list` `pagerduty.workflows_integrations_connections.list` 4. Write write 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. 1. ### 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. **Effect** read **Steps** 4 **Needs** aggregate unit, filters and time zone **Install** `pagerduty-weekly-reliability-report` 2. ### Audit extensions and webhook subscriptions Use it when An admin wants an inventory of every outbound integration, webhook and extension configured on the account. **Effect** read **Steps** 5 **Install** `pagerduty-audit-stale-extensions` 3. ### 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. **Effect** write **Steps** 2 · loops **Needs** service ids and time zone **Install** `pagerduty-triage-open-incidents` 4. ### 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. **Effect** write **Steps** 3 · loops **Needs** duration and service ids **Install** `pagerduty-snooze-noisy-incidents` 5. ### 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. **Effect** write **Steps** 5 **Needs** maintenance window and service id **Install** `pagerduty-maintenance-window-open` 6. ### 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_. **Effect** write **Steps** 5 **Needs** action id, incident id, invocation and service id **Install** `pagerduty-run-automation-on-incident` 7. ### 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). **Effect** write **Steps** 5 **Needs** overrides, schedule id, since and until **Install** `pagerduty-schedule-override-cover` 8. ### 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. **Effect** write **Steps** 6 **Needs** custom fields, escalation policy, service and tag **Install** `pagerduty-new-service-onboarding` 9. ### 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_. **Effect** write **Steps** 6 **Needs** post id, post update and status page id **Install** `pagerduty-status-page-update` 10. ### 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. **Effect** destructive **Steps** 6 **Needs** subscribables, team id and user id **Install** `pagerduty-offboard-user-from-team` install a plan ``` account { op: "plans.install", slug: "pagerduty-weekly-reliability-report" } # then ask for it by name; a schedule can run it on a timetable ``` Governance 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. do pagerduty.users.delete confirm_policy: **human** Delete a user.? **intent:** the user asked me to delete a user. run suspended · waiting for a named person · key _pagerduty-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` 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: "lead@example.com" }, { match: "pagerduty.teams.delete", approver: "lead@example.com" }, { match: "pagerduty.rulesets.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to PagerDuty only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. 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. - 1 upstream call per action all 451 PagerDuty actions - 451 actions page each page of a long list is one call - 218 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every PagerDuty action. 451 actions by area: the id your agent calls, what it does, and its effect. **Configuration 190** - `pagerduty.event_orchestrations.create` Create an Orchestration. write - `pagerduty.event_orchestrations.list` List Event Orchestrations. read - `pagerduty.paused_incident_reports_alerts.list` Get Paused Incident Reporting on Alerts. read - `pagerduty.rulesets.list` List Rulesets. read - `pagerduty.automation_actions_actions.create` Create an Automation Action. write - `pagerduty.automation_actions_actions.delete` Delete an Automation Action. destructive - and 184 more in this area **Incidents 68** - `pagerduty.incident_workflows.list` List Incident Workflows. read - `pagerduty.incidents.list` List incidents. read - `pagerduty.incidents_alerts.list` List alerts for an incident. read - `pagerduty.incidents_notes.list` List notes for an incident. read - `pagerduty.alert_grouping_settings.create` Create an Alert Grouping Setting. write - `pagerduty.alert_grouping_settings.delete` Delete an Alert Grouping Setting. destructive - and 62 more in this area **Services 65** - `pagerduty.business_services.list` List Business Services. read - `pagerduty.extensions.create` Create an extension. write - `pagerduty.extensions.list` List extensions. read - `pagerduty.services.list` List services. read - `pagerduty.addons.create` Install an Add-on. write - `pagerduty.addons.delete` Delete an Add-on. destructive - and 59 more in this area **Directory 63** - `pagerduty.teams.create` Create a team. write - `pagerduty.teams.list` List teams. read - `pagerduty.users.create` Create a user. write - `pagerduty.users.list` List users. read - `pagerduty.abilities.get` Test an ability. read - `pagerduty.abilities.list` List abilities. read - and 57 more in this area **Status 31** - `pagerduty.status_dashboards.get` Get a single Status Dashboard by `id`. read - `pagerduty.status_dashboards.list` List Status Dashboards. read - `pagerduty.status_dashboards_url_slugs.get` Get a single Status Dashboard by `url_slug`. read - `pagerduty.status_pages.list` List Status Pages. read - `pagerduty.status_dashboards_service_impacts.list` Get impacted Business Services for a Status Dashboard by `id`. read - `pagerduty.status_dashboards_url_slugs_service_impacts.list` Get impacted Business Services for a Status Dashboard by `url_slug`. read - and 25 more in this area **Oncall 18** - `pagerduty.escalation_policies.create` Create an escalation policy. write - `pagerduty.escalation_policies_audit_records.list` List audit records for an escalation policy. read - `pagerduty.schedules_audit_records.list` List audit records for a schedule. read - `pagerduty.schedules_users.list` List users on call. read - `pagerduty.escalation_policies.delete` Delete an escalation policy. destructive - `pagerduty.escalation_policies.get` Get an escalation policy. read - and 12 more in this area **Analytics 16** - `pagerduty.analytics_raw_incidents.get` Get raw data - single incident. read - `pagerduty.analytics_raw_incidents.query` Get raw data - multiple incidents. read - `pagerduty.analytics_raw_responders_incidents.query` Get raw incidents for a single responder_id. read - `pagerduty.analytics_raw_users.query` Get raw user analytics data. read - `pagerduty.analytics_metrics_incidents_all.query` Get aggregated incident data. read - `pagerduty.analytics_metrics_incidents_escalation_policies.query` Get 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](https://actionlake.com/console/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. ## More connectors like PagerDuty Shares the most action names with - [Opsgenie 84](https://actionlake.com/connectors/opsgenie) - [FireHydrant 53](https://actionlake.com/connectors/firehydrant) - [ilert 50](https://actionlake.com/connectors/ilert) - [Squadcast 45](https://actionlake.com/connectors/squadcast) - [incident.io 37](https://actionlake.com/connectors/incident-io) - [Better Stack Uptime 35](https://actionlake.com/connectors/better-stack-uptime) Joins with, on shared entities - [Zabbix 4](https://actionlake.com/connectors/zabbix) - [Palo Alto Networks Cortex XDR 4](https://actionlake.com/connectors/palo-alto-networks-cortex-xdr) - [Commvault Cloud 3](https://actionlake.com/connectors/commvault-cloud) - [Dynatrace 3](https://actionlake.com/connectors/dynatrace) - [MongoDB Atlas 3](https://actionlake.com/connectors/mongodb-atlas) - [Mitti 3](https://actionlake.com/connectors/mitti) Browse - [All Service desk & support connectors](https://actionlake.com/connectors/category/service-desk-and-support) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by PagerDuty; the name is the vendor's own. Counts are from the PagerDuty service file, version 1.0.0. ## Give your agent PagerDuty today. [Connect PagerDuty free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/pagerduty More: https://actionlake.com/llms.txt