MCP ServerOfficialHTTP

PagerDuty MCP Server

PagerDuty hosts an MCP server for its incident platform. During an incident an agent can pull the timeline, see who is on call, find recent changes and read the service setup, without someone clicking through five screens.

Hosted URL

https://mcp.pagerduty.com/mcp

Suggested model

Claude Sonnet 4.5

Chat with 60+ AI models on the same workflow — switch to a different model mid-conversation and re-run the same prompt, or use Compare mode to put several side-by-side and balance quality vs. cost.

Auth

A PagerDuty API key in the header Authorization: Token token=<key>, or OAuth. Dynamic client registration is not supported.

What the PagerDuty MCP server does

How models use it and what it is built for.

The server covers PagerDuty’s core objects in sixteen tool groups, split into read and write operations: incidents, services, schedules, teams, escalation policies, event orchestrations, alert grouping, status pages, users, change events and activity logs. The read side is where most of the value is. “What changed before this incident started” joins change events to the incident timeline, and “who is on call for checkout right now” resolves a schedule through an escalation policy. The write side can manage incidents and services, so scope it deliberately. PagerDuty does not offer tool filtering on its hosted server; you restrict what an agent can do with a scoped OAuth client instead.

Tools the PagerDuty MCP server exposes

Typical tools an AI model can call. Exact names vary by version.

  • incidents — list, read and manage incidents and their timelines
  • services — read and manage services
  • schedules, teams and escalation policies — resolve who is on call
  • change events — recent deploys and changes linked to services
  • event orchestrations and alert grouping — read routing and grouping setup
  • status pages, users and activity logs

Connecting to PagerDuty

Taken from the official PagerDuty documentation — see PagerDuty MCP Server integration guide for the full reference.

Examples

US

https://mcp.pagerduty.com/mcp

EU

https://mcp.eu.pagerduty.com/mcp

For accounts in the EU service region.

Client configuration

API key

Note the Token token= scheme — PagerDuty’s, not a plain bearer token.

{
  "mcpServers": {
    "pagerduty": {
      "type": "http",
      "url": "https://mcp.pagerduty.com/mcp",
      "headers": {
        "Authorization": "Token token=<PAGERDUTY_API_KEY>"
      }
    }
  }
}

Example prompts to try

Copy any of these into MCP Agent Studio after connecting.

  • Who is on call for the checkout service right now, and who is next in the escalation policy?

  • Summarise incident #4821: timeline, responders and what changed in the hour before it fired.

  • Which services had the most high-urgency incidents this month?

  • List open incidents with no acknowledgement in the last 15 minutes.

Models on MCP Playground

This is not a single-model product: you get the same MCP connection with 60+ models (Claude, GPT, Gemini, DeepSeek, open-weight, and more), you can switch mid-conversation, and you can open Compare mode to run the same prompt against multiple models at once. The card above is a suggested starting point for this server — not the only choice.

Default pick for PagerDuty

Claude Sonnet 4.5

Incident summaries mean correlating timelines, changes and schedules across calls. Sonnet 4.5 is careful to separate what the data shows from what it suspects.

Check an AI agent can actually use the PagerDuty MCP server

Listing tools proves the server is reachable, not that a model can work with it. Evals go further: they read every tool on the server, write a test suite from its real schemas, and run it — code decides pass/fail on the responses (schema conformance, error codes, pagination, result caps) while a scoring model grades plain-English tasks driven through the tools.

Get a pass/fail report per tool with the evidence behind each verdict — and replay the same suite after every schema change. Destructive tools are excluded from the run.

Run evals

Try the PagerDuty MCP server in your browser

Open MCP Agent Studio with the connection pre-filled. Add your token, pick any of 60+ models, and start chatting — no install required.

Open Agent Studio

PagerDuty MCP server — FAQ

Common questions about connecting, scoping and using it safely.

How do I authenticate to the PagerDuty MCP server?

With a PagerDuty API key in the header Authorization: Token token=<key>, or with OAuth. PagerDuty does not support dynamic client registration, so clients that rely on it need static OAuth credentials.

Is there an EU endpoint?

Yes: https://mcp.eu.pagerduty.com/mcp, for accounts in the EU service region. The US endpoint is https://mcp.pagerduty.com/mcp.

Can I limit which tools an agent can use?

Not with tool filtering on the hosted server. Use a scoped OAuth client to limit what the credential can do — read-only is the sensible start.

Can I still run it locally?

PagerDuty has deprecated the self-hosted server and recommends the hosted one.

Why do some incident queries fail with an API key?

Some tools need user-level authentication, such as filtering incidents by team. An account-level key cannot answer those. Use OAuth as the user.

Other MCP servers

More on MCP Playground

PagerDuty MCP Server — AI Agent for Incidents and On-Call