pagerduty-mcp
OfficialThis server provides MCP tools to read (and optionally write) PagerDuty data, covering incidents, alerts, services, schedules, on-call, and more.
Incidents: list, get, notes, change events, outlier/past/related incidents
Alerts: list/get alerts from incidents, alert grouping settings
Services: list/get services, service change events, technical service dependencies
Schedules: list/get schedules (both classic v2 and next-gen v3), schedule users, v3 rotations, rotation events, custom shifts, overrides
On-Call: list on-calls with filters
Teams & Users: list/get teams, team members, current user, users
Escalation Policies: list/get
Event Orchestrations: list/get, router, service, global configurations
Status Pages: list pages, severities, impacts, statuses, posts, post updates
Analytics: responder metrics, incident metrics by service/team/all, responder load
Log Entries: list/get
Webhooks: list/get subscriptions
Extension Schemas: list/get
Business Services: list, dependencies
Priorities: list all
Incident Workflows: list/get
Change Events: list/get, service/incident related
Provides tools to manage incidents, services, schedules, event orchestrations, and more directly from your MCP-enabled client, with embedded React UIs for incident management, on-call management, and service dependency visualization.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@pagerduty-mcp Show me the current incidents"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PagerDuty's official MCP Server
This repository is deprecated and now read-only. Development has moved to PagerDuty's hosted Remote MCP Server — see the docs there for setup instructions.
PagerDuty's local MCP (Model Context Protocol) server which provides tools to interact with your PagerDuty account, allowing you to manage incidents, services, schedules, event orchestrations, and more directly from your MCP-enabled client.
Quick start
You need uv and a PagerDuty User API Token — see
Prerequisites and Authentication.
PAGERDUTY_USER_API_KEY="your-token" uvx pagerduty-mcpBy default only read-only tools are exposed. Add --enable-write-tools to allow tools that modify
your PagerDuty account. Then point your MCP client at the server —
Cursor, VS Code,
Claude Desktop, or Docker.
Prefer no local install? PagerDuty hosts a Remote MCP Server with OAuth support.
Related MCP server: runframe-mcp-server
Contents
The full documentation lives in docs/ and is readable directly on GitHub.
Getting Started
Introduction — what the MCP server is and what it can do
Installation
Remote Server
Remote MCP Server Setup — PagerDuty-hosted, no local install. Maintained on the PagerDuty Knowledge Base.
Configuration
Tools Reference
Tools Overview — every tool, read/write type, and description
Use Cases
Experimental
Experimental Overview — MCP Apps and the
experimentalbranch
Community
Contributing
Support
PagerDuty's MCP server is an open-source project, and as such, we offer only community-based support. If assistance is required, please open an issue in GitHub or PagerDuty's community forum.
Contributing
If you are interested in contributing to this project, please refer to our Contributing Guidelines and the development setup guide.
Available Tools
63 toolsget_alert_from_incidentARead-onlyIdempotent
Get a specific alert from an incident.
Both IDs must be known, non-empty PagerDuty IDs (e.g. "PALERT123").
If the alert ID is not known, use list_alerts_from_incident to discover
the incident's alerts instead of calling this tool with an empty or
placeholder alert_id.
Args:
incident_id: The ID of the incident
alert_id: The ID of the alert
Returns:
Alert details
Inputs: alert_id (required), incident_id (required). Returns: Alert model representing a PagerDuty alert.
get_alert_grouping_settingBRead-onlyIdempotent
Get details for a specific alert grouping setting.
Args:
setting_id: The ID of the alert grouping setting to retrieve
Returns:
Alert grouping setting details
Inputs: setting_id (required). Returns: Defines how alerts will be automatically grouped into incidents based on the co…
get_business_service_dependenciesARead-onlyIdempotent
Get dependencies for a business service.
Args:
business_service_id: The ID of the business service
Returns:
JSON string with relationships list
Inputs: business_service_id (required). Returns: result
get_change_eventARead-onlyIdempotent
Get details about a specific change event.
Args:
change_event_id: The ID of the change event to retrieve
Returns:
ChangeEvent details
Inputs: change_event_id (required). Returns: Represents a PagerDuty Change Event. Change Events represent changes to systems…
get_escalation_policyCRead-onlyIdempotent
Get a specific escalation policy.
Args:
policy_id: The ID of the escalation policy to retrieve
Returns:
Escalation policy details
Inputs: policy_id (required). Returns: id, name, teams, summary, +9 more
get_event_orchestrationBRead-onlyIdempotent
Get details for a specific event orchestration.
Args:
orchestration_id: The ID of the event orchestration to retrieve
Returns:
The event orchestration details
Inputs: orchestration_id (required). Returns: id, name, self, team, +8 more
get_event_orchestration_globalARead-onlyIdempotent
Get the Global Orchestration configuration for a specific event orchestration.
Args:
orchestration_id: The ID of the event orchestration to retrieve global configuration for
Returns:
The global orchestration configuration
Inputs: orchestration_id (required). Returns: Global Orchestration response model.
get_event_orchestration_routerARead-onlyIdempotent
Get the router configuration for a specific event orchestration.
Args:
orchestration_id: The ID of the event orchestration to retrieve router for
Returns:
The event orchestration router configuration
Inputs: orchestration_id (required). Returns: orchestration_path
get_event_orchestration_serviceARead-onlyIdempotent
Get the Service Orchestration configuration for a specific service.
Args:
service_id: The ID of the service to retrieve the orchestration configuration for
Returns:
The service orchestration configuration
Inputs: service_id (required). Returns: Service Orchestration response model.
get_extension_schemaARead-onlyIdempotent
Get a specific extension schema by ID.
Args:
schema_id: The ID of the extension schema to retrieve
Returns:
Extension schema details
Inputs: schema_id (required). Returns: A PagerDuty extension schema (extension vendor definition).
get_incidentBRead-onlyIdempotent
Get a specific incident.
Args:
incident_id: The ID or number of the incident to retrieve.
query_model: Optional query parameters for additional information to include
Returns:
Incident details
Inputs: incident_id (required), query_model. Returns: id, title, status, service, +7 more
get_incident_metrics_allARead-onlyIdempotent
Get full-period aggregated incident metrics from PagerDuty Analytics.
Returns rollup metrics for the entire requested period including percentile
distributions (P50, P75, P90, P95) for ack and resolve times. These percentile
fields are ONLY available from this endpoint — not from the per-team or per-service
grouped endpoints.
Args:
created_at_start: ISO8601 DateTime. Incidents created before this are omitted.
created_at_end: ISO8601 DateTime. Incidents created on/after this are omitted.
team_ids: Only incidents related to these teams will be included.
service_ids: Only incidents related to these services will be included.
urgency: Filter by urgency: 'high' or 'low'.
time_zone: The time zone for results (e.g. 'America/New_York').
order: Sort order: 'asc' or 'desc'.
order_by: Field to sort results by.
Returns:
JSON string of AnalyticsAggregatedMetrics object.
Inputs: created_at_end (required), created_at_start (required), order, urgency, +4 more. Returns: result
get_incident_metrics_by_serviceARead-onlyIdempotent
Get aggregated incident metrics per service from PagerDuty Analytics.
Returns service-level MTTA, mean MTTR, escalation counts, incident
volume, and uptime percentage. Use this instead of list_incidents when you need
service health metrics — data is pre-aggregated by PagerDuty's analytics engine.
Args:
created_at_start: ISO8601 DateTime. Incidents created before this are omitted.
created_at_end: ISO8601 DateTime. Incidents created on/after this are omitted.
team_ids: Only incidents related to these teams will be included.
service_ids: Only incidents related to these services will be included.
urgency: Filter by urgency: 'high' or 'low'.
time_zone: The time zone for results (e.g. 'America/New_York').
order: Sort order: 'asc' or 'desc'.
order_by: Field to sort results by.
Returns:
JSON string of ListResponseModel containing AnalyticsServiceMetrics objects.
Inputs: created_at_end (required), created_at_start (required), order, urgency, +4 more. Returns: result
get_incident_metrics_by_teamARead-onlyIdempotent
Get aggregated incident metrics per team from PagerDuty Analytics.
Returns team-level MTTA, mean MTTR, escalation counts, incident
volume, and uptime percentage. Use for team performance comparisons and dashboards.
Args:
created_at_start: ISO8601 DateTime. Incidents created before this are omitted.
created_at_end: ISO8601 DateTime. Incidents created on/after this are omitted.
team_ids: Only incidents related to these teams will be included.
service_ids: Only incidents related to these services will be included.
urgency: Filter by urgency: 'high' or 'low'.
time_zone: The time zone for results (e.g. 'America/New_York').
order: Sort order: 'asc' or 'desc'.
order_by: Field to sort results by.
aggregate_unit: Time unit to aggregate metrics by: 'day', 'week', or 'month'.
If omitted, returns a single all-period row.
Returns:
JSON string of ListResponseModel containing AnalyticsTeamMetrics objects.
Inputs: created_at_end (required), created_at_start (required), order, urgency, +5 more. Returns: result
get_incident_workflowCRead-onlyIdempotent
Get a specific incident workflow.
Args:
workflow_id: The ID of the incident workflow to retrieve
Returns:
IncidentWorkflow details
Inputs: workflow_id (required). Returns: An incident workflow configuration.
get_log_entryBRead-onlyIdempotent
Get a specific log entry by ID.
Args:
log_entry_id: The ID of the log entry
Returns:
LogEntry details
Inputs: log_entry_id (required). Returns: Log entry model representing a PagerDuty log entry. Note: Log entries have poly…
get_outlier_incidentARead-onlyIdempotent
Get Outlier Incident information for a given Incident on its Service.
Outlier Incident returns incident that deviates from the expected patterns
for the same Service. This feature is currently available as part of the
Event Intelligence package or Digital Operations plan only.
Args:
incident_id: The ID of the incident to get outlier incident information for
query_model: Query parameters including date range and additional details
Returns:
Outlier incident information calculated over the same Service as the given Incident
Inputs: incident_id (required), query_model (required). Returns: outlier_incident
get_past_incidentsARead-onlyIdempotent
Get Past Incidents related to a specific incident ID.
Past Incidents returns Incidents within the past 6 months that have similar
metadata and were generated on the same Service as the parent Incident.
By default, 50 Past Incidents are returned. This feature is currently available
as part of the Event Intelligence package or Digital Operations plan only.
Args:
incident_id: The ID of the incident to get past incidents for
query_model: Query parameters including limit and total flag
Returns:
List of past incidents with similarity scores
Inputs: incident_id (required), query_model (required). Returns: limit, total, past_incidents
get_responder_load_metricsARead-onlyIdempotent
Get aggregated load metrics per responder from PagerDuty Analytics.
Returns per-responder on-call hours, incident count, acknowledgment count,
sleep-hour interruptions, and engaged time. Use for responder workload analysis.
Args:
date_range_start: ISO8601 DateTime. Incidents with created_at before this value are omitted.
date_range_end: ISO8601 DateTime. Incidents with created_at >= this value are omitted.
team_ids: Only incidents related to these teams will be included.
urgency: Filter by urgency: 'high' or 'low'.
time_zone: The time zone for results (e.g. 'America/New_York').
order: Sort order: 'asc' or 'desc'.
order_by: Field to sort results by.
Returns:
JSON string of ListResponseModel containing AnalyticsResponderLoad objects.
Inputs: date_range_end (required), date_range_start (required), order, urgency, +3 more. Returns: result
get_responder_metricsARead-onlyIdempotent
Get responder metrics aggregated by team from PagerDuty Analytics.
Returns per-user oncall seconds, interruption counts (business hours, off hours, sleep hours),
engaged time, and incident counts for a given date range. Powered by PagerDuty's analytics
engine — oncall hours are computed authoritatively, accounting for schedule overlaps.
Args:
date_range_start: ISO8601 DateTime. Incidents with created_at before this value are omitted.
date_range_end: ISO8601 DateTime. Incidents with created_at >= this value are omitted.
team_ids: Only incidents related to these teams will be included.
responder_ids: Only incidents related to these responders will be included.
urgency: Filter by urgency: 'high' or 'low'.
time_zone: The time zone to use for results and grouping (e.g. 'America/New_York').
order: Sort order: 'asc' or 'desc'.
order_by: Field to sort results by.
Returns:
JSON string of ListResponseModel containing AnalyticsResponderMetrics objects.
Inputs: date_range_end (required), date_range_start (required), order, urgency, +4 more. Returns: result
get_scheduleARead-onlyIdempotent
Get a single schedule by ID — works for layer-based (v2) and shift-based (v3) schedules alike.
You normally do not need to know the kind in advance; this resolves it automatically.
Args:
schedule_id: The ID of the schedule to retrieve.
kind: Optional hint ("layer_based" or "shift_based", taken from a prior list result) to
skip an extra lookup. A wrong or omitted hint still resolves correctly.
Returns:
The schedule details (a layer-based Schedule or a shift-based ScheduleV3).
Inputs: schedule_id (required), kind. Returns: result
get_schedule_v3_custom_shiftCRead-onlyIdempotent
Get a specific custom shift within a v3 schedule.
Args:
schedule_id: The ID of the v3 schedule
custom_shift_id: The ID of the custom shift
Returns:
The custom shift
Inputs: schedule_id (required), custom_shift_id (required). Returns: An ad-hoc one-off shift outside of rotation events.
get_schedule_v3_overrideBRead-onlyIdempotent
Get a specific override within a v3 schedule.
Args:
schedule_id: The ID of the v3 schedule
override_id: The ID of the override
Returns:
The override
Inputs: override_id (required), schedule_id (required). Returns: An override shift (temporary replacement of a scheduled on-call member).
get_schedule_v3_rotationARead-onlyIdempotent
Get a specific rotation within a v3 schedule.
Args:
schedule_id: The ID of the v3 schedule
rotation_id: The ID of the rotation
Returns:
The rotation including its events
Inputs: rotation_id (required), schedule_id (required). Returns: A rotation within a v3 schedule. Scheduling logic is defined on the rotation's…
get_schedule_v3_rotation_eventCRead-onlyIdempotent
Get a specific event within a v3 schedule rotation.
Args:
schedule_id: The ID of the v3 schedule
rotation_id: The ID of the rotation
event_id: The ID of the event
Returns:
The rotation event
Inputs: event_id (required), rotation_id (required), schedule_id (required). Returns: A recurring on-call event within a rotation.
get_serviceARead-onlyIdempotent
Get details for a specific service.
Args:
service_id: The ID of the service to retrieve
Returns:
The service details
Inputs: service_id (required). Returns: id, name, teams, status, +2 more
get_status_page_postARead-onlyIdempotent
Get a Post for a Status Page by Status Page ID and Post ID.
Args:
status_page_id: The ID of the Status Page
post_id: The ID of the Status Page Post
query_model: Optional query parameters (e.g., include related resources)
Returns:
StatusPagePost details
Inputs: post_id (required), query_model (required), status_page_id (required). Returns: id, self, title, ends_at, +6 more
get_teamARead-onlyIdempotent
Get a specific team.
Args:
team_id: The ID or name of the team to retrieve
Returns:
Team details
Inputs: team_id (required). Returns: id, name, summary, description
get_technical_service_dependenciesBRead-onlyIdempotent
Get dependencies for a technical service.
Args:
service_id: The ID of the technical service
Returns:
JSON string with relationships list
Inputs: service_id (required). Returns: result
get_user_dataARead-onlyIdempotent
Get the current user's data.
Returns:
User: User name, role, id, and summary and teams
Inputs: no named parameters. Returns: id, name, role, email, +4 more
get_webhook_subscriptionARead-onlyIdempotent
Get a specific webhook subscription by ID.
Args:
subscription_id: The ID of the webhook subscription to retrieve
Returns:
Webhook subscription details
Inputs: subscription_id (required). Returns: A PagerDuty webhook subscription.
list_alert_grouping_settingsARead-onlyIdempotent
List all alert grouping settings with optional filtering.
Args:
service_ids: An array of service IDs. Only results related to these services will be returned.
limit: The number of results per page. Default 1000.
after: Cursor to retrieve next page.
before: Cursor to retrieve previous page.
total: Set to True to include total count in response.
Returns:
List of alert grouping settings matching the query parameters
Inputs: after, limit, total, before, +1 more. Returns: response
list_alerts_from_incidentARead-onlyIdempotent
List alerts for a specific incident.
Args:
incident_id: The ID of the incident
limit: Maximum number of results to return (1-1000). Default is 100.
offset: Offset for pagination. Default is 0.
Returns:
List of Alert objects for the given incident
Inputs: incident_id (required), limit, offset. Returns: response
list_business_servicesBRead-onlyIdempotent
List all business services.
Returns:
JSON string of business services
Inputs: no named parameters. Returns: result
list_change_eventsARead-onlyIdempotent
List all change events with optional filtering.
Change Events represent changes to systems, services, and applications that
can be correlated with incidents to provide context for troubleshooting.
Args:
since: The start of the date range over which you want to search.
until: The end of the date range over which you want to search.
limit: The number of results per page. Default 100.
offset: The offset of the first record returned.
total: Set to True to include total count in response.
team_ids: An array of team IDs. Only results related to these teams will be returned.
integration_ids: An array of integration IDs. Only results related to these integrations will be returned.
Returns:
List of ChangeEvent objects matching the query parameters
Inputs: limit, since, total, until, +3 more. Returns: response
list_escalation_policiesARead-onlyIdempotent
List escalation policies with optional filtering.
Args:
query: Filter by name
user_ids: Filter by user IDs
team_ids: Filter by team IDs
include: Additional details to include (e.g. services, teams)
limit: Max results to return
Returns:
List of escalation policies matching the query parameters
Inputs: limit, query, include, team_ids, +1 more. Returns: response
list_event_orchestrationsARead-onlyIdempotent
List event orchestrations with optional filtering.
Args:
limit: The number of results per page. Default 100.
offset: Offset to start pagination search results.
sort_by: Field and direction to sort by. Default 'name:asc'. Options:
'name:asc', 'name:desc', 'routes:asc', 'routes:desc',
'created_at:asc', 'created_at:desc'.
Returns:
List of event orchestrations matching the query parameters
Inputs: limit, offset, sort_by. Returns: response
list_extension_schemasARead-onlyIdempotent
List available extension schemas (extension vendors).
Extension schemas describe the available extension integrations that can be
attached to PagerDuty services.
Args:
limit: Max results to return
Returns:
List of extension schemas
Inputs: limit. Returns: response
list_incident_change_eventsARead-onlyIdempotent
List change events related to a specific incident.
Args:
incident_id: The ID of the incident
limit: Maximum number of results to return (optional)
Returns:
List of ChangeEvent objects related to the incident
Inputs: incident_id (required), limit. Returns: response
list_incident_notesARead-onlyIdempotent
List all notes for a specific incident.
Args:
incident_id: The ID of the incident to retrieve notes from
Returns:
List of IncidentNote objects for the specified incidentInputs: incident_id (required). Returns: response
list_incidentsARead-onlyIdempotent
List incidents with optional filtering.
Args:
request_scope: Scope of incidents to return: 'all', 'assigned', or 'teams'
statuses: Filter by status (e.g. triggered, acknowledged, resolved)
since: Filter incidents created after this datetime
until: Filter incidents created before this datetime
urgencies: Filter by urgency (high, low)
priorities: Filter by priority IDs (use list_priorities to resolve names to IDs)
limit: Max results to return (default 1000)
Returns:
List of Incident objects matching the query parameters
Inputs: limit, since, until, statuses, +3 more. Returns: response
list_incident_workflowsARead-onlyIdempotent
List incident workflows with optional filtering.
Args:
limit: Maximum number of results to return. Maximum is 100. Default 100.
query: Filters the result, showing only the records whose name matches the query.
include: Array of additional details to include. Options: 'steps', 'team'.
Returns:
List of IncidentWorkflow objects matching the query parameters
Inputs: limit, query, include. Returns: response
list_log_entriesARead-onlyIdempotent
List all log entries across the account.
Log entries are records of all events on your account. This function allows you
to filter log entries by time range and paginate through results.
If no time range is specified, defaults to the last 7 days.
Args:
query_model: Query parameters including since, until, limit, and offset
Returns:
List of LogEntry objects matching the query parametersInputs: query_model. Returns: response
list_oncallsARead-onlyIdempotent
List on-call schedules with optional filtering.
Args:
time_zone: Time zone for date rendering (e.g. America/New_York)
user_ids: Filter by user IDs
escalation_policy_ids: Filter by escalation policy IDs
schedule_ids: Filter by schedule IDs
service_ids: Filter by service IDs. Resolves each service to its escalation policy to find on-call responders.
since: Start of time range
until: End of time range
earliest: Return only earliest oncall per user/policy combination. Defaults to True.
limit: Max results to return
Returns:
List of on-call schedules matching the query parameters
Inputs: limit, since, until, earliest, +5 more. Returns: response
list_prioritiesARead-onlyIdempotent
List all priorities configured in the account.
Returns:
JSON string of ListResponseModel containing PriorityReference objects
Inputs: no named parameters. Returns: result
list_schedulesARead-onlyIdempotent
List ALL PagerDuty schedules across BOTH scheduling systems in a single call.
This returns classic layer-based (v2) schedules AND next-gen shift-based (v3) schedules
together. It is the complete, authoritative schedule list — there is no other list tool.
Each item's `kind` field ("layer_based" or "shift_based") says which system it belongs to.
If either source fails, `response_summary`/`sources` explicitly mark the list INCOMPLETE;
otherwise treat it as exhaustive. Never tell the user a schedule type is unsupported or missing.
Args:
query_model: Filters (name query, team_ids, user_ids, limit). Shift-based (v3) schedules
are filtered by name `query` and `limit` only.
enrich: When True (default), fill in names for shift-based (v3) schedules (bounded to the
returned page, max 50). Set False to skip the extra lookups; v3 names may then be null.
Returns:
The merged schedule summaries with per-source status and a `degraded` flag.
Inputs: query_model (required), enrich. Returns: Unified schedules list spanning BOTH the layer-based (v2) and shift-based (v3)…
list_schedule_usersARead-onlyIdempotent
List users in a schedule.
Args:
schedule_id: The ID of the schedule
Returns:
List of users in the schedule
Inputs: schedule_id (required). Returns: response
list_schedule_v3_custom_shiftsARead-onlyIdempotent
List custom shifts for a v3 schedule within a time range.
Custom shifts are ad-hoc one-off shifts outside of rotation events.
Args:
schedule_id: The ID of the v3 schedule
since: Start of the time range (ISO 8601, required)
until: End of the time range (ISO 8601, required)
Returns:
List of custom shifts in the specified time range
Inputs: since (required), until (required), schedule_id (required). Returns: response
list_schedule_v3_overridesARead-onlyIdempotent
List overrides for a v3 schedule within a time range.
Args:
schedule_id: The ID of the v3 schedule
since: Start of the time range (ISO 8601, required)
until: End of the time range (ISO 8601, required)
Returns:
List of overrides in the specified time range
Inputs: since (required), until (required), schedule_id (required). Returns: response
list_schedule_v3_rotation_eventsARead-onlyIdempotent
List all events for a rotation in a v3 schedule.
Args:
schedule_id: The ID of the v3 schedule
rotation_id: The ID of the rotation
Returns:
List of events defining the on-call coverage windows and member assignments
Inputs: rotation_id (required), schedule_id (required). Returns: response
list_schedule_v3_rotationsARead-onlyIdempotent
List all rotations for a v3 schedule.
Args:
schedule_id: The ID of the v3 schedule
Returns:
List of rotations for the schedule
Inputs: schedule_id (required). Returns: response
list_service_change_eventsARead-onlyIdempotent
List all change events for a specific service.
Args:
service_id: The ID of the service.
since: The start of the date range over which you want to search.
until: The end of the date range over which you want to search.
limit: The number of results per page. Default 100.
offset: The offset of the first record returned.
total: Set to True to include total count in response.
team_ids: An array of team IDs. Only results related to these teams will be returned.
integration_ids: An array of integration IDs. Only results related to these integrations will be returned.
Returns:
List of ChangeEvent objects associated with the service
Inputs: service_id (required), limit, since, total, +4 more. Returns: response
list_servicesARead-onlyIdempotent
List all services.
Args:
query: Filter by name
teams_ids: Filter by team IDs
limit: Max results to return
Returns:
List of services matching the query parameters
Inputs: limit, query, teams_ids. Returns: response
list_status_page_impactsARead-onlyIdempotent
List Impacts for a Status Page by Status Page ID.
Args:
status_page_id: The ID of the Status Page
query_model: Optional filtering parameters
Returns:
List of StatusPageImpact objects for the given Status Page
Inputs: status_page_id (required), query_model. Returns: response
list_status_page_post_updatesARead-onlyIdempotent
List Post Updates for a Status Page by Status Page ID and Post ID.
Args:
status_page_id: The ID of the Status Page
post_id: The ID of the Status Page Post
query_model: Optional filtering parameters
Returns:
List of StatusPagePostUpdate objects for the given Post
Inputs: post_id (required), status_page_id (required), query_model. Returns: response
list_status_pagesARead-onlyIdempotent
List Status Pages with optional filtering.
Args:
query_model: Optional filtering parameters
Returns:
List of StatusPage objects matching the query parameters
Inputs: query_model. Returns: response
list_status_page_severitiesARead-onlyIdempotent
List Severities for a Status Page by Status Page ID.
Args:
status_page_id: The ID of the Status Page
query_model: Optional filtering parameters
Returns:
List of StatusPageSeverity objects for the given Status Page
Inputs: status_page_id (required), query_model. Returns: response
list_status_page_statusesARead-onlyIdempotent
List Statuses for a Status Page by Status Page ID.
Args:
status_page_id: The ID of the Status Page
query_model: Optional filtering parameters
Returns:
List of StatusPageStatus objects for the given Status Page
Inputs: status_page_id (required), query_model. Returns: response
list_team_membersARead-onlyIdempotent
List members of a team.
Args:
team_id: The ID of the team
Returns:
List of UserReference objects
Inputs: team_id (required). Returns: response
list_teamsARead-onlyIdempotent
List teams with optional filtering.
Args:
scope: 'all' for all teams, 'my' for teams the current user belongs to
query: Filter by team name
limit: Max results to return
Returns:
List of teams.
Inputs: limit, query, scope. Returns: response
list_usersARead-onlyIdempotent
List users, optionally filtering by name (query) and team IDs.
Args:
query: Filters the result, showing only the records whose name matches the query.
teams_ids: Filter users by team IDs.
limit: Pagination limit. Default 100.
Returns:
List of users matching the criteria.
Inputs: limit, query, teams_ids. Returns: response
list_webhook_subscriptionsARead-onlyIdempotent
List webhook subscriptions.
Args:
filter_type: Filter by scope type: 'account_reference', 'service_reference', or 'team_reference'
limit: Max results to return
Returns:
List of webhook subscriptions
Inputs: limit, filter_type. Returns: response
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 63 tools
Every tool targets a distinct entity or specific sub-aspect of an entity (e.g., get_incident vs. get_outlier_incident, list_schedule_v3_rotations vs. list_schedule_v3_rotation_events). No two tools have overlapping purposes.
All tools follow a consistent verb_noun pattern using 'get_' for single resources and 'list_' for collections. There is no mixing of camelCase or other conventions.
63 tools is far above the typical well-scoped range (3-15). While the tool count covers many PagerDuty entities, the sheer number makes the surface difficult to navigate and suggests insufficient consolidation.
The server is entirely read-only with no create, update, delete, or action tools (e.g., acknowledge_incident, create_service). For an incident management platform, this is a severe gap that prevents agents from performing any operational actions.
Maintenance
Related MCP Connectors
Manage uptime monitors, incidents and status pages from any MCP client.
Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.
Your team's custom tools and skills in every agent, through one MCP connection.
An AI concierge that turns static forms into adaptive AI conversations. From any MCP client.
Related MCP Servers
- AlicenseAqualityCmaintenanceA community-maintained MCP server for interacting with PagerDuty accounts, enabling management of incidents, services, schedules, and event orchestrations through MCP-enabled clients.201Apache 2.0

runframe-mcp-serverofficial
AlicenseNot gradedqualityDmaintenanceEnables managing incident response workflows including incidents, on-call, postmortems, and more through the Runframe platform using MCP tools.76 npm4MIT- AlicenseNot gradedqualityDmaintenanceEnables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage PagerDuty incidents, view alerts, and check on-call schedules with both read-only and write operations.9Apache 2.0