PagerDuty

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

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://mcp.pagerduty.com/
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.

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 .

Required non-secret settings

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

Provider setup steps

  1. Create a PagerDuty User API token for an account with Advanced Permissions.
  2. Keep the token in protected client configuration and send it only in the documented Authorization header.
  3. 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 this server to your client

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'

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.

  • Using live-validated endpoint: https://mcp.pagerduty.com/mcp
  • 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.
  • 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.
  • 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>.

Claude Code MCP documentation

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

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.

  • Using live-validated endpoint: https://mcp.pagerduty.com/mcp
  • 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.
  • 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.
  • 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>.

Codex MCP documentation

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

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.

  • Using live-validated endpoint: https://mcp.pagerduty.com/mcp
  • 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.
  • 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.
  • 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>.

Cursor MCP documentation

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
    }
  ]
}

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.

  • Using live-validated endpoint: https://mcp.pagerduty.com/mcp
  • 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.
  • 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.
  • 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>.

VS Code MCP documentation

Latest validation evidence

Validation status
Online when last tested
Validation checked at
Aug 24, 2026 at 2:00 AM
Validation detail
Authorization could not be started: protected-resource issuer https://mcp.pagerduty.com/ mismatches AS issuer https://app.pagerduty.com/global/oauth/anonymous; no registration endpoint; API-token alternative is available