Get started

PagerDuty for AI agents

PagerDuty collects operational signals, alerts the right on-call responder, and coordinates incident response across engineering teams. Ops and SRE teams use it to reduce time to resolution. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect PagerDutySee the 368 actions ↓
DevOps and monitoringOAuth 2.0MCP + RESTpagerduty.com
AUDIT LOG · PAGERDUTYPOLICY: acme-support
09:41:07 · claude · u_8f2read
pagerduty.list_licenses
List licenses✓ allowed · 212ms
09:41:08 · claude · u_8f2read
pagerduty.get_a_trigger
Get incident workflow trigger✓ allowed · 164ms
09:41:09 · claude · u_8f2write
pagerduty.create_a_ruleset
Create a ruleset✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
pagerduty.delete_tag_by_id
Delete tag by id✕ blocked · policy: deny
EVERY PAGERDUTY CALL, ON THE RECORD
01 · USE CASES

What agents do in PagerDuty.

01

Create an incident record

Open a new incident with a title and urgency so the right on-call team is paged.

02

Check escalation policy metrics

Pull aggregated incident metrics for an escalation policy read-only to spot repeat pages.

03

Create a maintenance window with approval

Schedule a maintenance window only after a change owner confirms the timing.

02 · ACTIONS

368 PagerDuty actions, graded by risk.

Every PagerDuty action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

187

Look things up. Allowed by default.

  • pagerduty.get_a_trigger
    Get incident workflow trigger
  • pagerduty.get_schedules
    Get schedules
  • pagerduty.get_scim_user
    Get SCIM user
  • pagerduty.list_licenses
    List licenses
  • pagerduty.list_templates
    List templates
  • pagerduty.get_addons_list
    Get addons list
  • pagerduty.get_log_entries
    Get log entries
  • pagerduty.list_scim_users
    List SCIM users
  • pagerduty.get_audit_records
    Get audit records
  • pagerduty.list_scim_schemas
    List SCIM schemas
  • pagerduty.get_response_plays
    Get response plays
  • pagerduty.get_template_by_id
    Get template by id
  • pagerduty.list_incident_types
    List incident types
  • pagerduty.get_an_incident_type
    Get an incident type
  • pagerduty.get_scim_schema_by_id
    Get SCIM schema by ID
  • pagerduty.get_incident_workflows
    Get incident workflows
+ 171 MORE

write

126

Create and change things. Allow, or ask the user first.

  • pagerduty.create_a_ruleset
    Create a ruleset
  • pagerduty.create_a_trigger
    Create incident workflow trigger
  • pagerduty.send_mcp_request
    Send MCP request
  • pagerduty.update_a_trigger
    Update incident workflow trigger
  • pagerduty.update_team_by_id
    Update team by id
  • pagerduty.create_new_service
    Create new service
  • pagerduty.create_user_object
    Create user object
  • pagerduty.post_change_events
    Send change event to PagerDuty
  • pagerduty.post_team_to_runner
    Post team to runner
  • pagerduty.update_add_on_by_id
    Update add on by id
  • pagerduty.update_ruleset_by_id
    Update ruleset by id
  • pagerduty.update_service_by_id
    Update service by id
  • pagerduty.post_incident_metrics
    Post incident metrics
  • pagerduty.update_incident_by_id
    Update incident by id
  • pagerduty.update_schedule_by_id
    Update schedule by id
  • pagerduty.update_standard_by_id
    Update standard by id
+ 110 MORE

destructive

55

Delete, cancel or archive. Ask first, or deny outright.

  • pagerduty.delete_tag_by_id
    Delete tag by id
  • pagerduty.delete_team_by_id
    Delete team by id
  • pagerduty.delete_user_by_id
    Delete user by id
  • pagerduty.delete_addon_by_id
    Delete addon by id
  • pagerduty.delete_event_by_id
    Delete event by id
  • pagerduty.delete_field_option
    Delete field option
  • pagerduty.delete_response_play
    Delete response play
  • pagerduty.delete_ruleset_by_id
    Delete ruleset by id
  • pagerduty.delete_service_by_id
    Delete service by id
  • pagerduty.delete_schedule_by_id
    Delete schedule by id
  • pagerduty.delete_template_by_id
    Delete template by id
  • pagerduty.delete_extension_by_id
    Delete extension by id
  • pagerduty.delete_post_update_by_id
    Delete post update by id
  • pagerduty.delete_service_rule_by_id
    Delete service rule by id
  • pagerduty.delete_user_session_by_id
    Delete all user sessions
  • pagerduty.delete_user_contact_method
    Delete user contact method
+ 39 MORE
03 · HOW IT WORKS

PagerDuty in three steps.

  1. 01Your users connect PagerDutyThey sign in to PagerDuty on Arc0 Connect, under your brand, and approve the access you ask for.
  2. 02You set the rulesReads run, writes like “create a ruleset” can wait for the user, and “delete tag by id” can be denied outright.
  3. 03Any agent can actYour agent calls PagerDuty through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('pagerduty', {
  read: 'allow',
  write: 'ask',        // create_a_ruleset
  destructive: 'deny',  // delete_tag_by_id
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How PagerDuty connects.

Users sign in to PagerDuty on Arc0 Connect and approve the scopes you request. Build with Arc0’s PagerDuty OAuth app, or bring your own so the PagerDuty consent screen names you. Tokens refresh automatically, and you can export them whenever you want.

The same PagerDuty connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key · OAuth 2.0
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use PagerDuty from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More devops and monitoring apps.

ServiceNow171 actionsNew Relic159 actionsGrafana Cloud118 actionsBetter Stack117 actionsDatadog65 actionsMezmo36 actionsStatuscake30 actionsInstatus15 actions
ALL DEVOPS AND MONITORING APPS →
07 · FAQ

PagerDuty and Arc0, answered.

Q01

Can I use PagerDuty with Claude, ChatGPT or Cursor?

Yes. Connect PagerDuty to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the PagerDuty actions you allow.

Q02

How do users connect PagerDuty?

Users sign in to PagerDuty on Arc0 Connect and approve the scopes you request. Build with Arc0’s PagerDuty OAuth app, or bring your own so the PagerDuty consent screen names you. Tokens refresh automatically, and you can export them whenever you want.

Q03

Which PagerDuty actions can my agent take?

368 in total: 187 read, 126 write and 55 destructive, such as “create a ruleset”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in PagerDuty?

Yes. Actions like “delete tag by id” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call PagerDuty too?

Yes. The same PagerDuty connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug PagerDuty into your agent.

Your users connect PagerDuty once, under your brand. Your agent gets 368 actions behind your policies, with every call on the record.

Connect PagerDutyBrowse all apps →

Free to build · MCP + REST · Audit log on every plan