PagerDuty MCP Server

Official PagerDuty MCP server enabling AI agents to manage incidents, on-call schedules, services, and escalation policies — turning agents into active participants in incident response.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Monitoring pagerduty incident-management on-call alerting mcp-server official sre devops
⚙ Agent Friendliness
84
/ 100
Can an agent use this?
🔒 Security
89
/ 100
Is it safe for agents?
⚡ Reliability
88
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
80
Documentation
88
Error Messages
84
Auth Simplicity
88
Rate Limits
82

🔒 Security

TLS Enforcement
100
Auth Strength
88
Scope Granularity
82
Dep. Hygiene
85
Secret Handling
88

HTTPS enforced. Read-only API keys available. Strong access control for multi-team environments.

⚡ Reliability

Uptime/SLA
98
Version Stability
88
Breaking Changes
85
Error Recovery
82
AF Security Reliability

Best When

An AI agent needs to participate in incident response — triaging alerts, acknowledging pages, routing to the right person, or generating incident summaries.

Avoid When

You need metric collection, log aggregation, or deployment tracking — PagerDuty is incident management, not observability.

Use Cases

  • Creating and resolving incidents programmatically from agents
  • Querying on-call schedules to route issues to the right person
  • Listing and filtering active incidents by service or severity
  • Acknowledging and escalating incidents in automated workflows
  • Generating incident summaries and post-mortem data for agents

Not For

  • Real-time metric collection (use Prometheus/Datadog for that)
  • Teams without a PagerDuty subscription
  • Non-incident use cases like project management or deployment

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
Yes

Authentication

Methods: api_key oauth2
OAuth: Yes Scopes: Yes

REST API key (user or account-level) for MCP server. OAuth 2.0 available for user-specific actions. API keys can be scoped to read-only for safe agent access.

Pricing

Model: per-seat
Free tier: Yes
Requires CC: No

Requires active PagerDuty subscription. The MCP server itself is open source.

Agent Metadata

Pagination
offset
Idempotent
Partial
Retry Guidance
Documented

Known Gotchas

  • Rate limit is 960 req/min per account — shared across all API users, not per key
  • Incident IDs are alphanumeric strings (not integers) — easy to mix up in agent context
  • On-call schedule queries require knowing the schedule ID — discovery requires a separate call
  • Webhook payloads use a different schema than REST API responses — check type carefully
  • Resolving an incident requires it to be acknowledged first in some configurations

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for PagerDuty MCP Server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-06.

5565
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered