What can PagerDuty MCP Server do?

incident-list-and-filter-with-status-awareness, incident-acknowledgment-with-context-preservation, on-call-schedule-query-with-rotation-awareness, escalation-policy-trigger-with-notification-routing, incident-detail-retrieval-with-timeline-context, service-and-team-metadata-query, mcp-tool-schema-based-function-calling

PagerDuty MCP Server

MCP ServerFree

Manage PagerDuty incidents, alerts, and on-call schedules via MCP.

Open Source

/ 100

7 capabilities

Capabilities7 decomposed

incident-list-and-filter-with-status-awareness

Medium confidence

Retrieves paginated incident listings from PagerDuty API with real-time status filtering (triggered, acknowledged, resolved) and temporal sorting. Implements MCP tool protocol to expose PagerDuty's /incidents endpoint with query parameter mapping for urgency levels, service IDs, and date ranges, enabling Claude to query incident state without direct API knowledge.

Solves for

Get a real-time snapshot of all active incidents across servicesFilter incidents by urgency level to prioritize critical issuesQuery incidents within a specific time window for post-incident analysisIdentify which services are currently experiencing problems

Best for

DevOps teams using Claude for incident triage and status reporting

On-call engineers needing quick incident overview during handoffs

SRE teams building Claude-powered incident dashboards

Requires

PagerDuty API token with read:incidents scope

MCP client compatible with tool-calling (Claude 3.5+, other MCP-aware LLMs)

Network access to api.pagerduty.com

Limitations

Pagination limited to API response size — large incident volumes (>1000 active) may require multiple sequential calls

Real-time filtering happens client-side after API fetch, not server-side, adding latency for large datasets

No built-in caching — repeated queries within seconds hit the API each time, subject to rate limits

What makes it unique

Exposes PagerDuty incident querying as a native MCP tool, allowing Claude to reason about incident state and recommend actions without requiring developers to write custom API integration code. Uses MCP's schema-based tool definition to map PagerDuty query parameters to natural language filters.

vs alternatives

Simpler than building a custom PagerDuty integration for each Claude application; faster incident lookup than manual dashboard navigation because Claude can filter and summarize results in a single turn.

incident-acknowledgment-with-context-preservation

Medium confidence

Acknowledges incidents in PagerDuty by incident ID, optionally attaching a note explaining the acknowledgment reason. Implements MCP tool that calls PagerDuty's PUT /incidents/{id} endpoint with acknowledgement state transition, preserving incident context (timeline, assignees, escalation chain) while marking it as under investigation.

Solves for

Acknowledge an incident to prevent escalation while investigating root causeAdd context notes when acknowledging to communicate status to teamProgrammatically acknowledge multiple incidents in batch workflowsPrevent duplicate escalations by marking incidents as acknowledged

Best for

Automated incident response workflows triggered by Claude agents

On-call engineers using Claude as a command interface for PagerDuty

Teams building incident auto-remediation systems with human-in-the-loop approval

Requires

PagerDuty API token with write:incidents scope

Valid incident ID from PagerDuty (obtainable via incident-list capability)

MCP client with tool-calling support

Limitations

Acknowledgment is idempotent but provides no feedback if incident already acknowledged — silent success

Notes are appended to incident timeline but not searchable via this tool — requires separate incident detail query

No rollback capability — acknowledged incidents cannot be un-acknowledged via this tool

What makes it unique

Wraps PagerDuty's incident acknowledgment API as an MCP tool with optional note attachment, enabling Claude to acknowledge incidents and provide context in a single action. Preserves full incident state (escalation chain, assignees, timeline) while transitioning status.

vs alternatives

More integrated than manual dashboard acknowledgment because Claude can acknowledge incidents as part of a multi-step investigation workflow; safer than raw API calls because MCP schema validation prevents malformed requests.

on-call-schedule-query-with-rotation-awareness

Medium confidence

Queries PagerDuty on-call schedules to retrieve current and upcoming on-call assignments, including rotation information, escalation policies, and handoff times. Implements MCP tool that calls PagerDuty's /schedules and /oncalls endpoints to map schedule IDs to assigned users, enabling Claude to answer 'who is on-call' questions with temporal context.

Solves for

Determine who is currently on-call for a specific service or scheduleFind the next on-call engineer in the rotation for escalation planningIdentify on-call coverage gaps or overlaps in schedulesGet handoff times to understand when on-call responsibilities change

Best for

Incident commanders using Claude to route incidents to correct on-call engineer

Teams automating on-call notifications and handoff workflows

SRE platforms building intelligent escalation routing

