List available extension schemas representing integration vendors that can be attached to PagerDuty services.
Apache 2.0
440,475 tools. Updated 2026-08-10 23:37
"PagerDuty" matching MCP tools:
- Retrieve full details for a specific PagerDuty incident, including description, timeline, and alerts.Apache 2.0
- Retrieve PagerDuty teams by search query or get details for a specific team ID.MIT
- Resolve a PagerDuty incident by providing its ID to stop escalations and mark it as resolved.MIT
- Retrieve PagerDuty services using filters like team, user context, or search query. Get details for a specific service ID.MIT
- Acknowledge a PagerDuty incident to signal that someone is actively working on it. Requires incident ID.MIT
Matching MCP Servers
pagerduty-mcpofficial
AlicenseBqualityCmaintenanceEnables management of PagerDuty incidents, services, schedules, and more directly from MCP-enabled clients, with embedded interactive UIs for incident command center, on-call management, and other features.6374Apache 2.0- Alicense-qualityCmaintenanceEnables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.MIT
- Fetch PagerDuty schedules by name or ID, with options to limit results and specify time ranges for schedule details.MIT
- Retrieve PagerDuty incidents using filters (service, team, status, urgency, time range) or get details for a specific incident.MIT
- List all services in a PagerDuty account with optional name filtering to find specific services.AGPL 3.0
- Retrieve current on-call assignments from PagerDuty, with optional filtering by schedule or user ID.AGPL 3.0
- Retrieve detailed information for a single PagerDuty incident by providing its incident ID and API key.AGPL 3.0
- Acknowledge a PagerDuty incident using its ID to reduce alert noise and confirm response.AGPL 3.0
- Resolve a PagerDuty incident by providing its ID and API key, enabling automated incident management workflows.AGPL 3.0
- List PagerDuty incidents filtered by status, service, or date range, with pagination support.AGPL 3.0
- List curated multi-server bundles for common workflows like PR review or incident triage. Returns ready-to-run activate commands or matches against installed servers to identify missing namespaces.Cryptographic Autonomy 1.0 (Combined Work Exception)
- Retrieve teams with optional filtering by scope, name, or result count.Apache 2.0
- Get a schedule by ID – works for both layer-based and shift-based schedules, automatically resolving the type.Apache 2.0
- Retrieve details of a specific alert from a PagerDuty incident by providing the incident and alert IDs. If the alert ID is unknown, first use list_alerts_from_incident.Apache 2.0
- Retrieve full-period aggregated incident metrics from PagerDuty Analytics, including unique percentile distributions (P50, P75, P90, P95) for acknowledgment and resolution times. Filter by time range, teams, services, and urgency.Apache 2.0
- Retrieve all PagerDuty schedules from both v2 layer-based and v3 shift-based systems in one call, with source-specific status marks for completeness.Apache 2.0