Skip to content

PagerDuty Copilot

PagerDuty Copilot focuses on Incident assist → Dev & IT → Automate workflows.

shipped Nov 14, 2025automatepaid
Read full review
Visit PagerDuty Copilot
AutomateDev & ITIncident assist
PagerDuty Copilot - AI tool hero image
1Automate
2Dev & IT
3Incident assist

Stork Quadrant

Sleeping Giant· 47/100

Has a real moat but invisible to agents. Add an MCP and you'd climb.

PagerDuty Copilot survives because it's embedded in a coordination layer that orchestrates on-call rotations, escalations, and multi-team response — an LLM can't replace the rails. The network effect (teams depend on shared incident data, integrations, and trust in who's on call) and the trust moat (wrong incident response kills production) create real defensibility. The tool's value isn't the AI suggestions; it's that those suggestions flow through PagerDuty's coordination engine to the right people at the right time.

Claude Haiku 4.5, scored 2026-05-25

Defensibility · 60/100

  • Physical-world coupling
  • Regulatory moat
  • Network liquidity
  • Proprietary refreshing data
  • High-trust catastrophic workflows
  • Multi-party coordination
  • Brand / community / taste

An LLM alone could replace

  • Summarize incident timeline and context from logs
  • Generate runbook suggestions based on incident type
  • Draft initial incident communication to stakeholders
  • Propose remediation steps from historical incident patterns

Agent-Readiness · 30/100

  • Verified MCP
  • Listed on agent surfaces
  • Usage-based pricing
  • Headless agent authhttps://www.pagerduty.com/docs (api-key auth)
  • Public OpenAPI
  • Active changeloghttps://www.pagerduty.com/blog/ (2026-03-03)
  • llms.txthttps://www.pagerduty.com/llms.txt

How to defend

Double down on coordination: make Copilot the decision layer that doesn't just suggest but orchestrates — auto-triggering runbooks, auto-escalating, auto-notifying based on incident severity and team context. Own the incident-response data layer so competitors can't replicate your pattern library without years of customer incident history.

  • Ship an MCP server and list it on Stork — biggest single point gain (+25).
  • Get listed in the Anthropic MCP registry, Cursor, or Claude Desktop (+20).
  • Add a usage-based or per-call tier; per-seat-only pricing dies when agents replace seats (+15).
  • Publish an OpenAPI spec at /openapi.json or /.well-known/openapi (+10).

Similar Tools

Compare Alternatives

Other tools you might consider

Connect

overview

Overview

PagerDuty Copilot focuses on Incident assist → Dev & IT → Automate workflows.

For builders

This page is doing a job for someone else’s tool.

AI agents read it. Buyers find it. Backlinks accrue. Your tool can have one too — live in 24 hours, indexed by Claude, ChatGPT, and Perplexity, queryable via MCP.