PagerDuty MCP server

Endpoint: https://mcp.pagerduty.com/mcp · Authentication: Sign in with OAuth

PagerDuty's hosted MCP server provides incident, service, schedule, escalation, and on-call operations.

Test it live Run the release-readiness report

How do I authenticate?

Add the endpoint in your client, start Connect or Sign in, approve the requested scopes, and return to the client. OAuth discovery finds the authorization server; client registration requirements vary by provider. Follow the provider guidance and client setup below.

Authentication and connection guide

Connection specification

Remote endpoint: https://mcp.pagerduty.com/mcp
Browser access: Not yet measured
Declared MCP transport: Streamable HTTP
Live-validated MCP transport: Not yet verified — Latest validation did not verify a transport
Declared authentication: OAuth 2.1
Detected authentication: OAuth 2.1 detected or retained from publisher evidence
Alternative authentication: API token
Alternative endpoint: https://mcp.eu.pagerduty.com/mcp — Use for PagerDuty EU service-region accounts (OAuth 2.1)
Protocol lifecycle: Not yet negotiated
Required header: Authorization — Optional PagerDuty API token syntax: Token token=<PAGERDUTY_API_TOKEN>
Authorization server: https://app.pagerduty.com/global/oauth/anonymous
Category: Observability

Product documentation · Official listing documentation

Provider guidance

Authorization could not be started in the 2026-08-24 audit: protected-resource metadata names https://mcp.pagerduty.com/, while the retrieved authorization-server document declares https://app.pagerduty.com/global/oauth/anonymous and no Dynamic Client Registration endpoint. Strict issuer equality is preserved. Use the documented API-token option directly; EU accounts use the separate EU endpoint.

More Observability MCP servers · Browse all MCP servers · Test this endpoint in the MCP Playground

Authorization setup

Use an API token

For hosted mcptest, automatic OAuth client registration is unavailable. Use the publisher-documented API token route and keep the credential in protected client storage.

Publisher evidence reviewed 2026-08-24.

Required non-secret settings

Account permission: Advanced Permissions (required)
Credential type: PagerDuty User API token (required)

Provider setup steps

Create a PagerDuty User API token for an account with Advanced Permissions.
Keep the token in protected client configuration and send it only in the documented Authorization header.
Use the EU hosted endpoint when the PagerDuty account is in the EU service region.

Safe header template: Token token=<PAGERDUTY_API_TOKEN>. Replace only the named placeholder in protected client configuration.

Publisher documentation

Connect it

Live-validated endpoint: https://mcp.pagerduty.com/mcp · Streamable HTTP. Use an API token: For hosted mcptest, automatic OAuth client registration is unavailable. Use the publisher-documented API token route and keep the credential in protected client storage.

Agent prompt for Claude Code or Codex

Add the PagerDuty MCP server to my MCP client configuration and verify that it works.

What it is: PagerDuty's hosted MCP server provides incident, service, schedule, escalation, and on-call operations.
Server URL: https://mcp.pagerduty.com/mcp
Transport: Streamable HTTP (remote MCP server, no local install).
Authentication: OAuth 2.1. Use an API token: For hosted mcptest, automatic OAuth client registration is unavailable. Use the publisher-documented API token route and keep the credential in protected client storage.
Tools: not yet observed by mcptest; tools/list will show them.
Reference: https://mcptest.io/servers/pagerduty/

Steps:
1. Work out which MCP client I use (Claude Code, Codex, Cursor, VS Code or another) and add the server under the name "pagerduty" in that client's MCP configuration, user scope unless I ask otherwise.
   Claude Code: claude mcp add --transport http --scope user --header 'Authorization: Token token='"${PAGERDUTY_API_TOKEN}" 'pagerduty' 'https://mcp.pagerduty.com/mcp'
   Other clients: use the setup for that client on the reference page.
2. Never write a credential value into a file that could be committed; reference an environment variable or the client's secret store, and ask me for any value you need.
3. Verify: connect to the server and call tools/list. Confirm the tools above are listed, and report any sign-in step I still have to complete.

Claude Code setup

Run in a terminal. This user-scoped entry is available across projects.

claude mcp add --transport http --scope user --header 'Authorization: Token token='"${PAGERDUTY_API_TOKEN}" 'pagerduty' 'https://mcp.pagerduty.com/mcp'

Store PAGERDUTY_API_TOKEN in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Token token=<PAGERDUTY_API_TOKEN>.

Codex CLI setup

Add to ~/.codex/config.toml, then securely set PAGERDUTY_API_TOKEN_HEADER to the complete Authorization header value, including the required syntax Token token=<credential>.

[mcp_servers.pagerduty]
url = "https://mcp.pagerduty.com/mcp"
env_http_headers = { "Authorization" = "PAGERDUTY_API_TOKEN_HEADER" }

Store PAGERDUTY_API_TOKEN_HEADER in your operating system keychain, secret manager, or protected environment; never commit the value. Set it to the complete Authorization header value, including the required syntax Token token=<credential>.

Cursor setup

Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.

{
  "mcpServers": {
    "pagerduty": {
      "url": "https://mcp.pagerduty.com/mcp",
      "headers": {
        "Authorization": "Token token=${env:PAGERDUTY_API_TOKEN}"
      }
    }
  }
}

Store PAGERDUTY_API_TOKEN in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Token token=<PAGERDUTY_API_TOKEN>.

VS Code setup

Add to .vscode/mcp.json, or run “MCP: Open User Configuration” for a private user-level entry.

