PagerDuty
The PagerDuty connector gives AI agents the ability to monitor incidents, check on-call schedules, acknowledge and resolve pages, and create new incidents — all via the PagerDuty REST API using OAuth 2.0. Your credentials are stored encrypted in MCPGate's vault and are never exposed to the AI client.
Incident creation pages your team
pagerduty_create_incident immediately triggers a page to the on-call engineer for the target service. Only enable this tool for agents that genuinely need to raise alerts. Use the respond preset to restrict the agent to acknowledgement and resolution actions only.Required scopes#
MCPGate requests the following OAuth scopes when you connect a PagerDuty account.
| Scope | Purpose |
|---|---|
| read | Read incidents, services, schedules, and on-call entries |
| write | Create, update, acknowledge, resolve, and snooze incidents |
Tool reference#
The PagerDuty connector exposes 10 tools: 5 read and 5 write.
| Tool | Category | Description |
|---|---|---|
| pagerduty_list_incidents | read | List PagerDuty incidents |
| pagerduty_get_incident | read | Get a specific PagerDuty incident by ID |
| pagerduty_list_services | read | List PagerDuty services |
| pagerduty_list_oncalls | read | List current on-call entries |
| pagerduty_list_schedules | read | List PagerDuty on-call schedules |
| pagerduty_create_incident | write | Create a new PagerDuty incident |
| pagerduty_update_incident | write | Update an existing PagerDuty incident |
| pagerduty_acknowledge_incident | write | Acknowledge a PagerDuty incident |
| pagerduty_resolve_incident | write | Resolve a PagerDuty incident |
| pagerduty_snooze_incident | write | Snooze a PagerDuty incident for a specified duration |
Common guardrail recipes#
Read-only access#
Enable only the five read tools. Deny all write tools. Useful for status dashboards and on-call lookup agents that need to surface incident context without taking any action.
Respond preset#
Enable read tools plus pagerduty_acknowledge_incident, pagerduty_resolve_incident, and pagerduty_snooze_incident. Deny pagerduty_create_incident and pagerduty_update_incident. This allows the AI to take immediate action on active pages without the ability to trigger new ones.
Restrict to specific services#
Apply the allow_values template to pagerduty_create_incident and target the service_id field. Provide a list of service IDs the agent is permitted to page. All other services will be denied.
Troubleshooting#
- Incident not found — PagerDuty incident IDs are alphanumeric strings (e.g.
P12345A). Ensure you are passing the correct ID — not the incident number shown in the UI, which is different. - Cannot acknowledge a resolved incident — Incidents in a terminal state (resolved) cannot be acknowledged or snoozed. Check the incident status with
pagerduty_get_incidentbefore taking action. - On-call list is empty —
pagerduty_list_oncallsreturns only current on-call entries. If the list is empty, verify that at least one escalation policy is active and has scheduled coverage at the current time.