From pagerduty
Guides PagerDuty service management: catalog, status (active/warning/critical), integrations, dependencies, alert grouping, maintenance windows, and API for listing services.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pagerduty:servicesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Services in PagerDuty represent the applications, components, or infrastructure that your team is responsible for. Each service has an escalation policy, integrations (event sources), and configuration for how incidents are created and grouped. Services are the primary organizational unit for routing alerts to the right responders.
Services in PagerDuty represent the applications, components, or infrastructure that your team is responsible for. Each service has an escalation policy, integrations (event sources), and configuration for how incidents are created and grouped. Services are the primary organizational unit for routing alerts to the right responders.
| Status | Description |
|---|---|
active | Service is live and will create incidents from alerts |
warning | Service has acknowledged but unresolved incidents |
critical | Service has triggered (unacknowledged) incidents |
maintenance | Service is in a maintenance window; alerts are suppressed |
disabled | Service is disabled; no incidents will be created |
Integrations are the event sources that feed into a service. Each integration has a unique integration_key used to route events:
Services can be configured to automatically group related alerts into a single incident:
| Mode | Description |
|---|---|
intelligent | PagerDuty ML groups related alerts automatically |
time | Alerts within a time window are grouped together |
content_based | Alerts with matching fields are grouped |
Service dependencies map upstream and downstream relationships between services. This helps identify blast radius during incidents and understand service topology.
pagerduty_list_services
Parameters:
query -- Search by service nameteam_ids[] -- Filter by teaminclude[] -- Include related resources (escalation_policies, teams, integrations)sort_by -- Sort field (name)limit / offset -- PaginationExample response:
{
"services": [
{
"id": "PSVC123",
"name": "Payment API",
"status": "active",
"description": "Payment processing service",
"escalation_policy": {
"id": "PPOLICY1",
"summary": "Engineering On-Call"
},
"alert_creation": "create_alerts_and_incidents",
"alert_grouping_parameters": {
"type": "intelligent"
},
"teams": [
{
"id": "PTEAM01",
"summary": "Platform Team"
}
]
}
],
"limit": 25,
"offset": 0,
"total": 1,
"more": false
}
pagerduty_get_service
Parameters:
id -- Service IDinclude[] -- Include integrations, escalation_policies, teamspagerduty_create_service
Parameters:
name -- Service name (required)description -- Service descriptionescalation_policy -- Escalation policy reference (required)alert_creation -- create_alerts_and_incidents or create_incidentsalert_grouping_parameters -- Alert grouping configurationpagerduty_update_service
Parameters:
id -- Service IDname -- Updated namedescription -- Updated descriptionstatus -- active or disabledalert_grouping_parameters -- Updated grouping configpagerduty_list_service_dependencies
Parameters:
id -- Service IDReturns upstream (depends on) and downstream (depended on by) service relationships.
pagerduty_list_maintenance_windows
Parameters:
service_ids[] -- Filter by servicefilter -- ongoing, future, past, or allquery -- Search by descriptionpagerduty_create_maintenance_window
Parameters:
start_time -- Start time (ISO 8601)end_time -- End time (ISO 8601)description -- Description of the maintenanceservices -- List of service referencesExample request body:
{
"maintenance_window": {
"type": "maintenance_window",
"start_time": "2026-03-28T02:00:00Z",
"end_time": "2026-03-28T06:00:00Z",
"description": "Database upgrade - v12 to v15",
"services": [
{
"id": "PSVC123",
"type": "service_reference"
}
]
}
}
pagerduty_list_services to get all servicesstatus field for each service (critical, warning, active)critical or warning status, list their incidentspagerduty_create_servicepagerduty_create_maintenance_windowpagerduty_list_service_dependencies for the serviceCause: Invalid service ID Solution: List services to find the correct ID
Cause: Service has unresolved incidents Solution: Resolve all incidents before disabling or deleting
Cause: A service with the same name already exists Solution: Use a unique name or update the existing service
include[]=integrations to verify monitoring sources are connectednpx claudepluginhub wyre-technology/msp-claude-plugins --plugin pagerdutyManages Rootly service catalog: lists services by team/tier/env, views details/dependencies/ownership/health, creates/updates services, links to incidents/alerts.
Automates PagerDuty incident management, services, schedules, escalation policies, and on-call rotations via Rube MCP (Composio) toolkit.
Automates PagerDuty tasks via Composio's Rube MCP: manage incidents, services, schedules, escalation policies, and on-call rotations. Use for incident workflows and ops.