Provisioning pathDeveloper Tools

Connect PagerDuty to Claude, ChatGPT, and any MCP client

PagerDuty, wired to your AI assistant through a hosted MCP connector: verdict first, tools second, guardrails throughout.

Every system here gets an honest, affirmative path: verified and instant, buildable and provisioned, human-assisted, or a done-for-you conversation. Zero dead ends.

Connect PagerDuty PagerDuty API docs

OAuth 2.0 sign-inTeam mode availableOpenAPI spec on file

Buildability verdict

Where PagerDuty stands today

Buildable. We will provision it.Provisioning path

266 tools from PagerDuty's API, a core surface built from the vendor's own spec. PagerDuty is spec-backed: the pipeline reads the published OpenAPI description, shapes it into tools, and validates everything before deploy. Same-day turnaround is typical.

From our index notes on PagerDuty: REST API v2; incidents, services, escalation policies, and on-call schedules are the core objects.

Issues, pull requests, and build status: engineering questions answered without leaving the conversation.

Also searched as pager duty. The vendor's developer documentation lives at developer.pagerduty.com. A machine-readable OpenAPI description is on file.

Proposed tools

What a PagerDuty connector would expose

The proposal you review during intake, separated into Read and Write. Nothing writes without asking you first.

Built from OpenAPI spec

Generated from the published machine-readable spec, then run through validation gates before going live. The list shown here is a representative preview; the real spec build produces the full tool list.

Readon by default

search_issues
Find issues by title, label, or assignee
get_issue
Fetch one issue with its comments
list_pull_requests
List open pull requests by repo or author
get_build_status
Read the latest build or deploy status

Writeon, asks first

create_issueconfirm
Open a new issue
fields: title, body, labels, assignee
update_issue_stateconfirm
Close, reopen, or relabel an issue
fields: state, labels
add_issue_commentconfirm
Comment on an issue or pull request
fields: body
delete_branchdestructivedry-run
Delete a branch
fields: branch

Every write asks first: it pauses on a preview of the exact change and runs only when you approve it, before anything reaches PagerDuty. Turn off anything you never want your AI to touch.

How it works

From "PagerDuty" to a working connector URL

Designed for operators, not developers. You never read API docs, manage tokens, or touch a line of code.

01
Name it
A 30-second eligibility check confirms your AI client accepts a custom connector URL, then you pick the software. This page pre-fills that step.
02
Describe what you need
Plain language, not configuration. What should the assistant be able to look up, and what should it be able to change?
03
Review your Connector Blueprint
The exact Read and Write tool list, before you pay anything. Every write ships on in confirm mode and asks before it runs, every tool is individually toggled, and anything destructive carries a distinct warning.
04
Deploy and paste the URL
You get a hosted connector URL plus paste-in instructions matched to your AI client, and a live test panel that confirms the connection.

Identity and team

PagerDuty supports Team mode

PagerDuty supports per-user credentials, so each team member connects as themselves: upstream audit trails stay truthful, each member's reach is capped by their own PagerDuty permissions, and per-member URLs are individually revocable.

Team mode available

OAuth 2.0 sign-in

You sign in to PagerDuty and approve access. The connector requests the scopes its tool surface needs at connect time; every write still asks first, you can turn tools off at any time, and no password is ever shared.

The safety story

Write access to PagerDuty your IT team will approve

Every write asks first: it pauses on a preview of the exact change and runs only when you approve it. Nothing reaches the upstream system unapproved.

Confirm mode

Enabled writes run through Multi Round-Trip Requests: the tool pauses, shows a human-readable preview of the exact change, and only proceeds with approval. Nothing reaches PagerDuty on the model's intent alone.

Guardrails

Any tool can be turned off. Field-level constraints restrict what can be touched, per-tool rate limits are enforced at the gateway edge, and destructive operations ship in dry-run, demonstrating what they would do until you graduate them.

Activity log

Every tool call is logged: who, what, when, result. Write actions and confirmations are highlighted, redaction controls decide how much argument data is stored, and the log is append-only, with updates and deletes refused by the database.

FAQ

Connecting PagerDuty: the specifics

Can my AI assistant write to PagerDuty?

Yes, with guardrails. Write tools work out of the box in confirm mode: every write asks first, pausing on a preview of the exact change before anything reaches PagerDuty. Destructive operations ship in dry-run and never execute until you graduate them, and you can turn off any tool you never want touched.

Is it safe to connect PagerDuty to an AI assistant?

Safety is the architecture, not a setting. Every write asks first: it pauses on a human confirmation with the exact change previewed before it reaches PagerDuty. Destructive operations demonstrate in dry-run and never execute until you graduate them, any tool can be turned off, and every call lands in an activity log with redaction controls.

If my team uses a PagerDuty connector, whose name is on the actions?

The right one. In Team mode each member connects with their own PagerDuty identity, so upstream audit trails show the real person, and each member's effective access is the intersection of the connector's guardrails and their own PagerDuty permissions. Per-member URLs are individually revocable.

Which AI clients work with a PagerDuty connector?

Any client that accepts a remote MCP connector URL: Claude (Free, Pro, Max, Team, and Enterprise), ChatGPT on paid plans with developer mode enabled, Cursor, and other MCP-compatible clients. Team and Enterprise workspaces may need an admin to allow custom connectors first.

How long until a PagerDuty connector is live?

Typically the same day. PagerDuty publishes a machine-readable spec, so the pipeline generates the mapping, validates it, and deploys without waiting on a human.

Anything specific to the PagerDuty API worth knowing?

Yes. From our index notes on PagerDuty: REST API v2; incidents, services, escalation policies, and on-call schedules are the core objects.

Related connectors