Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider’s consent screen.
  • Scopes: incidents.read, incidents.write, services.read, oncalls.read, users.read.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

​
Setup

  1. Get a PagerDuty account: Sign up at https://www.pagerduty.com - a free trial or developer account is sufficient for testing.
  2. Register an app: In PagerDuty go to Integrations > App Registration (https://app.pagerduty.com/developer/applications), create an app, and add Scoped OAuth functionality. Select the scopes incidents.read, incidents.write, services.read, oncalls.read, and users.read.
  3. Configure the redirect URI: Set the redirect URI to your app’s /api/auth/pagerduty/callback URL, then copy the Client ID and Client Secret into your .env as PAGERDUTY_CLIENT_ID and PAGERDUTY_CLIENT_SECRET.
  4. Verify access: Complete the OAuth flow, then run List Services and List Incidents.

​
Provider notes

  • OAuth endpoints live on identity.pagerduty.com; the REST API lives on api.pagerduty.com
  • Creating or updating incidents requires a From header containing the email of a valid PagerDuty user - the tools expose it as a required parameter
  • Scoped OAuth tokens expire and are renewed with the refresh token
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as pagerduty__list_incidents with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.