PagerDuty Official Remote MCP Server

๐Ÿ›ก๏ธ Officialโœ“ VerifiedStreamable HTTPOAuth 2.1๐Ÿ›ก๏ธ A+~371 tok6 toolsยทOnline676msยท30d uptime: 100%ยทLast checked 2m ago

PagerDuty's hosted MCP (mcp.pagerduty.com/mcp) exposes incidents, services, on-call schedules and escalation policies to agents over OAuth 2.1.

https://mcp.pagerduty.com/mcp
Provider
PagerDuty โ†—
Categories
โ˜๏ธ Cloud, Infrastructure & DevOps
ไธญๆ–‡็ฎ€ไป‹

PagerDuty ๅฎ˜ๆ–น่ฟœ็จ‹ MCP ๆœๅŠกๅ™จใ€‚AI ไปฃ็†ๅฏ้€š่ฟ‡ OAuth ๅˆ—ๅ‡บๅ’Œๅˆ†่ฏŠไบ‹ไปถใ€ๆŸฅ็œ‹ๅ€ผ็ญ่กจ๏ผŒๅนถ็กฎ่ฎคๆˆ–่งฃๅ†ณไบ‹ไปถใ€‚

Maintainer of PagerDuty Incident? Claim or update this listing โ†’

Streamable HTTPhttps://mcp.pagerduty.com/mcp
Install in Cursor โ†’

Or add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "pagerduty": {
      "url": "https://mcp.pagerduty.com/mcp"
    }
  }
}

๐Ÿงฐ PagerDuty Incident MCP Tools & Schema (6)

ToolSafetyDescriptionParameters
list_incidents
~71 tok
๐ŸŸข ReadList incidents filtered by status and service.status: stringserviceId: string
get_incident
~57 tok
๐ŸŸข ReadGet incident details including alerts and log entries.incidentId*: string
acknowledge_incident
~51 tok
๐ŸŸ  WriteAcknowledge an incident.incidentId*: string
resolve_incident
~68 tok
๐ŸŸ  WriteResolve an incident with a note.incidentId*: stringresolution: string
list_services
~45 tok
๐ŸŸข ReadList PagerDuty services.query: string
get_oncall
~59 tok
๐ŸŸข ReadGet who is currently on call for a schedule or escalation policy.scheduleId*: string

๐Ÿ›ก๏ธ Security, Quality & Context Token Audit

๐Ÿ›ก๏ธ Grade A+Context tax: ~371 tokens injected into every system prompt by this serverโ€™s 6 tools

Every tool definition (name + description + input schema) is injected into your LLMโ€™s context on every request โ€” Estimate per-call LLM token cost โ†’

  • No prompt-injection or hidden-character anomalies detected in tool descriptions
  • Streamable HTTP primary endpoint (current 2025-03-26 transport)
  • OAuth 2.1 with PKCE S256 enforced
  • Official first-party endpoint operated by the vendor
  • Manually verified by RemoteMCP.net

๐Ÿ” OAuth 2.1 & Security

Auth type
OAuth 2.1
Dynamic Client Registration
โœ… Supported
PKCE S256
โœ… Supported
Scopes
readwrite
Protected resource metadata
https://mcp.pagerduty.com/.well-known/oauth-protected-resource (expected location)
๐Ÿ” Audit OAuth 2.1 Config โ†’

๐Ÿงฉ Recommended Agent Skills

๐Ÿ“– PagerDuty Incident MCP Endpoint Overview & Security Guide

PagerDuty Incident MCP โ€” Remote MCP Server

PagerDuty's remote MCP is the on-call endpoint โ€” agents can list open incidents, pull context on a triggered alert, check who's on call, and acknowledge or resolve โ€” turning 'what's paging us right now' into a chat answer.

Official PagerDuty Incident MCP Endpoint & Transport Architecture

  • Endpoint URL: https://mcp.pagerduty.com/mcp
  • Transport: Streamable HTTP

Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. PagerDuty Incident MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.

Authentication, Scopes & Permission Boundaries

PagerDuty Incident MCP uses OAuth 2.1 โ€” the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ€” PKCE and Dynamic Client Registration, so no manual client setup is needed โ€” and simply open a browser consent screen.

Of the 6 cataloged tools, 4 are read-only and 2 can write or mutate state (create resources, run SQL, post messages). Grant access only to the accounts and projects you intend agents to act on, and prefer scoped credentials or a dedicated workspace where the provider supports them.

