summaryPagerDuty MCP Server by PagerDuty — Incident management MCP on the Scrums.com enterprise catalog. Gateway grade A: gateway-ready. Deployable through the Scrums.com MCP Gateway.Priced on scope·★ 5.0·● available now·vetted by Scrums.com

mcp servers · CAT-30031014 · rev 1.0

PagerDuty MCP Server. @pagerduty-mcp-server

MCP Serversmcp · pagerduty · incidents · on callPagerDuty● available now

5.0Reviews ▾

Rated 5.0 / 5 by clients on GoodFirms.

Read verified reviews on GoodFirms →

Vetted by Scrums.com Platform

Provider PagerDuty

Last review 2026-09-14

What you get

the numbers that matter

Starting price

Priced on scope

starting price

Ready in

≈ 2 weeks

signed to first PR

Retention

96%

engagements renewed

Match

96%

to your stack & domain

PagerDuty MCP Server gives approved AI clients access to incidents, on-call schedules, escalation policies and operational response context. It is most valuable where teams want to give incident agents direct access to who is on call and what is happening during an outage.

How this operator works

every way of working, already decided

A · capability focus

Owns the system, not the ticket

Takes end-to-end ownership of a service or surface. Design, delivery, on-call. And is measured on outcomes, not hours.

B · ways of working

Embedded, async-first, instrumented

Works inside your repos, your CI and your rituals. Daily written standups, decisions logged. No status-meeting tax.

C · reliability posture

Runbooks, canaries, reversible deploys

Every change gated and reversible. Incidents get a timeline and a postmortem; nothing ships without a rollback.

D · comms & cadence

Plugged into your Slack & rituals

Joins standups and retros, reports weekly against the goal. You get an operator, not a queue.

E · tooling

Brings a pre-wired stack or adopts yours

Infrastructure and observability as code by default. No bespoke setup tax to absorb.

F · onboarding

Scoped, gated, reversible

Week-1 shadow, week-2 ownership, swap on request inside the trial window. No long-tail handover risk.

What it connects

What engineering teams can do

Example workflow: Summarize active Sev-1 incidents, identify the on-call responder for payments and show the current escalation state.

Enterprise MCP Gateway deployment

Grade A (gateway-ready): vendor-managed remote HTTP/OAuth or similarly strong enterprise control. Default posture: list and enable after connector certification.

Server-specific posture: Separate incident read context from acknowledge/resolve/escalation writes; preserve PagerDuty roles.

What's included

in every engagement · no add-ons

✓Embedded operatorfull-time, in your timezone overlapincl.

✓Daily written standuplogged, async, searchableincl.

✓Code review & pairingon your PRs, dailyincl.

✓Weekly progress reportagainst the goalincl.

✓Scrums.com delivery managerescalation + cadence ownerincl.

✓No-fault replacement guaranteecovered for the engagementincl.

Track record

deployments on real systems · anonymized

Sector	System	Outcome	Span	Status
Fintech	payments-core ledger	99.97% achieved	14 mo	● complete
Commerce	checkout platform	−38% incident rate	9 mo	● complete
Health SaaS	data plane	0 SEV1 in 6 mo	11 mo	● active
Logistics	routing engine	zero-downtime cutover	7 mo	● complete
AI infra	inference cluster	p99 −120 ms	5 mo	● active

Works inside your stack

surfaces this operator binds to

Surface	Binding	Direction	Auth
Source control	github.com/<org>	reviews + writes	OIDC
CI / CD	scm-flow · deploy-service	gates deploys	OIDC
Observability	otlp://collector:4317	metrics + alerts	mTLS
Comms	slack://<workspace>	standups, incidents	SSO
Secrets	vault://scrums/op/<id>	short-lived creds	SPIFFE
On-call	pagerduty://<org>	primary / secondary	API token

Boundaries

what to deploy instead

Scoped to this discipline. For an adjacent capability, compose a second operator into the squad. compose →

Not a fractional advisory engagement. For advisory-only, contact platform@scrums.com.

Deployments

the only social proof we publish

402deploys

across 38 organizations

+24 last 30 days · median age 11.4 mo · retention 96%

Pricing

one number · one footnote

starting price

Priced on scope

All-in: the operator, delivery manager and replacement guarantee. No recruiter fee, no markup surprises.

Final pricing computed at deploy from your committed envelope, region and account tier.

FAQ

common questions

How is PagerDuty MCP Server priced?

Priced on scope. Request a quote and pricing is computed from the work envelope.

Is PagerDuty MCP Server available now?

Yes. It is published and deployable directly from the Scrums.com catalog.

Can a PagerDuty MCP Server deployment be reversed?

Yes. Deployments are reversible with a one-click swap inside the trial window.

Who provides PagerDuty MCP Server?

PagerDuty, vetted by the Scrums.com platform.

How it compares

vs other MCP servers

Option	From	Stack	Status
PagerDuty MCP Server · this one	Priced on scope	mcp · pagerduty · incidents	● available
GitHub MCP Server	Priced on scope	mcp · github · source control	● available
GitLab MCP Server	Priced on scope	mcp · gitlab · merge requests	● available
Managed MCP Gateway	Priced on scope	mcp · platform · governance	● available

Commonly deployed with

more MCP servers

More MCP servers

GitHub MCP Server

GitHub MCP Server gives approved AI clients access to repositories, issues, pull requests, branches, code search and common GitHub workflows. It is most valuable where teams want to give coding agents governed access to the system where engineering work is reviewed and merged.

GitHubmcpgithubsource controlSee options →

GitLab MCP Server

Use GitLab MCP Server to connect engineering agents with gitLab projects, merge requests, issues and related DevSecOps context across GitLab deployments. The key operational benefit is to bring source, planning and pipeline context into agents for GitLab-centric engineering organizations.

GitLabmcpgitlabmerge requestsSee options →

Managed MCP Gateway

One governed Model Context Protocol endpoint for your whole organisation. Connect your tools once, scope them per team and per agent, and see every call every agent makes.

mcpplatformgovernanceSee options →

starting price

Priced on scope