🧪 Community ✓ Claude Code ✓ Claude Desktop Standalone • PagerDuty
PagerDuty
PagerDuty - incident management, on-call scheduling, alerting
Installation
Install this plugin individually:
/plugin marketplace add wyre-technology/msp-claude-plugins --plugin pagerduty Or install all MSP plugins at once:
/plugin marketplace add wyre-technology/msp-claude-plugins Features
- Alert Handling
- Analytics
- Incident Management
- On-Call Scheduling
- Services
Skills
This plugin provides 6 skills that teach Claude about PagerDuty:
| Skill | Description |
|---|---|
alerts | PagerDuty alerts: the alert-vs-incident model, alert statuses, grouping modes, event rules for routing and suppression, dedup_key deduplication, and the Events API v2 trigger/acknowledge/resolve payloads. |
analytics | PagerDuty Analytics: MTTA/MTTR/MTTE/MTTS definitions, incident and interruption counts, aggregation levels (account, service, team, escalation policy), time-range constraints, and benchmark tables for interpreting the numbers. |
incidents | PagerDuty incident lifecycle (triggered/acknowledged/resolved), urgency vs. priority, alerts-to-incident grouping, the 14 incident MCP tools, incident fields, notes, log entries, past-incident similarity search, merge and snooze semantics, and cross-vendor PSA ticket correlation for MSPs. |
oncall | PagerDuty on-call model: schedules with rotation layers, restrictions, the computed final schedule, and overrides; escalation policy tiers and timeouts; on-call entry fields; and the schedule, escalation policy, and team MCP tools. |
services | PagerDuty service catalog: service statuses, integrations and integration keys as event sources, alert grouping modes, upstream/downstream service dependencies, and maintenance windows. |
api-patterns | PagerDuty API and hosted MCP fundamentals: US/EU MCP endpoints, the `Token token=` auth header and token types, the complete 66-tool reference across 13 categories (incidents, on-call, schedules, escalation policies, services, event orchestrations, status pages, teams, users, and more), offset pagination, common filter parameters, rate limits, and error codes. |
Agents
This plugin provides 2 agents for autonomous task execution:
| Agent | Description |
|---|---|
incident-commander | Use this agent when an MSP engineer, SRE, or incident manager needs to command an active incident or review the state of open PagerDuty incidents. |
on-call-scheduler | Use this agent when an MSP operations lead, SRE manager, or engineering manager needs to review and manage PagerDuty on-call schedules — not incident response, but the health of the schedule system itself: coverage gaps, upcoming holidays without coverage, overloaded individuals, escalation policy misconfigurations, and rotation balance. |
Commands
Available slash commands:
| Command | Description |
|---|---|
/create-incident | Create a new PagerDuty incident on a service |
/escalate-incident | Escalate a PagerDuty incident to the next level in the escalation policy |
/incident-triage | Triage current open PagerDuty incidents by urgency and priority |
/oncall-schedule | Show who is currently on call across schedules and escalation policies |
/service-health | Check PagerDuty service health status and recent incident activity |
API Reference
| Base URL | |
| Authentication | |
| Rate Limit | |
| Documentation |
Example Usage
Create a new PagerDuty incident on a service
/create-incidentEscalate a PagerDuty incident to the next level in the escalation policy
/escalate-incidentTriage current open PagerDuty incidents by urgency and priority
/incident-triageShow who is currently on call across schedules and escalation policies
/oncall-scheduleCheck PagerDuty service health status and recent incident activity
/service-healthUsing Skills
/skill pagerduty:alerts
PagerDuty alerts: the alert-vs-incident model, alert statuses, grouping modes, event rules for routing and suppression, dedup_key deduplication, and the Events API v2 trigger/acknowledge/resolve payloads.