PagerDuty MCP Server

PagerDuty is an incident management platform that helps teams respond to and resolve critical incidents with on-call scheduling, alerting, and escalation management.

Tools

Last Updated

Apr 7, 2026

What is the PagerDuty MCP Server?

The PagerDuty MCP server gives AI agents structured, permission-aware access to PagerDuty through the Model Context Protocol. With 23 pre-built actions, agents can read, create, and update PagerDuty data on behalf of authorized users.

Willow ships the PagerDuty MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how PagerDuty is being used by every AI agent in your stack.

Tools

List Incidents

Query and list incidents with flexible filtering options. Filter by status (triggered, acknowledged, resolved), urgency (high, low), date ranges, service, user, or team. Returns paginated results with incident details including title, status, urgency, service, assignees, and timestamps. Use this to monitor active incidents, audit historical incidents, or find specific incidents matching criteria.

Get Incident

Retrieve detailed information about a specific incident by its ID. Returns comprehensive incident data including title, description, status, urgency, priority, service, escalation policy, assignments, acknowledgments, last status change time, and full incident timeline. Use this when you need complete details about a known incident for investigation or reporting.

Create Incident

Manually create a new incident in PagerDuty. Requires a title and service ID at minimum. Optionally specify urgency (high/low), priority, escalation policy, body/details, and assignments. The incident will be created and routed according to the service's escalation policy unless overridden. Use this to manually report incidents, create test incidents, or integrate external monitoring tools.

Update Incident

Update properties of an existing incident. You can modify the title, urgency, priority, status (acknowledged/resolved), escalation policy, or assignments. To acknowledge or resolve incidents in bulk, use the dedicated Acknowledge Incident or Resolve Incident tools instead. Use this for general incident updates like changing priority, reassigning, or updating details.

Acknowledge Incident

Acknowledge one or more incidents to indicate that work has begun on resolving them. Acknowledging stops the escalation process and prevents further notifications. Supports bulk operations - you can acknowledge multiple incidents in a single request. The user performing the acknowledgment must be specified via from_email for audit purposes. Use this when responding to incidents to signal active work.

Resolve Incident

Resolve one or more incidents to mark them as fixed and close them. Once resolved, incidents stop generating notifications and are moved to the resolved state. Supports bulk operations - you can resolve multiple incidents in a single request. The user performing the resolution must be specified via from_email for audit purposes. Use this when incidents are fully addressed and no longer require attention.

List Incident Alerts

Retrieve all alerts associated with a specific incident. An incident can be triggered by one or multiple alerts from monitoring systems. This returns the individual alert details including severity, summary, source, custom details, and timestamps. Use this to investigate the root cause of an incident by examining all triggering alerts and their context.

List Services

Browse and search all services in your PagerDuty account with pagination. Services represent the applications, systems, or components you monitor. Filter by team to see services owned by specific teams. Optionally include escalation policy and integration details in the response. Use this to discover available services, audit service configuration, or find specific services for incident creation.

Get Service

Retrieve detailed information about a specific service by its ID. Returns comprehensive service details including name, description, status, escalation policy, integrations, incident urgency rules, alert grouping settings, and associated teams. Use this to inspect service configuration, understand routing rules, or get integration details for a known service.

Update Service

Modify configuration of an existing service. You can update the service name, description, escalation policy, acknowledgement timeout, auto-resolve timeout, and alert grouping settings. Changes to escalation policy affect how future incidents are routed. Use this to maintain service configuration, update escalation rules, or adjust incident handling behavior.

1 2 3

1–10 of 23 tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your PagerDuty MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-pagerduty": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/pagerduty"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-pagerduty": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/pagerduty"
    }
  }
}

Claude Code

CLI

claude mcp add willow-pagerduty --transport http https://<org>.mcp-s.com/mcp/mcp/pagerduty

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/pagerduty",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for PagerDuty

Willow adds the layer PagerDuty and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

PagerDuty MCP Server FAQ

What is the PagerDuty MCP server?

The PagerDuty MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write PagerDuty data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's PagerDuty MCP server different from the official one?

The official PagerDuty MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the PagerDuty MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the PagerDuty MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in PagerDuty, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which PagerDuty actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow PagerDuty MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved PagerDuty MCP locally, you'll see it.

What does the PagerDuty MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the PagerDuty MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.