# PagerDuty — MCP Server

> Investigate incidents, check who is on call and read services and schedules from a conversation.

**Source:** https://mcpplaygroundonline.com/mcp-servers/pagerduty  
**Transport:** http  
**Requires auth:** Yes

---

## What it does

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 exposed

- 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

## Example queries you can run

- "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."

## Details

- **Recommended model:** anthropic/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.
- **Transport:** http
- **Authentication:** Required — A PagerDuty API key in the header Authorization: Token token=<key>, or OAuth. Dynamic client registration is not supported.
- **Hosted endpoint:** https://mcp.pagerduty.com/mcp
- **Official source:** [PagerDuty MCP Server integration guide](https://support.pagerduty.com/main/docs/pagerduty-mcp-server-integration-guide)

## Connecting to PagerDuty

### Connection 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>"
      }
    }
  }
}
```

## Frequently asked questions

### 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.

---

_Test this server across 40+ models on MCP Playground: https://mcpplaygroundonline.com/mcp-servers/pagerduty — free, no install._