MCP100 IndexMonitoring & Observability

ShortlistFirst-party MCP

PagerDuty MCP

by PagerDuty

Updated September 24, 2026

Monitoring & ObservabilityCybersecurityAccess · Hosted

MCP100 verdict

Connect AI clients to PagerDuty incidents, on-call, schedules, escalation, and related incident-response workflows.

MCP100 Assessment

Editorial verdict

Promising incident-response tooling, but it remains on the Shortlist until account scopes, incident-changing actions, regional endpoint behavior, sensitive operational data, and failure handling are independently reviewed.

Reviewed July 24, 2026

Task Fit

Mapped

Specialized workflows

Trust

Status warning

hosted_destructive_tools_without_direct_tool_filter_or_mandatory_confirmation

Maintenance

Activity observed

A dated repository or package update is available; editorial maintenance review is still pending.

Popularity

Signals unavailable

No independently comparable adoption metric is currently stored.

Best for

Connect compatible AI clients to PagerDuty's documented MCP capabilities.

Not ideal for

Users who need a fully reviewed MCP100 recommendation today

Avoid if

Permissions, credentials, and connected data cannot be tested with least privilege

Trade-offs

Publisher attribution supports discovery, but does not replace an independent permissions and usability review.

Evidence scope

Evidence

Current source snapshot

Popularity

75 shared-repository stars · not MCP-specific

PagerDuty-hosted MCP · no comparable public usage metric

Current PagerDuty MCP is hosted. The archived self-hosted repository and pagerduty-mcp PyPI package are legacy/deprecated and are excluded from current adoption.

Stars observed August 14, 2026 · Downloads observed September 8, 2026

Reviewed legacy_archived_local; context only and not exact MCP ranking evidence.

Reviewed legacy_local_or_none_current_hosted; context only and not exact MCP ranking evidence.

Maintenance

Publisher activity observed September 14, 2026

Current source snapshot

Trust review

Source relationship: First-party MCP

Reviewed July 24, 2026

Sources

GitHub repository ↗Official setup docs ↗

Evidence-backed setup

Install & Agents

Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.

Claude Code

Streamable HTTP

MCP100 logic checked

claude mcp add --transport http pagerduty "https://mcp.pagerduty.com/mcp"

The publisher connection details were combined with this client's official MCP transport configuration; installation was not executed by MCP100.

Verify safely: Reconnect Claude Code, complete the publisher OAuth or authentication flow if prompted, confirm pagerduty tools are listed, and perform one read-only test.

Uninstall and revoke

Remove pagerduty from Claude Code, clear its stored MCP OAuth credentials, and revoke the publisher authorization if it is no longer needed.

Evidence & methodology

Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.

Evidence checked 2026-07-24

Evidence 1 ↗Evidence 2 ↗

Read additional publisher installation details

From the publisher README

Publisher installation details

Original client setup and configuration retained from the publisher documentation.

View original README ↗

Publisher-documented clients

Claude DesktopCursorVS Code

These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.

Quick start

You need uv and a PagerDuty User API Token — see Prerequisites and Authentication.

PAGERDUTY_USER_API_KEY="your-token" uvx pagerduty-mcp

By default only read-only tools are exposed. Add --enable-write-tools to allow tools that modify your PagerDuty account. Then point your MCP client at the server — Cursor, VS Code, Claude Desktop, or Docker.

Prefer no local install? PagerDuty hosts a Remote MCP Server with OAuth support.

Loading optional publisher installation details…

Capability

What it does

Connect compatible AI clients to PagerDuty's documented MCP capabilities.

Monitoring & ObservabilityCybersecurity

Representative uses

Connect compatible AI clients to PagerDuty's documented MCP capabilities.

Important limits

Users who need a fully reviewed MCP100 recommendation today

Tools82 toolsView tools

