PagerDuty Official Remote MCP Server
PagerDuty's hosted MCP (mcp.pagerduty.com/mcp) exposes incidents, services, on-call schedules and escalation policies to agents over OAuth 2.1.
- Provider
- PagerDuty โ
- Categories
- โ๏ธ Cloud, Infrastructure & DevOps
ไธญๆ็ฎไป
PagerDuty ๅฎๆน่ฟ็จ MCP ๆๅกๅจใAI ไปฃ็ๅฏ้่ฟ OAuth ๅๅบๅๅ่ฏไบไปถใๆฅ็ๅผ็ญ่กจ๏ผๅนถ็กฎ่ฎคๆ่งฃๅณไบไปถใ
Maintainer of PagerDuty Incident? Claim or update this listing โ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"pagerduty": {
"url": "https://mcp.pagerduty.com/mcp"
}
}
}claude mcp add --transport http pagerduty https://mcp.pagerduty.com/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"pagerduty": {
"type": "http",
"url": "https://mcp.pagerduty.com/mcp"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.pagerduty.com/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"pagerduty": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.pagerduty.com/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"pagerduty": {
"serverUrl": "https://mcp.pagerduty.com/mcp"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"pagerduty": {
"url": "https://mcp.pagerduty.com/mcp"
}
}
}Add to ~/.codex/config.toml โ Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.pagerduty] url = "https://mcp.pagerduty.com/mcp"
Add to cline_mcp_settings.json (Cline โ MCP Servers โ Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"pagerduty": {
"type": "streamableHttp",
"url": "https://mcp.pagerduty.com/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers โ httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"pagerduty": {
"httpUrl": "https://mcp.pagerduty.com/mcp"
}
}
}๐งฐ PagerDuty Incident MCP Tools & Schema (6)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| list_incidents ~71 tok | ๐ข Read | List incidents filtered by status and service. | status: stringserviceId: string |
| get_incident ~57 tok | ๐ข Read | Get incident details including alerts and log entries. | incidentId*: string |
| acknowledge_incident ~51 tok | ๐ Write | Acknowledge an incident. | incidentId*: string |
| resolve_incident ~68 tok | ๐ Write | Resolve an incident with a note. | incidentId*: stringresolution: string |
| list_services ~45 tok | ๐ข Read | List PagerDuty services. | query: string |
| get_oncall ~59 tok | ๐ข Read | Get who is currently on call for a schedule or escalation policy. | scheduleId*: string |
๐ก๏ธ Security, Quality & Context Token Audit
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)
๐งฉ 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-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; 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
- Copy the PagerDuty Incident MCP endpoint URLThe remote endpoint is https://mcp.pagerduty.com/mcp.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http pagerduty https://mcp.pagerduty.com/mcp. Cursor: add"pagerduty": { "url": "https://mcp.pagerduty.com/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn 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.
- Verify with the online inspectorPaste 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
Related Servers
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.
Cloudflare's free, authless documentation MCP server. Agents can search the full Cloudflare docs corpus โ no account or token required.
Vercel's official remote MCP server. Agents can list deployments, fetch build logs and search Vercel docs with a token-authorized connection.
Sentry's hosted MCP server for error monitoring. Agents can inspect issues, search events and resolve regressions directly from your IDE.