---
title: "PagerDuty Hosted MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/pagerduty/
description: "PagerDuty’s current hosted connection for incident, service and on-call workflows under an authorized account."
---

# PagerDuty Hosted MCP: review, setup & limitations · Undominated.ai

> PagerDuty’s current hosted connection for incident, service and on-call workflows under an authorized account.

[← Explore all mcp servers](/mcp-servers/)

OPERATIONS AND INCIDENTS / PagerDuty

# PagerDuty Hosted MCP

PagerDuty’s current hosted connection for incident, service and on-call workflows under an authorized account.

 [See setup guidance ↓](#setup)[Original source ↗](https://support.pagerduty.com/main/docs/pagerduty-mcp-server)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 2 linked sources
 Publisher PagerDuty
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“Connect AI tools to PagerDuty with MCP to securely manage incidents, services and on-call schedules”

 [PagerDuty · upstream description ↗](https://support.pagerduty.com/main/docs/pagerduty-mcp-server) Our analysis follows below.

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.

### A good fit for

 - Retrieving incident context and on-call information during an investigation
- Performing deliberately approved incident or schedule operations
- Connecting a remote-capable MCP client to PagerDuty with OAuth or an API key
- Not for continuing to develop the archived local repository

### Weigh up before choosing

 - The self-hosted repository is deprecated and read-only. Its old defaults and MIT licence do not establish the hosted service’s behavior or licensing.
- Hosted tool filtering is not available in the reviewed guide; use appropriate OAuth scopes and account permissions to limit which operations succeed.
- This connector can write to PagerDuty. Static OAuth client registration is required where OAuth is used; automatic dynamic registration is not supported.
- Some filters require user-level authentication. A bare endpoint URL is insufficient unless the client completes the required authentication flow.
- The hosted client must support remote HTTP MCP servers. A local-only client is outside that requirement.
- The archived repository notice is a GitHub banner on the listed blob, not a new commit hash for this row.
- No licence was stated on the support page, and none was inferred.
- This review did not execute the resource.
- The server was not called.
- API-key Token token= and OAuth Bearer authentication are different header forms; swapping them can fail even with valid credentials.

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.

[Upstream setup instructions ↗](https://support.pagerduty.com/main/docs/pagerduty-mcp-server)
 - 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"
 }
 }
} Copy configuration ↗

### Compatibility

Claude Desktop · Cursor · VS Code

### Transports

Streamable HTTP

### Hosted account connection

 - Read incident, service and on-call data allowed by the account
- Permitted tools can modify incidents, services, schedules and related resources
- OAuth scopes and account roles govern effective access; this is not a local read-only mode

### Cost model

Hosted service under PagerDuty account and feature terms; assistant usage is separate. The old local implementation’s licence is not a hosted-service entitlement.

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 ↗](https://support.pagerduty.com/main/docs/pagerduty-mcp-server) Checked 2026-10-14 https://support.pagerduty.com/main/docs/pagerduty-mcp-server Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access
- [Deprecated local repository notice ↗](https://github.com/PagerDuty/pagerduty-mcp-server/blob/dcfbdb82e1a63584bf5c37b43007561498b06dc7/README.md) Checked 2026-10-14 https://github.com/PagerDuty/pagerduty-mcp-server/blob/dcfbdb82e1a63584bf5c37b43007561498b06dc7/README.md Supports: install, compatibility, review, limitations, access

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Apollo MCP Server ↗ Exposes a chosen set of GraphQL operations as MCP tools backed by an existing graph.](/mcp-servers/apollo/)[### Checkly MCP Server ↗ Checkly's hosted MCP server over Streamable HTTP: inspect check status and results, test sessions, RCA and result assets, trigger deployed checks, manage monitors and groups, environment variables and status-page incidents. OAuth is recommended; user and service API keys are the documented alternatives.](/mcp-servers/checkly/)[### Datadog MCP ↗ Query Datadog telemetry and operate permitted monitoring resources from an authenticated AI client.](/mcp-servers/datadog/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