Alert grouping5 tools
Create, inspect, update, and remove PagerDuty alert-grouping settings.
Analytics5 tools
Retrieve incident and responder metrics for operational analysis.
Business services3 tools
Inspect PagerDuty business services and their service dependencies.
Change events4 tools
Inspect change events and relate them to incidents or services.
Event orchestrations7 tools
Inspect and modify event-orchestration configuration and routing rules.
Escalation policies4 tools
Create, inspect, list, and update escalation policies.

View 12 more capabilities

Incidents12 tools
Create, inspect, enrich, and manage incidents, alerts, responders, notes, and related incident context.
Incident workflows3 tools
Inspect and start predefined incident workflows.
Log entries2 tools
Inspect PagerDuty log entries associated with account activity or incidents.
Teams8 tools
Create, inspect, update, and manage team membership.
Users2 tools
Inspect PagerDuty users and account-level user information.
On-call1 tool
Inspect who is currently on call.
Priorities1 tool
List incident priorities.
Schedules6 tools
Inspect and manage schedules, users, and schedule overrides.
Services4 tools
Create, inspect, list, and update PagerDuty services.
Status pages8 tools
Create and inspect status-page posts, updates, impacts, severities, and statuses.
Webhooks5 tools
Create, inspect, update, and remove webhook integrations used for event delivery.
Extension schemas2 tools
Inspect PagerDuty extension schemas.

View tool names (82)

create_alert_grouping_setting
delete_alert_grouping_setting
get_alert_grouping_setting
list_alert_grouping_settings
update_alert_grouping_setting
get_incident_metrics_all
get_incident_metrics_by_service
get_incident_metrics_by_team
get_responder_load_metrics
get_responder_metrics
get_business_service_dependencies
get_technical_service_dependencies
list_business_services
get_change_event
list_change_events
list_incident_change_events
list_service_change_events
get_event_orchestration
get_event_orchestration_global
get_event_orchestration_router
get_event_orchestration_service
list_event_orchestrations
update_event_orchestration_router
append_event_orchestration_router_rule
create_escalation_policy
get_escalation_policy
list_escalation_policies
update_escalation_policy
add_note_to_incident
add_responders
create_incident
get_alert_from_incident
get_incident
get_outlier_incident
get_past_incidents
get_related_incidents
list_alerts_from_incident
list_incident_notes
list_incidents
manage_incidents
get_incident_workflow
list_incident_workflows
start_incident_workflow
get_log_entry
list_log_entries
add_team_member
create_team
delete_team
get_team
list_team_members
list_teams
remove_team_member
update_team
get_user_data
list_users
list_oncalls
list_priorities
create_schedule_override
get_schedule
list_schedule_users
list_schedules
create_schedule
update_schedule
create_service
get_service
list_services
update_service
create_status_page_post
create_status_page_post_update
get_status_page_post
list_status_page_impacts
list_status_page_post_updates
list_status_page_severities
list_status_page_statuses
list_status_pages
create_webhook_subscription
delete_webhook_subscription
get_webhook_subscription
list_webhook_subscriptions
update_webhook_subscription
get_extension_schema
list_extension_schemas

The current official README table has 82 tools: 55 read-only and 27 write-capable.

Source: Official source

Context Footprint

Varies by configuration

Estimated token footprint of the MCP tool schemas exposed to the agent.

~16,400 schema tokens is an Approx. catalog/reference estimate, not Runtime Verified.

Read publisher documentation

Publisher documentation

Publisher README

Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.

View original README ↗

PagerDuty's official MCP Server

[!IMPORTANT] This repository is deprecated and now read-only. Development has moved to PagerDuty's hosted Remote MCP Server — see the docs there for setup instructions.

PagerDuty's local MCP (Model Context Protocol) server which provides tools to interact with your PagerDuty account, allowing you to manage incidents, services, schedules, event orchestrations, and more directly from your MCP-enabled client.

The full documentation lives in docs/ and is readable directly on GitHub.

Getting Started

Introduction — what the MCP server is and what it can do
Prerequisites
Quick Start
Authentication

Installation

Remote Server

Remote MCP Server Setup — PagerDuty-hosted, no local install. Maintained on the PagerDuty Knowledge Base.

