OPERATIONS AND INCIDENTS / PagerDuty
PagerDuty Hosted MCP
PagerDuty’s current hosted connection for incident, service and on-call workflows under an authorized account.
“Connect AI tools to PagerDuty with MCP to securely manage incidents, services and on-call schedules”
01 / THE REASONING
Why this made the selection.
- Provides an official account-aware path from incident context to service and schedule operations.
- The current guide explicitly distinguishes hosted authentication and permissions from the deprecated local server.
- PagerDuty’s support page describes a hosted MCP server that needs no local install and accepts OAuth or an API key.
- The same page, and the GitHub blob named on this row, say the self-hosted repository is archived and read-only.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Current official hosted setup, regional endpoints and authentication/permissions sections
- Archived local repository deprecation notice
- https://support.pagerduty.com/main/docs/pagerduty-mcp-server
- https://github.com/PagerDuty/pagerduty-mcp-server/blob/dcfbdb82e1a63584bf5c37b43007561498b06dc7/README.md
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- The current docs recommend the hosted service and explicitly deprecate the local repository.
- No private hosted implementation was available for inspection; this is a documentation and lifecycle review.
- The support page says the PagerDuty-hosted MCP server connects an assistant without a local install and supports OAuth and API keys.
- It says the client for that hosted server must support remote HTTP MCP servers.
- Both the support page and the listed GitHub blob say the self-hosted repository is archived and read-only. The blob banner dates that archive to Sep 4, 2026.
- The former self-hosted server is deprecated; the hosted service supports API keys and distinct OAuth token/client paths.
Not established by this review
- No MCP server or upstream package was installed or run.
- No authenticated account, API request, client handshake or write operation was tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Choose the hosted endpoint for the account region: https://mcp.pagerduty.com/mcp or https://mcp.eu.pagerduty.com/mcp.
- Configure the documented API-key flow or pre-register an OAuth client with the required redirect details.
- Choose least-privilege account/scopes for the actual incident workflow and inspect tool calls before making changes.
Before you start
- A PagerDuty account with the documented Advanced Permissions capability
- An appropriate user/account API key or a registered OAuth client
- A client that supports remote HTTP MCP and the selected authentication flow
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"pagerduty": {
"url": "https://mcp.pagerduty.com/mcp"
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Official service setup ↗Checked
https://support.pagerduty.com/main/docs/pagerduty-mcp-server
Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access
https://github.com/PagerDuty/pagerduty-mcp-server/blob/dcfbdb82e1a63584bf5c37b43007561498b06dc7/README.md
Supports: install, compatibility, review, limitations, access