PagerDuty MCP Server (Official)

Official PagerDuty MCP server enabling AI agents to interact with PagerDuty's incident management platform — querying incidents, managing on-call schedules, triggering alerts, acknowledging and resolving incidents, and accessing service health data.

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

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

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

HTTPS enforced. User-scoped API keys. OAuth2. FedRAMP, SOC 2, ISO 27001, GDPR, HIPAA.

⚡ Reliability

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

Best When

An agent needs to query or manage incidents, on-call schedules, or service health in a PagerDuty-powered operations environment.

Avoid When

You're using OpsGenie, VictorOps, or another incident management platform.

Use Cases

  • Querying active incidents and severity from incident response agents
  • Acknowledging and resolving incidents from automated remediation agents
  • Checking on-call schedules for escalation routing agents
  • Triggering alerts from monitoring and detection agents
  • Summarizing incident history for post-mortem analysis agents
  • Managing escalation policies from workflow automation agents

Not For

  • Teams using OpsGenie, VictorOps, or Rootly for incident management
  • Service monitoring setup (use Datadog, Prometheus for that)
  • Non-incident-management use cases

Interface

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

Authentication

Methods: api_key oauth2
OAuth: Yes Scopes: Yes

PagerDuty API keys (user-level) or OAuth2 apps. API keys have read/write scope per resource type. Service accounts recommended for agents.

Pricing

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

Per-seat pricing. Free tier available. Enterprise customers often have custom plans. MCP server is open source.

Agent Metadata

Pagination
cursor
Idempotent
Full
Retry Guidance
Documented

Known Gotchas

  • Service IDs and escalation policy IDs required — discover these before triggering alerts
  • Incident acknowledgment changes on-call routing — understand implications
  • API keys are user-level — actions appear as that user in audit logs
  • Webhooks v3 vs v2 have different payload formats
  • Rate limits are per-account — shared across all integrations
  • Incidents have complex state machines — acknowledge before resolving

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for PagerDuty MCP Server (Official).

$99

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

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