{
  "servers": {
    "pagerduty": {
      "type": "http",
      "url": "https://mcp.pagerduty.com/mcp",
      "headers": {
        "Authorization": "Token token=${input:pagerduty_api_token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "pagerduty_api_token",
      "description": "PAGERDUTY_API_TOKEN for PagerDuty",
      "password": true
    }
  ]
}

VS Code requests PAGERDUTY_API_TOKEN as a masked input; use a secret manager and do not put a default value in mcp.json. The Authorization syntax remains Token token=<PAGERDUTY_API_TOKEN>.

Claude setup

Add the endpoint above in Claude:

Customize > Connectors > Add custom connector
Team/Enterprise: Organization settings > Connectors > Add > Custom > Web

Claude Desktop setup

Add the endpoint above in Claude Desktop:

Remote: Customize > Connectors (same as claude.ai)
Local: Settings > Developer > Edit Config, or Settings > Extensions for .mcpb files
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), local servers only

ChatGPT setup

Add the endpoint above in ChatGPT:

ChatGPT web: Plugins > Add custom MCP server, then configure authentication and accept the risk warning

Windsurf setup

Add the endpoint above in Windsurf:

~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows), serverUrl or url
Cascade panel > ... > MCPs > Open MCP config file

Gemini CLI setup

Add the endpoint above in Gemini CLI:

gemini mcp add --transport http <name> <url>
~/.gemini/settings.json (user) or .gemini/settings.json (project), mcpServers

MCP SDK setup

Add the endpoint above in MCP SDK:

Programmatic: new Client(...).connect(new StreamableHTTPClientTransport(url))

Notes for every client

Provider setup: Create a PagerDuty User API token for an account with Advanced Permissions.
Provider setup: Keep the token in protected client configuration and send it only in the documented Authorization header.
Provider setup: Use the EU hosted endpoint when the PagerDuty account is in the EU service region.
Publisher evidence (reviewed 2026-08-24): https://support.pagerduty.com/main/docs/pagerduty-mcp-server
Use the exact publisher-documented Authorization header syntax: Token token=<PAGERDUTY_API_TOKEN>.
Alternative endpoint: https://mcp.eu.pagerduty.com/mcp — Use for PagerDuty EU service-region accounts.
Provider guidance: Authorization could not be started in the 2026-08-24 audit: protected-resource metadata names https://mcp.pagerduty.com/, while the retrieved authorization-server document declares https://app.pagerduty.com/global/oauth/anonymous and no Dynamic Client Registration endpoint. Strict issuer equality is preserved. Use the documented API-token option directly; EU accounts use the separate EU endpoint.

Client compatibility

Client	Status	Why
Claude Code	Supported	Claude Code supports Streamable HTTP servers and API key headers.
Codex	Supported	Codex supports Streamable HTTP servers and API key headers.
Cursor	Supported	Cursor supports Streamable HTTP servers and API key headers.
VS Code	Supported	VS Code supports Streamable HTTP servers and API key headers.
Claude	Partial	Claude supports API key headers only in limited availability. static_headers: beta, for a limited set of organizations.
Claude Desktop	Partial	Claude Desktop supports API key headers only in limited availability. static_headers: beta, for a limited set of organizations.
ChatGPT	Not supported	ChatGPT does not support API key headers. ChatGPT cannot present custom API keys.
Windsurf	Supported	Windsurf supports Streamable HTTP servers and API key headers.
Gemini CLI	Supported	Gemini CLI supports Streamable HTTP servers and API key headers.
MCP SDK	Supported	MCP SDK supports Streamable HTTP servers and API key headers.

Computed from this server's validated transport, protocol and authentication against documented client support. Checks the catalog has not observed are not counted.

Similar servers

Sentry — Remote MCP server for searching, querying, and debugging Sentry issues and application errors. OAuth 2.1
Cloudflare Observability — Queries Workers logs and analytics to debug Cloudflare Workers applications. Requires Cloudflare OAuth. OAuth 2.1
Cloudflare Radar — Explores Cloudflare Radar internet insights such as global traffic trends. Requires Cloudflare OAuth. OAuth 2.1
Cloudflare GraphQL — Explores the Cloudflare GraphQL Analytics API schema and runs analytics queries against an account's zones and Workers. Requires Cloudflare OAuth. OAuth 2.1
Axiom — Queries Axiom event datasets with APL, explores datasets and metrics, and manages dashboards, monitors, and notifiers. Requires Axiom OAuth. OAuth 2.1
Globalping — Runs ping, traceroute, DNS, MTR, and HTTP measurements from Globalping's worldwide probe network. Uses OAuth or a Globalping API token. OAuth 2.1

Guides for this server

Watch this server for breaking changes

Share and embed

Maintain PagerDuty? Embed this badge in your README. It follows the latest catalog validation result and links to this server profile.

Markdown

[![Tested on mcptest.io](https://mcptest.io/badge/server/pagerduty.svg)](https://mcptest.io/servers/pagerduty/)

HTML

<a href="https://mcptest.io/servers/pagerduty/"><img src="https://mcptest.io/badge/server/pagerduty.svg" alt="Tested on mcptest.io"></a>

reStructuredText

.. image:: https://mcptest.io/badge/server/pagerduty.svg
   :alt: Tested on mcptest.io
   :target: https://mcptest.io/servers/pagerduty/

Latest validation evidence

Validation status: Online when last tested
Validation checked at: Oct 26, 2026 at 2:08 PM
Validation detail: Authentication challenge at https://mcp.pagerduty.com/mcp returned HTTP 401; endpoint was reachable but did not complete an MCP probe; authentication oauth

Tool inventory

Requires authorization; inventory not observed

The catalog validator lists tools only on servers that answer without credentials. PagerDuty asks for OAuth 2.1 sign-in first, so its tools, resources and prompts were not observed. Connect in the Playground with your own credentials to list them.