Common Troubleshooting & Connection Tips

  • 401 Unauthorized on connect โ€” that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact WWW-Authenticate challenge.
  • "Session expired" / stale Mcp-Session-Id โ€” just re-send initialize; stateless clients can ignore session headers entirely.
  • Acknowledge/resolve are mutating operations โ€” they act as your PagerDuty user.
  • Use scoped OAuth to restrict the agent to the teams that matter.

๐Ÿš€ How to Connect

  1. Copy the PagerDuty Incident MCP endpoint URL
    The remote endpoint is https://mcp.pagerduty.com/mcp.
  2. Add it to your MCP client
    Claude Code: claude mcp add --transport http pagerduty https://mcp.pagerduty.com/mcp. Cursor: add "pagerduty": { "url": "https://mcp.pagerduty.com/mcp" } under mcpServers in ~/.cursor/mcp.json. Other clients work similarly.
  3. Complete the OAuth consent
    On first connection your client opens a PagerDuty consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
  4. Verify with the online inspector
    Paste https://mcp.pagerduty.com/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm PagerDuty Incident MCP's 6 tools respond.

โ“ FAQ

What is the PagerDuty Incident MCP remote MCP endpoint?

The primary endpoint is https://mcp.pagerduty.com/mcp. It is an official first-party server operated by PagerDuty, speaking the Streamable HTTP transport.

How do I authenticate with PagerDuty Incident MCP?

PagerDuty Incident MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.

I'm getting a 401 Unauthorized from PagerDuty Incident MCP โ€” what's wrong?

A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.

Which MCP clients work with PagerDuty Incident MCP?

Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http pagerduty https://mcp.pagerduty.com/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.

What tools does PagerDuty Incident MCP expose?

6 tools are cataloged in this directory โ€” including `list_incidents`, `get_incident`, `acknowledge_incident` and more. Use our online inspector to fetch the live tool list straight from the endpoint.

๐Ÿ”— Connect Guides

โš”๏ธ Featured in Comparisons

๐Ÿ“› Embed Status Badge in README

PagerDuty Incident MCP status badge
[![Remote MCP Status](https://remotemcp.net/api/badge/status/pagerduty.svg)](https://remotemcp.net/servers/pagerduty)
PagerDuty Incident MCP inspector badge
[![Test in Inspector](https://remotemcp.net/api/badge/inspect/pagerduty.svg)](https://remotemcp.net/inspector?url=https%3A%2F%2Fmcp.pagerduty.com%2Fmcp)
PagerDuty Incident MCP audit grade badge
[![MCP Audit Grade](https://remotemcp.net/api/badge/grade/pagerduty.svg)](https://remotemcp.net/servers/pagerduty)
PagerDuty Incident MCP context tax badge
[![Context Tax](https://remotemcp.net/api/badge/tokens/pagerduty.svg)](https://remotemcp.net/servers/pagerduty)

Related Servers

AWS KnowledgeAmazon Web Services

AWS Knowledge's hosted remote MCP server. AWS's fully-managed public knowledge MCP gives agents access to the latest AWS documentation, API references, What's New posts and architectural guidance across all AWS services. It is public and unauthenticated โ€” connect and call tools immediately.

https://knowledge-mcp.global.api.aws
๐Ÿ›ก๏ธ Officialโœ“ VerifiedStreamable HTTPPublic ยท No Auth๐Ÿ›ก๏ธ A+~1896 tok5 toolsOnline178ms

Cloudflare's free, authless documentation MCP server. Agents can search the full Cloudflare docs corpus โ€” no account or token required.

https://docs.mcp.cloudflare.com/mcp
๐Ÿ›ก๏ธ Officialโœ“ VerifiedHTTP + SSEPublic ยท No Auth๐Ÿ›ก๏ธ A+~271 tok2 toolsOnline7ms

Vercel's official remote MCP server. Agents can list deployments, fetch build logs and search Vercel docs with a token-authorized connection.

https://mcp.vercel.com
๐Ÿ›ก๏ธ Officialโœ“ VerifiedStreamable HTTPOAuth 2.1๐Ÿ›ก๏ธ A+~506 tok16 toolsOnline210ms

Sentry's hosted MCP server for error monitoring. Agents can inspect issues, search events and resolve regressions directly from your IDE.

https://mcp.sentry.dev/mcp
๐Ÿ›ก๏ธ Officialโœ“ VerifiedHTTP + SSEOAuth 2.1๐Ÿ›ก๏ธ A+~575 tok18 toolsOnline62ms