Skip to main content
Back to the MCP Gateway catalog

MCP Gateway · Catalog

PagerDuty icon

PagerDuty MCP server

Official

PagerDuty MCP is the official Model Context Protocol server for PagerDuty, with API key authentication and tools that let agents list and manage incidents, alerts, services, teams, schedules, escalation policies, and status pages. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT get one governed URL for it, with SSO, RBAC, and a full audit trail.

Category
Infrastructure
Tools
64
Authentication
API key
Connects through
Speakeasy MCP Gateway

Behind the MCP Gateway

Run PagerDuty MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every PagerDuty call inspected and logged.

Deploy on MCP Gateway

Connect from your AI client

Use PagerDuty in the clients your teams already use

Setup steps and the controls Speakeasy applies, for each client.

Tools

64 tools

Each tool below can be allowed or denied per team and role at the MCP Gateway, and every call is inspected and logged.

list_alert_grouping_settings

List all alert grouping settings with optional filtering.

get_alert_grouping_setting

Get details for a specific alert grouping setting.

list_alerts_from_incident

List alerts for a specific incident.

get_alert_from_incident

Get a specific alert from an incident.

list_change_events

List all change events with optional filtering.

get_change_event

Get details about a specific change event.

list_service_change_events

List all change events for a specific service.

list_incident_change_events

List change events related to a specific incident.

list_incidents

List incidents with optional filtering.

get_incident

Get a specific incident.

get_outlier_incident

Get Outlier Incident information for a given Incident on its Service.

get_past_incidents

Get Past Incidents related to a specific incident ID.

list_incident_notes

List all notes for a specific incident.

list_incident_workflows

List incident workflows with optional filtering.

get_incident_workflow

Get a specific incident workflow.

list_services

List all services.

get_service

Get details for a specific service.

list_teams

List teams based on the provided query model.

get_team

Get a specific team.

list_team_members

List members of a team.

get_user_data

Get the current user's data.

list_users

List users, optionally filtering by name (query) and team IDs.

list_schedules

List schedules with optional filtering.

get_schedule

Get a specific schedule by ID.

list_schedule_users

List users in a schedule.

list_oncalls

List on-call schedules with optional filtering.

list_log_entries

List all log entries across the account.

get_log_entry

Get a specific log entry by ID.

list_escalation_policies

List escalation policies with optional filtering.

get_escalation_policy

Get a specific escalation policy.

list_event_orchestrations

List event orchestrations with optional filtering.

get_event_orchestration

Get details for a specific event orchestration.

get_event_orchestration_router

Get the router configuration for a specific event orchestration.

get_event_orchestration_service

Get the Service Orchestration configuration for a specific service.

get_event_orchestration_global

Get the Global Orchestration configuration for a specific event orchestration.

list_status_pages

List Status Pages with optional filtering.

list_status_page_severities

List Severities for a Status Page by Status Page ID.

list_status_page_impacts

List Impacts for a Status Page by Status Page ID.

list_status_page_statuses

List Statuses for a Status Page by Status Page ID.

get_status_page_post

Get a Post for a Status Page by Status Page ID and Post ID.

list_status_page_post_updates

List Post Updates for a Status Page by Status Page ID and Post ID.

create_alert_grouping_setting

Create a new alert grouping setting.

update_alert_grouping_setting

Update an existing alert grouping setting.

delete_alert_grouping_setting

Delete an alert grouping setting.

create_incident

Create an incident.

manage_incidents

Manage one or more incidents by changing its status, urgency, assignment, or escalation level.

add_responders

Add responders to an incident.

add_note_to_incident

Add a note to an incident.

start_incident_workflow

Start an incident workflow instance.

create_service

Create a new service.

update_service

Update an existing service.

create_team

Create a team.

update_team

Update a team.

delete_team

Delete a team.

add_team_member

Add a user to a team.

remove_team_member

Remove a user from a team.

create_schedule

Create a new on-call schedule.

create_schedule_override

Create an override for a schedule.

update_schedule

Update an existing schedule.

update_event_orchestration_router

Update the router configuration for a specific event orchestration.

append_event_orchestration_router_rule

Append a new routing rule to the end of an event orchestration's router rules.

create_status_page_post

Create a Post for a Status Page by Status Page ID.

create_status_page_post_update

Create a Post Update for a Post by Post ID.

Questions

Frequently asked questions

What is a PagerDuty MCP server?
A PagerDuty MCP server exposes PagerDuty to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call tools such as list_alert_grouping_settings or get_alert_grouping_setting to work with PagerDuty. The server in this catalog is the official PagerDuty MCP server, which authenticates with an API key.
What can you do with PagerDuty MCP?
Agents can list and manage incidents, alerts, services, teams, schedules, escalation policies, and status pages. The catalog lists 64 tools for this server, including list_alert_grouping_settings, get_alert_grouping_setting, and list_alerts_from_incident. The full list with descriptions is on this page.
Why put PagerDuty MCP behind an MCP gateway?
Connecting the PagerDuty MCP server directly to each client means a separate credential per developer, no inventory of who can reach PagerDuty through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the PagerDuty server, so sign-in runs through your identity provider, role-based access decides which teams can call which PagerDuty tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to PagerDuty and to every other server in your catalog.
How do you connect PagerDuty MCP through a gateway?
Add the PagerDuty server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which PagerDuty tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial PagerDuty MCP?
Community-built PagerDuty MCP servers wrap the same PagerDuty surface but are not vendor-maintained. This catalog lists the official PagerDuty MCP server. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access controls, and an audit trail of every call, whichever credential the server itself uses.

AI everywhere.

Control here.