Skip to main content
Book a demo

PagerDuty

PagerDuty-hosted MCP server for incident management, alerting, and on-call scheduling operations

Book a demo View documentation

Ways to connect

2 ways to connect PagerDuty

Every one of them gets the same identity, policy, scanning, and audit. Pick the delivery and sign-in that fit your workspace.

Official PagerDuty server, vendor-hosted

Delivery
Hosted by PagerDuty
Sign-in
OAuth
Tools
18
Documentation

Open-source PagerDuty server, Runlayer-hosted

Delivery
PagerDuty's server, hosted by Runlayer
Sign-in
Credentials required
Documentation

Tools

18 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

18 tools found.

  • Browse activity

    Tool name: browse_activity

    Read PagerDuty account activity (log entries).

  • Browse alert grouping

    Tool name: browse_alert_grouping

    Read PagerDuty alert grouping settings.

  • Browse change events

    Tool name: browse_change_events

    Read PagerDuty change event data.

  • Browse escalation policies

    Tool name: browse_escalation_policies

    Read PagerDuty escalation policy data.

  • Browse event orchestrations

    Tool name: browse_event_orchestrations

    Read PagerDuty event orchestration data.

  • Browse incidents

    Tool name: browse_incidents

    Read PagerDuty incident data.

  • Browse schedules

    Tool name: browse_schedules

    Read PagerDuty schedules and on-call data.

  • Browse services

    Tool name: browse_services

    Read PagerDuty service data.

  • Browse status pages

    Tool name: browse_status_pages

    Read PagerDuty status page data.

  • Browse teams

    Tool name: browse_teams

    Read PagerDuty team data.

  • Browse users

    Tool name: browse_users

    Read PagerDuty user data.

  • Manage alert grouping

    Tool name: manage_alert_grouping

    Create, update, or delete PagerDuty alert grouping settings.

  • Manage event orchestrations

    Tool name: manage_event_orchestrations

    Modify PagerDuty event orchestration routing rules.

  • Manage incidents

    Tool name: manage_incidents

    Modify PagerDuty incidents.

  • Manage schedules

    Tool name: manage_schedules

    Create, update or delete PagerDuty schedules and their shifts.

  • Manage services

    Tool name: manage_services

    Create or update PagerDuty services.

  • Manage status pages

    Tool name: manage_status_pages

    Create posts and post updates on PagerDuty status pages.

  • Manage teams

    Tool name: manage_teams

    Create, update, or delete PagerDuty teams and membership.

Compatibility

Connect PagerDuty to the clients your teams already use

27 AI clients can connect to PagerDuty through Runlayer. Pick one for its setup steps and controls.

CursorVS CodeClaudeClaude CodeClaude CoworkChatGPTWindsurfGooseCodexHermesGumloopRaycastWarpGitHub CopilotGitHub Copilot CLIMicrosoft 365 CopilotGemini CLIZedCline CLIAntigravityOpenCodeCrushGleanLovablePerplexityECAOh My Pi

Why Runlayer

Why connect PagerDuty through Runlayer?

One approved path

Approve PagerDuty once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions