Retrieve PagerDuty escalation policies by query, user, team, or policy ID to find the right escalation rules for incident response.
MIT
190,696 tools. Last updated 2026-06-10 23:13
"PagerDuty" matching MCP tools:
- Retrieve PagerDuty teams filtered by name or ID. Get details for a specific team or list teams matching a query.MIT
- Add a note to a PagerDuty incident to document context, investigation progress, or resolution details.MIT
- Resolve a PagerDuty incident by providing its ID to stop escalations and mark it as resolved.MIT
- Retrieve PagerDuty services by filters such as team ID, search query, or limit, or get details for a specific service ID.MIT
- Acknowledge an incident to signal that it is being actively worked on and update its status in PagerDuty.MIT
Matching MCP Servers
- AlicenseAqualityCmaintenanceA server that exposes PagerDuty API functionality to LLMs with structured inputs and outputs, enabling management of incidents, services, teams, and users.Last updated127MIT
- AlicenseAqualityCmaintenanceA community-maintained MCP server for interacting with PagerDuty accounts, enabling management of incidents, services, schedules, and event orchestrations through MCP-enabled clients.Last updated201Apache 2.0
- Retrieve PagerDuty schedules by filtering on name or specific ID, with options to include time-range details and select response fields.MIT
- List all PagerDuty services to monitor incidents and manage configurations. Filter by name to find specific services.MIT
- Acknowledge a PagerDuty incident using its unique ID to confirm that a responder is handling it.MIT
- Retrieve details for a specific PagerDuty incident by providing its unique incident ID.MIT
- Resolve a PagerDuty incident by providing the incident ID and API key.MIT
- Create a PagerDuty incident on a specified service to trigger alerts and notify your team.MIT
- List PagerDuty incidents filtered by status, service, or date range to manage and respond to alerts.MIT
- Bind external systems (ticketing, alerts, Slack, monitors) to FleetQ so events become signals that trigger rules and agents. Query and extend the knowledge graph for agent reasoning.AGPL 3.0
- Retrieve the current user's PagerDuty profile data, including name, role, teams, and summary.Apache 2.0
- Retrieve on-call entries for schedules, policies, or time ranges. Returns current on-calls or those within a specified range.MIT
- Get details for a specific service by providing its service ID to view configuration and status.Apache 2.0
- Retrieve details of a specific PagerDuty schedule using its unique ID.Apache 2.0
- Retrieve details of a specific PagerDuty team by providing its ID or name.Apache 2.0
- Constructs a user context dictionary containing user, team, service, and escalation policy IDs to filter PagerDuty resources like incidents, services, and teams.MIT