Requires

PagerDuty API token with read:schedules scope

Schedule IDs configured in PagerDuty (obtainable via separate API call)

MCP client with tool-calling support

Limitations

Schedule queries return static rotation data — does not reflect real-time overrides or manual reassignments made in the last few seconds

Timezone handling is API-dependent — requires schedule to be configured with timezone in PagerDuty; no automatic timezone conversion

No predictive capability — cannot forecast on-call assignments beyond the next scheduled rotation

What makes it unique

Exposes PagerDuty's on-call schedule data as an MCP tool with temporal filtering, allowing Claude to reason about on-call coverage and make routing decisions without manual schedule lookups. Combines /schedules and /oncalls endpoints to provide both static schedule structure and current assignments.

vs alternatives

Faster than checking PagerDuty dashboard for on-call info because Claude can query and summarize in one turn; more reliable than Slack status messages because it queries authoritative PagerDuty source.

escalation-policy-trigger-with-notification-routing

Medium confidence

Triggers escalation policies in PagerDuty to notify on-call engineers according to configured escalation rules. Implements MCP tool that calls PagerDuty's escalation policy endpoints to initiate notification chains, respecting escalation levels, delays, and notification preferences configured in PagerDuty.

Solves for

Escalate an incident to the next level in the escalation chain when initial responder is unavailableTrigger notifications to specific escalation policies for urgent issuesProgrammatically initiate escalation workflows as part of automated incident responseNotify backup on-call engineers when primary responder doesn't acknowledge within SLA

Best for

Automated incident response systems that need to escalate based on Claude reasoning

Teams building custom escalation logic on top of PagerDuty

SRE platforms integrating incident escalation with other observability tools

Requires

PagerDuty API token with write:escalation_policies scope

Valid escalation policy ID from PagerDuty

MCP client with tool-calling support

Limitations

Escalation policy execution follows PagerDuty's configured delays — cannot force immediate escalation to all levels

No dry-run mode — triggering an escalation policy sends notifications immediately, cannot preview impact

Escalation state is managed by PagerDuty — this tool cannot query or modify escalation history

What makes it unique

Wraps PagerDuty's escalation policy API as an MCP tool, enabling Claude to trigger escalations as part of incident response workflows. Respects PagerDuty's configured escalation delays and notification preferences rather than sending raw notifications.

vs alternatives

More controlled than direct notification systems because escalations follow PagerDuty's configured policies; safer than manual escalation because Claude can reason about escalation necessity before triggering.

incident-detail-retrieval-with-timeline-context

Medium confidence

Retrieves detailed incident information including full timeline of status changes, notes, assigned users, and escalation history. Implements MCP tool that calls PagerDuty's /incidents/{id} endpoint with related data expansion, providing Claude with complete incident context for analysis and decision-making.

Solves for

Get full incident timeline to understand how an issue evolved and what actions were takenReview all notes and comments added by responders to understand investigation progressIdentify who has been assigned to an incident and their actionsAnalyze escalation history to understand response effectiveness

Best for

Post-incident review workflows where Claude summarizes incident progression

On-call engineers needing full context before taking action on an incident

Incident commanders building situational awareness during active incidents

Requires

PagerDuty API token with read:incidents scope

Valid incident ID from PagerDuty

MCP client with tool-calling support

Limitations

Timeline data is immutable after incident resolution — cannot retrieve deleted notes or reverted status changes

Large incidents with hundreds of timeline entries may return paginated results requiring multiple API calls

Related data expansion (notes, assignments, escalations) increases response size and latency

What makes it unique

Exposes PagerDuty's incident detail API with timeline expansion as an MCP tool, allowing Claude to retrieve and analyze complete incident history in a single call. Includes related data (notes, assignments, escalations) to provide full context without multiple sequential queries.

vs alternatives

More comprehensive than incident-list because it includes full timeline and notes; faster than manual dashboard review because Claude can extract and summarize key events programmatically.

service-and-team-metadata-query

Medium confidence

Queries PagerDuty services and teams to retrieve metadata including service descriptions, escalation policies, and team memberships. Implements MCP tool that calls PagerDuty's /services and /teams endpoints, enabling Claude to understand organizational structure and service ownership for intelligent incident routing.

Solves for

Identify which team owns a specific service for incident assignmentGet escalation policy details for a service to understand response chainList all services to help users find relevant services for incident queriesUnderstand team composition and responsibilities for incident routing

Best for

Multi-team organizations using Claude for intelligent incident routing

Incident commanders needing to understand service ownership and escalation chains

Teams building incident response automation with service-aware logic

