PagerDuty MCP server
Drive incidents, schedules, and escalations on PagerDuty.
About
Connect Tracecat to PagerDuty to drive incidents, schedules, and escalation policies for SOC analysts and SRE on-call responders. You can acknowledge a noisy page and enrich the incident with SIEM and EDR context before a human even opens the app. From there, escalate to the right rotation, post status updates into the incident timeline, and log change events with full audit attribution under the connected user.
Setup
- 1
Create an API key
PagerDuty's MCP server authenticates with a PagerDuty User API Token. The token inherits the role and team permissions of the user that created it, so create it as a service user with least privilege when possible.
- 2
Select the
PagerDutytile in the Tracecat MCP catalogOpen the
MCP catalogin your workspace, select thePagerDutytile, and paste your API key. - 3
Enable
PagerDutyin your agentIn your
ai.agentaction orAgents→toolstab, selectPagerDutyfrom theMCP integrationsdropdown.
Tools
list_incidents | List incidents filtered by status, service, urgency, or assigned user. |
get_incident | Fetch a single incident with its alerts, log entries, and current responders. |
create_incident | Manually open an incident on a specific service with title, urgency, and details. |
acknowledge_incident | Acknowledge one or more incidents on behalf of the connected user. |
resolve_incident | Resolve one or more incidents and post a resolution note. |
list_schedules | List on-call schedules with rotations and current on-call users. |
get_schedule | Fetch a schedule with its layers, overrides, and upcoming shifts. |
list_escalation_policies | List escalation policies with their rules and target users or schedules. |
list_services | List services with integrations, escalation policies, and alert routing settings. |
create_change_event | Record a change event on a service to correlate with future alerts. |