PagerDuty MCP

What it is

The PagerDuty MCP server is PagerDuty's own Model Context Protocol server for the PagerDuty platform. It lets AI assistants such as Cursor, VS Code and Claude Code read incident data, manage services and update on-call schedules in your PagerDuty account. PagerDuty hosts it at https://mcp.pagerduty.com/mcp, so there is nothing to install: PagerDuty describes it as hosted and maintained by PagerDuty, exposing tools through a remote HTTP endpoint, with no local Python or uvx needed. Accounts in the EU service region use https://mcp.eu.pagerduty.com/mcp.

PagerDuty used to publish a self-hosted server in the PagerDuty/pagerduty-mcp-server GitHub repository. That local server is now deprecated: PagerDuty's docs say the repository is archived and read-only, and its README says development has moved to the hosted server. If you find older guides that run uvx pagerduty-mcp, they describe the deprecated version.

Tools it exposes

The hosted server groups actions into browse and manage tools:

Requirements

• A PagerDuty account with Advanced Permissions. PagerDuty lists Advanced Permissions on PD Reliability Platform plans and on Professional, Business, Digital Operations (legacy) and Enterprise for Incident Management plans.
• A PagerDuty User API key, or an OAuth client for the hosted server.
• An MCP client that supports remote (HTTP-based) MCP servers.

Authentication

Both user-level and account-level credentials work, but some tools and filters need user-level auth, for example scoping list_incidents by teams or by assignee.

• API key: send the header Authorization: Token token=<your-api-key>.
• OAuth with static client credentials: your client discovers the OAuth metadata and you supply the client ID and secret. PagerDuty does not support Dynamic Client Registration, so you must create the OAuth client first.
• Bearer token: send Authorization: Bearer <token>, for example an App OAuth token from the client-credentials grant.

Setup by client

Cursor: add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "pagerduty": {
      "url": "https://mcp.pagerduty.com/mcp"
    }
  }
}

VS Code: add a pagerduty server of type http with the same URL to settings.json. With OAuth, VS Code prompts for the client credentials and shows the redirect URIs you need. With an API key, define a password promptString input and pass it in an Authorization: Token token=${input:pagerduty-api-key} header.

Claude Code with an API key:

PAGERDUTY_API_KEY=YOUR_API_KEY claude mcp add-json pagerduty '{"type":"http","url":"https://mcp.pagerduty.com/mcp","headers":{"Authorization":"Token token=${PAGERDUTY_API_KEY}"}}'

Claude Code with OAuth: use a static redirect port such as http://localhost:8080/callback on your OAuth client, then run claude mcp add-json with an oauth block holding your client ID and "callbackPort": 8080, passing the secret through MCP_CLIENT_SECRET and --client-secret. If Claude Code is your main client, compare it with the other best MCP servers for Claude Code.

Limits and safety

• Tool filtering is not available on the hosted server yet. PagerDuty suggests a Scoped OAuth client to limit which tools succeed.
• The server includes write tools such as manage_incidents, manage_teams (including delete) and manage_alert_grouping, so pick credentials with only the access the agent needs.
• Dynamic Client Registration is not supported, which means clients that rely on it cannot connect with OAuth until you register a client yourself.

Who it is for

On-call engineers, SREs and incident commanders who already run PagerDuty and want an agent to pull incident context, check who is on call, add notes or post status page updates from the editor or chat. It pairs well with the Datadog MCP server when your alerts start in Datadog.

Pricing

As of October 2026, PagerDuty's plan comparison lists MCP Integration as not included on the Free Incident Management plan and included on Professional and on the PD Reliability Platform plans (Starter, Essential, Plus and Ultimate). Professional is listed at $21 per user per month billed annually, or $25 billed monthly. PD Reliability Platform Starter is listed at a $2,800 platform fee per year and Essential at $12,000 per year.

Alternatives

• Datadog MCP server for logs, metrics, traces and incidents in Datadog.
• Splunk MCP for SPL search and alerts in Splunk.
• Grafana MCP server for Grafana dashboards, metrics and alerts.
• Sentry MCP server for application errors and traces.

What we could not verify

• The MCP Registry entry io.github.PagerDuty/pagerduty-mcp points to the deprecated local package (version 0.2.1 in the repository's server.json), not to the hosted endpoint.
• PagerDuty does not publish rate limits specific to the hosted MCP server on the pages we checked.

Sources

• PagerDuty MCP Server: https://docs.pagerduty.com/ai-automation/advance/pagerduty-mcp-server
• Advanced Permissions: https://docs.pagerduty.com/account-admin/advanced-permissions
• PagerDuty pricing: https://www.pagerduty.com/pricing/
• Deprecated self-hosted repository: https://github.com/PagerDuty/pagerduty-mcp-server