Requires

PagerDuty API token with read:services and read:teams scope

MCP client with tool-calling support

Limitations

Service metadata is static — does not reflect real-time service health or current load

Team membership changes require PagerDuty to be updated separately — this tool reflects current state only

No service dependency mapping — cannot query which services depend on each other

What makes it unique

Exposes PagerDuty's service and team metadata as MCP tools, enabling Claude to understand organizational structure and make service-aware routing decisions. Combines service and team endpoints to provide both service details and ownership information.

vs alternatives

Enables intelligent incident routing because Claude can query service ownership and escalation policies; more reliable than hardcoded service mappings because it queries authoritative PagerDuty source.

mcp-tool-schema-based-function-calling

Medium confidence

Implements MCP (Model Context Protocol) tool definitions with JSON schema for all PagerDuty operations, enabling Claude and other MCP-compatible LLMs to discover and invoke PagerDuty capabilities through standardized tool-calling interface. Uses MCP's tool registry pattern to expose PagerDuty API operations as callable functions with schema validation.

Solves for

Enable Claude to discover available PagerDuty operations without documentation lookupValidate tool parameters against schema before sending to PagerDuty APISupport multiple MCP-compatible LLMs (Claude, other providers) with same tool definitionsProvide structured error handling and response parsing for PagerDuty API responses

Best for

Developers building Claude applications that need PagerDuty integration

Teams standardizing on MCP for multi-tool LLM applications

Organizations wanting to expose PagerDuty to multiple LLM providers via MCP

Requires

MCP client implementation (Claude 3.5+, or other MCP-compatible LLM)

MCP server running (this artifact)

PagerDuty API token

Limitations

MCP tool discovery requires client to support MCP protocol — not compatible with basic API clients

Schema validation adds ~50-100ms overhead per tool call for parameter checking

Tool definitions are static — cannot dynamically generate schemas based on PagerDuty API changes

What makes it unique

Implements MCP tool protocol for PagerDuty, providing schema-based function calling that enables Claude to discover and invoke PagerDuty operations with validated parameters. Uses MCP's standardized tool definition format for cross-LLM compatibility.

vs alternatives

More standardized than custom API wrappers because it uses MCP protocol; enables multi-LLM support because MCP tools work with any compatible client, not just Claude.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with PagerDuty MCP Server, ranked by overlap. Discovered automatically through the match graph.

Product19

Pagerly

Your Operations Co-pilot on Slack/Teams. It assists and prompts oncall with relevant information to debug issues.

oncall rotation and escalation path managementintelligent oncall prompt and suggestion engineincident timeline and communication thread consolidation

3 shared capabilities

Product29

Pagerly

Your Operations Co-pilot on Slack/Teams. It assists and prompts oncall with relevant information to debug...

on-call-prompt-assistanceincident-history-retrievalincident-context-injection

3 shared capabilities

MCP Server20

ilert