Configuration

Tools Reference

Tools Overview — every tool, read/write type, and description
Alert Grouping
Alerts
Analytics
Business Services
Change Events
Incidents
Incident Workflows
Services
Teams
Users
Schedules
On-Call
Priorities
Log Entries
Escalation Policies
Event Orchestrations
Status Pages

Use Cases

Experimental

Experimental Overview — MCP Apps and the experimental branch
Incident Command Center
On-Call Manager
On-Call Compensation Report
Service Dependency Graph
Onboarding Wizard

Community

Community Streams

Contributing

Support

PagerDuty's MCP server is an open-source project, and as such, we offer only community-based support. If assistance is required, please open an issue in GitHub or PagerDuty's community forum.

Contributing

If you are interested in contributing to this project, please refer to our Contributing Guidelines and the development setup guide.

Loading optional publisher documentation…

FAQ

What can PagerDuty MCP do?

Connect compatible AI clients to PagerDuty's documented MCP capabilities.

Can PagerDuty MCP inspect or manage incidents and on-call workflows?

Yes. The reviewed server covers incidents, incident workflows, on-call schedules, escalation policies, services, teams, event orchestration, status pages, webhooks, and related PagerDuty operations. By default it exposes read-only tools; write-capable tools require the write-tools option.

Does PagerDuty MCP work with Claude Code?

Yes. MCP100 reviewed an evidence-backed setup for Claude Code, but has not independently verified it with a live runtime test.

How does PagerDuty MCP authenticate?

Follow only the publisher source; credential storage, scopes, and revocation remain under review.

What operational risks should I consider before enabling write actions?

Use a test account, least privilege, read-only controls where available, and explicit approval for mutations.

Is this an official MCP?

PagerDuty is listed as First-party MCP in MCP100’s current evidence.

Current official resources:

Publisher documentation ↗

PagerDuty's official MCP Server

[!IMPORTANT] This repository is deprecated and now read-only. Development has moved to PagerDuty's hosted Remote MCP Server — see the docs there for setup instructions.

The full documentation lives in docs/ and is readable directly on GitHub.

Getting Started

Introduction — what the MCP server is and what it can do
Prerequisites
Quick Start
Authentication

Installation

Remote Server

Remote MCP Server Setup — PagerDuty-hosted, no local install. Maintained on the PagerDuty Knowledge Base.

Configuration

Tools Reference

Tools Overview — every tool, read/write type, and description
Alert Grouping
Alerts
Analytics
Business Services
Change Events
Incidents
Incident Workflows
Services
Teams
Users
Schedules
On-Call
Priorities
Log Entries
Escalation Policies
Event Orchestrations
Status Pages

Use Cases

Experimental

Experimental Overview — MCP Apps and the experimental branch
Incident Command Center
On-Call Manager
On-Call Compensation Report
Service Dependency Graph
Onboarding Wizard

Community

Community Streams

Contributing

Support

PagerDuty's MCP server is an open-source project, and as such, we offer only community-based support. If assistance is required, please open an issue in GitHub or PagerDuty's community forum.

Contributing

If you are interested in contributing to this project, please refer to our Contributing Guidelines and the development setup guide.

PagerDuty MCP

Promising incident-response tooling, but it remains on the Shortlist until account scopes, incident-changing actions, regional endpoint behavior, sensitive operational data, and failure handling are independently reviewed.

Best for

Not ideal for

Avoid if

Trade-offs

Evidence

Popularity

Maintenance

Trust review

Sources

Install & Agents

Claude Code

Publisher installation details

Quick start

What it does

Representative uses

Important limits

Context Footprint

Access & risk

Other options

MCP Server for Splunk platform

Grafana Cloud MCP

Datadog MCP

Publisher README

PagerDuty's official MCP Server

Contents

Support

Contributing

FAQ

Publisher installation details

Quick start

Publisher README

PagerDuty's official MCP Server

Contents

Support

Contributing