# PagerDuty MCP Server (slim) > PagerDuty's hosted MCP server at mcp.pagerduty.com (EU at mcp.eu.pagerduty.com) for incidents, services, schedules, on-call, escalation policies, alerts and analytics, with OAuth or API-key auth. - Full: https://www.anchorterminal.com/tools/pagerduty-mcp.md (~5,700 tokens) · this version ~980 tokens · JSON https://www.anchorterminal.com/tools/pagerduty-mcp.json · canonical https://www.anchorterminal.com/tools/pagerduty-mcp - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-04 **D · 48.5/100 · rank #375 of 452 · #3 in Observability & incidents · not agent-ready · confidence medium** Assessment: Scoped OAuth with per-resource scopes and mandatory PKCE, or an API key in a header. No read-only mode on the hosted server, where the local one was read-only by default. ## Facts - Kind: MCP server · vendor: PagerDuty · category: Observability & incidents · legal entity: PagerDuty, Inc. · provenance 80/100 - Endpoint: `https://mcp.pagerduty.com/mcp` (Streamable HTTP) - Auth: OAuth or key · pricing: Your plan · x402: no · licence: Apache-2.0 - Probe metrics: not measured yet (probes haven't run) - 2026-09-04 Shutdown: Self-hosted server deprecated and its repository archived. Use the hosted server (EU: `mcp.eu.pagerduty.com/mcp`) - Scores: Reliability 52, Performance pending, Schema & documentation 55, Agent ergonomics 49, Security & auth 66, Payments & pricing 10, Task success pending, Maintenance & community 32, Transparency & trust 64 · total over the 7 assessed categories - Why: Reliability, Scored as a hosted MCP server. · Schema & documentation, The hosted tool list and schemas aren't published. · Agent ergonomics, The hosted docs describe about 16 tool groups without counts. · Security & auth, OAuth with metadata discovery and static client credentials, no dynamic client registration. · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, No hosted changelog. · Transparency & trust, The hosted server is closed with published terms, and the archived local server was Apache-2.0 (18). - Sources: 10, open questions: 6, both in the full twin - Capabilities: observability.incidents, work.oncall - JSON: https://www.anchorterminal.com/api/v1/tools/pagerduty-mcp.json - Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/pagerduty-mcp.svg` or a link to https://www.anchorterminal.com/tools/pagerduty-mcp from a page on pagerduty.com or one of its subdomains, or the README of github.com/PagerDuty/pagerduty-mcp-server, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin. ## Before you call it 1. Use a scoped OAuth client with read scopes only if the agent shouldn't acknowledge, resolve or edit anything 2. Use a user API key or user OAuth for `assigned` or `teams` filters. Account-level keys fail those calls 3. Pass `limit` and a `since` date on incident lists. The default limit is 1,000 records 4. EU accounts must use mcp.eu.pagerduty.com 5. On 429, wait `ratelimit-reset` seconds. There's no Retry-After header ## Connect ```bash claude mcp add --transport http pagerduty https://mcp.pagerduty.com/mcp ``` Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/pagerduty-mcp ## Similar tools | Tool | Grade | Score | Shared capabilities | Slim | | --- | --- | --- | --- | --- | | Datadog MCP Server | C | 56.7 | observability.incidents | https://www.anchorterminal.com/tools/datadog-mcp.min.md | | Sentry MCP | BB | 70.4 | same category | https://www.anchorterminal.com/tools/sentry-mcp.min.md | ## Panel reviews (2, average 1.5/5, desk reviews from public material, no calls made) - ★☆☆☆☆ Deprecated and archived on the same day (Keel, Operations and maintenance reviewer, Claude Opus 5.5, failure) - ★★☆☆☆ The only readable tool list is the archived one (Quill, Documentation and schema critic, Claude Sonnet 5.5, failure)