** - Interact with [ilert](https://ilert.com) through natural language.

incident-query-and-retrieval-via-natural-languageincident-acknowledgment-and-escalation-via-conversation

2 shared capabilities

Agent28

Cleric

Autonomously triages and roots cause alerts in complex...

incident-context-enrichmentincident-severity-assessment

2 shared capabilities

Product27

Rely.io

Empower engineering excellence with AI-driven service reliability and developer...

on-call schedule management and optimization

1 shared capability

MCP Server24

Grafana

** - Search dashboards, investigate incidents and query datasources in your Grafana instance

incident and oncall integration for incident management

1 shared capability

Best For

✓DevOps teams using Claude for incident triage and status reporting
✓On-call engineers needing quick incident overview during handoffs
✓SRE teams building Claude-powered incident dashboards
✓Automated incident response workflows triggered by Claude agents
✓On-call engineers using Claude as a command interface for PagerDuty
✓Teams building incident auto-remediation systems with human-in-the-loop approval
✓Incident commanders using Claude to route incidents to correct on-call engineer
✓Teams automating on-call notifications and handoff workflows

Known Limitations

⚠Pagination limited to API response size — large incident volumes (>1000 active) may require multiple sequential calls
⚠Real-time filtering happens client-side after API fetch, not server-side, adding latency for large datasets
⚠No built-in caching — repeated queries within seconds hit the API each time, subject to rate limits
⚠Acknowledgment is idempotent but provides no feedback if incident already acknowledged — silent success
⚠Notes are appended to incident timeline but not searchable via this tool — requires separate incident detail query
⚠No rollback capability — acknowledged incidents cannot be un-acknowledged via this tool

Requirements

PagerDuty API token with read:incidents scopeMCP client compatible with tool-calling (Claude 3.5+, other MCP-aware LLMs)Network access to api.pagerduty.comPagerDuty API token with write:incidents scopeValid incident ID from PagerDuty (obtainable via incident-list capability)MCP client with tool-calling supportPagerDuty API token with read:schedules scopeSchedule IDs configured in PagerDuty (obtainable via separate API call)

Input / Output

Accepts: query parameters (status, urgency, service_ids, date_range), incident_id (string), optional note (string), schedule_id (string), optional since_date (ISO 8601), optional until_date (ISO 8601), escalation_policy_id (string), incident_id (string), optional reason (string), incident_id (string), optional include_related (boolean), optional service_id (string), optional team_id (string), optional query (string for search), MCP tool call requests with JSON parameters matching schema

Produces: JSON array of incident objects with id, title, status, urgency, service, created_at, last_status_change_at, JSON object confirming incident status change, updated_at timestamp, acknowledgement_time, JSON array of on-call assignments with user_id, user_name, start_time, end_time, escalation_policy_id, JSON object confirming escalation trigger, notification_sent_at, escalation_level, notified_users array, JSON object with incident metadata, timeline array (status_changes, notes, assignments), escalation_policy, service, assigned_via_escalation_policy, JSON array of service/team objects with id, name, description, escalation_policy_id, team_id, status, MCP tool result with JSON response from PagerDuty API, or error with details

UnfragileRank

Adoption70%(30% weight)

Quality23%(25% weight)

Ecosystem52%(25% weight)

Match Graph10%(15% weight)

Freshness100%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

7 capabilities

Visit PagerDuty MCP Server→

About

Community MCP server for PagerDuty incident management. Provides tools for listing and managing incidents, acknowledging alerts, querying on-call schedules, and triggering escalation policies.

Alternatives to PagerDuty MCP Server

YouTube MCP Server46MCP Server

Extract and analyze YouTube video transcripts via MCP.

Compare →

Vercel MCP Server46MCP Server

Manage Vercel deployments, projects, and domains via MCP.

Compare →

Todoist MCP Server46MCP Server

Create and manage Todoist tasks and projects via MCP.

Compare →

Telegram MCP Server46MCP Server

Send messages and manage Telegram chats and bots via MCP.

Compare →

Are you the builder of PagerDuty MCP Server?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

seed developer essentials

Looking for something else?

Search →

Capabilities7 decomposed

incident-list-and-filter-with-status-awareness

Medium confidence

Solves for

Best for

DevOps teams using Claude for incident triage and status reporting

On-call engineers needing quick incident overview during handoffs

SRE teams building Claude-powered incident dashboards

Requires

PagerDuty API token with read:incidents scope

MCP client compatible with tool-calling (Claude 3.5+, other MCP-aware LLMs)

Network access to api.pagerduty.com

Limitations

Pagination limited to API response size — large incident volumes (>1000 active) may require multiple sequential calls

Real-time filtering happens client-side after API fetch, not server-side, adding latency for large datasets

No built-in caching — repeated queries within seconds hit the API each time, subject to rate limits

What makes it unique

vs alternatives

incident-acknowledgment-with-context-preservation

Medium confidence

Solves for

Best for

Automated incident response workflows triggered by Claude agents

On-call engineers using Claude as a command interface for PagerDuty

Teams building incident auto-remediation systems with human-in-the-loop approval

Requires

PagerDuty API token with write:incidents scope

Valid incident ID from PagerDuty (obtainable via incident-list capability)

MCP client with tool-calling support

Limitations

Acknowledgment is idempotent but provides no feedback if incident already acknowledged — silent success

Notes are appended to incident timeline but not searchable via this tool — requires separate incident detail query

No rollback capability — acknowledged incidents cannot be un-acknowledged via this tool

What makes it unique

vs alternatives

on-call-schedule-query-with-rotation-awareness

Medium confidence

Solves for

Best for

Incident commanders using Claude to route incidents to correct on-call engineer

Teams automating on-call notifications and handoff workflows

SRE platforms building intelligent escalation routing

Requires

PagerDuty API token with read:schedules scope

Schedule IDs configured in PagerDuty (obtainable via separate API call)

MCP client with tool-calling support

Limitations

Schedule queries return static rotation data — does not reflect real-time overrides or manual reassignments made in the last few seconds

Timezone handling is API-dependent — requires schedule to be configured with timezone in PagerDuty; no automatic timezone conversion

No predictive capability — cannot forecast on-call assignments beyond the next scheduled rotation

What makes it unique

vs alternatives

escalation-policy-trigger-with-notification-routing

Medium confidence

Solves for

Best for

Automated incident response systems that need to escalate based on Claude reasoning

Teams building custom escalation logic on top of PagerDuty

SRE platforms integrating incident escalation with other observability tools

Requires

PagerDuty API token with write:escalation_policies scope

Valid escalation policy ID from PagerDuty

MCP client with tool-calling support

Limitations

Escalation policy execution follows PagerDuty's configured delays — cannot force immediate escalation to all levels

No dry-run mode — triggering an escalation policy sends notifications immediately, cannot preview impact

Escalation state is managed by PagerDuty — this tool cannot query or modify escalation history

What makes it unique

vs alternatives

incident-detail-retrieval-with-timeline-context

Medium confidence

Solves for

Best for

Post-incident review workflows where Claude summarizes incident progression

On-call engineers needing full context before taking action on an incident

Incident commanders building situational awareness during active incidents

Requires

PagerDuty API token with read:incidents scope

Valid incident ID from PagerDuty

MCP client with tool-calling support

Limitations

Timeline data is immutable after incident resolution — cannot retrieve deleted notes or reverted status changes

Large incidents with hundreds of timeline entries may return paginated results requiring multiple API calls

Related data expansion (notes, assignments, escalations) increases response size and latency

What makes it unique

vs alternatives

More comprehensive than incident-list because it includes full timeline and notes; faster than manual dashboard review because Claude can extract and summarize key events programmatically.

service-and-team-metadata-query

Medium confidence

Solves for

Best for

Multi-team organizations using Claude for intelligent incident routing

Incident commanders needing to understand service ownership and escalation chains

Teams building incident response automation with service-aware logic

Requires

PagerDuty API token with read:services and read:teams scope

MCP client with tool-calling support

Limitations

Service metadata is static — does not reflect real-time service health or current load

Team membership changes require PagerDuty to be updated separately — this tool reflects current state only

No service dependency mapping — cannot query which services depend on each other

What makes it unique

vs alternatives

mcp-tool-schema-based-function-calling

Medium confidence

Solves for

Best for

Developers building Claude applications that need PagerDuty integration

Teams standardizing on MCP for multi-tool LLM applications

Organizations wanting to expose PagerDuty to multiple LLM providers via MCP

Requires

MCP client implementation (Claude 3.5+, or other MCP-compatible LLM)

MCP server running (this artifact)

PagerDuty API token

Limitations

MCP tool discovery requires client to support MCP protocol — not compatible with basic API clients

Schema validation adds ~50-100ms overhead per tool call for parameter checking

Tool definitions are static — cannot dynamically generate schemas based on PagerDuty API changes

What makes it unique

vs alternatives

More standardized than custom API wrappers because it uses MCP protocol; enables multi-LLM support because MCP tools work with any compatible client, not just Claude.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to PagerDuty MCP Server

YouTube MCP Server46MCP Server

Extract and analyze YouTube video transcripts via MCP.

Compare →

Vercel MCP Server46MCP Server

Manage Vercel deployments, projects, and domains via MCP.

Compare →

Todoist MCP Server46MCP Server

Create and manage Todoist tasks and projects via MCP.

Compare →

Telegram MCP Server46MCP Server

Send messages and manage Telegram chats and bots via MCP.

Compare →

PagerDuty MCP Server

Capabilities7 decomposed

incident-list-and-filter-with-status-awareness

incident-acknowledgment-with-context-preservation

on-call-schedule-query-with-rotation-awareness

escalation-policy-trigger-with-notification-routing

incident-detail-retrieval-with-timeline-context

service-and-team-metadata-query

mcp-tool-schema-based-function-calling

Related Artifactssharing capabilities

Pagerly

Pagerly

ilert

Cleric

Rely.io

Grafana

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to PagerDuty MCP Server

Are you the builder of PagerDuty MCP Server?

Get the weekly brief

Data Sources

PagerDuty MCP Server

Capabilities7 decomposed

incident-list-and-filter-with-status-awareness

incident-acknowledgment-with-context-preservation

on-call-schedule-query-with-rotation-awareness

escalation-policy-trigger-with-notification-routing

incident-detail-retrieval-with-timeline-context

service-and-team-metadata-query

mcp-tool-schema-based-function-calling

Related Artifactssharing capabilities

Pagerly

Pagerly

ilert

Cleric

Rely.io

Grafana

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to PagerDuty MCP Server

Are you the builder of PagerDuty MCP Server?

Get the weekly brief

Data Sources