PagerDuty

Overview

Connect PagerDuty so AI clients can browse services, see who is on-call, list open incidents, and inspect incident log entries and alerts via REST API v2.

This integration is read-first: list and get tools only. Acknowledge, resolve, and snooze actions are not included.

Prefer OAuth (Connect PagerDuty). A REST API key remains available as a fallback.

Prerequisites

• A PagerDuty account with access to the services you want to query
• Permission to authorize a PagerDuty OAuth app, or to create a REST API key
• A stackgate.ai account

Connect with OAuth

1. Sign in to stackgate.ai and open My Integrations → PagerDuty.
2. Choose Connect PagerDuty.
3. Sign in to PagerDuty and approve read access for services, schedules, on-calls, incidents, and log entries.
4. stackgate.ai stores the token encrypted and detects US vs EU residency from the token.
5. Optionally use Edit tool access to keep a subset of read tools.

Your PagerDuty OAuth app (Integrations → App Registration, Scoped OAuth) must allow the hub redirect URI and these read scopes: openid, users.read, services.read, schedules.read, oncalls.read, incidents.read, and log_entries.read.

See PagerDuty OAuth.

Connect with a REST API key

Use this when OAuth is not available for your account.

1. Sign in to PagerDuty for the account you want to connect.
2. Open Integrations → API Access Keys (or User Settings → API Access for a user token).
3. Create a REST API key. Copy it immediately.
4. Note your service region:
   • US accounts use https://api.pagerduty.com
   • EU data residency accounts use https://api.eu.pagerduty.com
5. In stackgate.ai, open My Integrations → PagerDuty.
6. Under Add with REST API key, paste the key, choose US or EU, and save. stackgate.ai verifies the key against /users/me and stores it encrypted.

See the PagerDuty REST API authentication docs.

Using with AI clients

• Dedicated endpoint: POST /mcp/pagerduty with a Sanctum bearer token
• Private gateway: one config for all integrations - use pagerduty__* namespaced tools

Example prompts:

• "Who is on-call for the payments service?"
• "List open PagerDuty incidents."
• "Show log entries for incident Q0U5BQO4V7E7X5."

Troubleshooting

• 422 integration not configured - complete OAuth or the API key form in My Integrations.
• 401 Unauthorized - reconnect OAuth, or regenerate the REST API key in PagerDuty and update My Integrations.
• 403 Forbidden - the connection cannot read services, schedules, or incidents. Re-authorize OAuth with the read scopes, or use an account-level API key.
• Wrong region - EU-residency accounts must use the EU API host. OAuth usually detects this; API keys need the EU option.
• 429 Too many requests - PagerDuty rate-limits REST calls. Retry after a short delay and use limit/offset instead of polling.
• Revoke access - disconnect the integration in My Integrations, then revoke the app or delete the key in PagerDuty.

Limitations

• Read-only MVP. Mutating incident actions are reserved for a later permission-gated release.
• Rate limits vary by plan. Prefer paginated list tools over tight loops.
• Incident payloads may include responder emails and phone numbers. Treat results as operational data.