PagerDuty for AI agents

On-call schedules, incident triage, and escalation policies. Add an API key once and every agent you run can use it.

  • Connects with an API key
  • Ready to connect
  • Any MCP client
  • No card required

The route from an agent to PagerDuty

Once PagerDuty is set up in your workspace, any agent you run can reach it: a Spinrun agent, or Claude, ChatGPT and Cursor through one MCP endpoint. Every call passes through the Spinrun gateway, which sorts it by risk and writes it to the activity log.

By default, every change an agent makes in a connected app waits for your approval, on every plan. Enhanced Control adds per-app read, write and destructive rules at the gateway on Free and Pro.

PagerDuty in the catalog

On-call schedules, incident triage, and escalation policies. · Developer Tools & DevOps

  1. An agent gets a jobFrom chat, a schedule, or your own AI client
  2. Spinrun checks the callSorted as a read, a write or a destructive call
  3. PagerDuty does the workThrough the connection you set up in your workspace
  4. Every call is loggedTool, outcome and duration, in one activity log

From Spinrun recipes

Jobs to hand an agent in PagerDuty

Each one is a real prompt from a Spinrun recipe or team page, ready to adapt to your own work.

  • “Open an #incidents thread first: I'm being paged about slow API responses. Then see what Datadog and the latest deploys say.”

    Latency page

  • “Open an #incidents thread for the alert PagerDuty just sent, and tell me whether traffic explains what Datadog is showing.”

    Alert triage

Three steps

From connection to first call

  1. Connect an app once

    Sign in from your workspace with OAuth or an API key. Spinrun keeps the credential in an encrypted vault, never in an agent's config.

  2. Decide what it may do

    By default, every change an agent makes in a connected app waits for your approval, on every plan. Enhanced Control adds per-app rules for reads, writes and destructive calls on Free and Pro.

  3. Let any agent use it

    Claude, ChatGPT, Cursor or a Spinrun agent reach the app through one MCP endpoint, and every call is written to the same activity log.

What it can do

Every PagerDuty action, sorted by risk

Spinrun sorts every PagerDuty action into one of three tiers. By default, agents ask before a write; on Free and Pro, the rules you set decide which tiers run.

  • Reads

    Read actions

    Fetch and search. Cannot change anything.

  • Writes

    Write actions

    Create and update. Changes data but does not remove it.

  • Destructive

    Destructive actions

    Delete, revoke, or overwrite. Hard or impossible to undo.

Paired in recipes

Apps agents use with PagerDuty

These appear next to PagerDuty in Spinrun's templates, recipes and team pages.

Same category

Other Developer Tools & DevOps apps

Other apps in this category that your agents can use.

See every app in this category

Questions about PagerDuty

You paste an PagerDuty API key once. Spinrun keeps it in an encrypted vault rather than in an agent's config, and you can revoke it in one click.

Put PagerDuty to work. Start free.

Connect PagerDuty, decide what it may do, and give an agent its first job.

Before anything loads

We would like to switch on analytics, so we can see which pages are worth keeping. Nothing has loaded yet and nothing will until you choose. The cookies that keep you signed in and remember your language are not part of this.

Read the Cookie Policy