PagerDuty MCP Server – Incidents and On-Call
PagerDuty's official MCP server gives AI assistants structured access to incident-response and on-call operations. Use it to retrieve incident context, inspect services and schedules, manage approved response workflows, and support operational triage from an MCP-compatible client.
Overview
PagerDuty's official MCP server connects compatible AI assistants to a
PagerDuty account. It provides structured tools for operational data and
actions, allowing an agent to work with current incidents, services, schedules,
escalation policies, workflows, status pages, and event-orchestration context
instead of relying only on manually pasted information.
What the MCP server enables
PagerDuty documents tools across multiple operational domains. Depending on
authentication type, account permissions, enabled capabilities, and whether
write tools are allowed, an AI agent can:
- Retrieve and inspect incidents, alerts, notes, responders, and related context.
- Review services, teams, schedules, escalation policies, and on-call coverage.
- Access incident insights such as related, past, or outlier incidents.
- Inspect service and global event orchestrations.
- Work with status pages and publish approved status updates.
- List and start incident workflows.
- Create, update, or delete selected schedules and escalation policies.
- Filter the available tool set for focused workflows.
When to use it
Use PagerDuty MCP when an agent needs live operational context or must perform
an approved incident-response action. Typical workflows include summarizing an
active incident, checking who is on call, reviewing escalation paths, finding
similar past incidents, inspecting service configuration, starting an incident
workflow, preparing a status-page update, or coordinating response activity
from an AI assistant.
Connection and authentication
PagerDuty hosts a remote Streamable HTTP endpoint at
https://mcp.pagerduty.com/mcp. EU-region accounts use
https://mcp.eu.pagerduty.com/mcp. The hosted service supports OAuth and API
token authentication, but does not currently support Dynamic Client
Registration. API-token connections use the Authorization header with the
format Token token=<api-key>.
PagerDuty also publishes the local pagerduty-mcp package for stdio use through
uvx. The local server reads a user API token from
PAGERDUTY_USER_API_KEY. EU accounts can set PAGERDUTY_API_HOST to
https://api.eu.pagerduty.com.
Key considerations
The local server is read-only by default; write tools must be enabled
explicitly. Use a dedicated user API token with minimum permissions and require
human confirmation before incident changes, schedule edits, escalation-policy
changes, workflow starts, or status-page updates. Some hosted-server filters
require user-level authentication rather than account-level credentials.
PagerDuty rate limits and account permissions still apply. Limit exposed tools
where possible and connect only trusted MCP clients.
Supported Transports
streamable_http
URL: https://mcp.pagerduty.com/mcp
stdio
Command: uvx
Args:
pagerduty-mcp
Frequently Asked Questions
- When should an AI agent use the PagerDuty MCP server?
- Use it when a workflow needs current incident-response or on-call context, such as reviewing active incidents, checking schedules, inspecting services, finding related incidents, starting workflows, or preparing approved status updates.
- What does the PagerDuty MCP server add to an AI agent's capabilities?
- It gives the agent structured access to live PagerDuty operational data and supported actions, allowing it to investigate and coordinate current response workflows instead of relying only on static model knowledge or manually pasted incident information.
- What can an AI agent access or manage through PagerDuty MCP?
- Depending on permissions and enabled tools, the agent can work with incidents, alerts, services, teams, schedules, escalation policies, event orchestrations, incident workflows, status pages, on-call data, and selected incident insights and write operations.
- How is authentication configured for the PagerDuty MCP server?
- The hosted server supports OAuth or a PagerDuty API token in the Authorization header using the Token token= format. The local stdio server reads a user API token from PAGERDUTY_USER_API_KEY. Store credentials in a protected environment or secret manager and grant minimum permissions.
- Which transport should be used for the PagerDuty MCP server?
- Use Streamable HTTP for PagerDuty's managed hosted service, with the region-specific endpoint for US or EU accounts. Use stdio with uvx when a local process is preferred, when local tool filtering is needed, or when the client cannot connect directly to a remote MCP endpoint.