Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From pagerduty
Creates a PagerDuty incident on a specified service using title and service name. Resolves service ID, confirms on-call responder, and displays incident number, ID, title, urgency, and assigned responder.
npx claudepluginhub wyre-technology/msp-claude-plugins --plugin pagerdutyHow this command is triggered — by the user, by Claude, or both
Slash command
/pagerduty:create-incidentThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Create PagerDuty Incident Create a new incident on a specified service. The incident will be routed through the service's escalation policy, notifying the on-call responder according to urgency-based notification rules. ## Prerequisites - PagerDuty MCP server connected with valid API token - MCP tools `list_services`, `create_incident`, and `list_oncalls` available ## Steps 1. **Resolve the service** Call `list_services` with `query` set to the provided `service_name`. If multiple services match, present them and ask the user to clarify. Extract the service ID. 2. **Confirm the ...
/create-incidentCreate a new Rootly incident with title, optional severity (default high), affected services, and summary. Looks up IDs via API, posts incident, and displays details with URL.
/incidentOrchestrates incident response for specified <incident> using SRE best practices, supporting optional [phase] like triage or postmortem.
/incident-responseStart incident response with severity classification, role assignment, and action plan.
/incident-triageTriages current Better Stack incidents: fetches active ones, categorizes by status, highlights unacknowledged grouped by monitor, and suggests next steps.
/incident-responseInvokes incident response playbook for managing security or operational incidents. Uses shortcut 'sir' for quick access.
/create-ticketCreates a new service ticket in SuperOps.ai for a client by name/ID and subject, with optional description, priority, requester, and tech-group. Validates inputs, checks duplicates, and returns ticket number, ID, and URL.
Share bugs, ideas, or general feedback.
Create a new incident on a specified service. The incident will be routed through the service's escalation policy, notifying the on-call responder according to urgency-based notification rules.
list_services, create_incident, and list_oncalls availableResolve the service
Call list_services with query set to the provided service_name. If multiple services match, present them and ask the user to clarify. Extract the service ID.
Confirm the on-call responder
Call list_oncalls filtered by the service's escalation policy to show who will be notified. Present the on-call chain so the user can confirm before creating.
Create the incident
Call create_incident with:
type: incidenttitle: the provided titleservice: { "id": "<service_id>", "type": "service_reference" }urgency: the provided urgency (default: high)body: { "type": "incident_body", "details": "<details>" } if details are providedConfirm creation
Display the created incident number, ID, title, service, urgency, and assigned responder.
Provide next steps
Suggest monitoring the incident with /incident-triage and checking the on-call responder's acknowledgement status.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| title | string | Yes | Short summary of the incident | |
| service_name | string | Yes | Name of the service to create the incident on | |
| urgency | string | No | high | Urgency level (high, low) |
| details | string | No | Detailed description of the incident |
/create-incident --title "Payment processing failures" --service_name "Payment API"
/create-incident --title "Elevated latency on search" --service_name "Search Service" --urgency low --details "P99 latency increased from 200ms to 800ms starting at 14:00 UTC. No errors, just slowness."
list_services to find available servicesPAGERDUTY_API_TOKEN is set correctly/incident-triage - Triage open incidents including the newly created one/escalate-incident - Escalate the incident if the responder doesn't acknowledge/oncall-schedule - Check who will be notified/service-health - Check service health before creating