Pagerduty MCP server

Read from the package source without running it. The installed server may list more.

• add_and_remove_tags_for_entitywrite action

  Add or remove tags from a user, team, or escalation policy. Tags can be existing tags or newly created ones, and are used to organize and filter entities.

• add_automation_action_team

  Associate an Automation Action with a team, enabling the team to access and manage the automation action.

• add_subscribers_to_business_service

  Subscribe one or more entities (users, teams, or schedules) to a Business Service to receive notifications related to that service.

• associate_automation_action_with_service

  Associate an Automation Action with a service to enable the action to be triggered by or applied to that service. This establishes the relationship between an automation action and a specific service in your PagerDuty account.

• associate_runner_with_team

  Associate an automation actions runner with a team to enable the team to use that runner for executing automations.

• check_account_ability

  Check whether your account has a specific capability or feature enabled. Abilities represent account features (such as 'teams') that may be available based on your pricing plan or account state.

• create_automation_actionwrite action

  Create a new automation action (Script, Process Automation, or Runbook Automation) to define automated workflows and tasks within PagerDuty.

• create_automation_runnerwrite action

  Create a new automation runner for Process Automation or Runbook Automation workflows. The runner executes automation actions within your PagerDuty environment.

• create_business_servicewrite action

  Create a new Business Service that models capabilities spanning multiple technical services and owned by different teams. Each account is limited to 5,000 business services.

• create_cache_variable_for_global_orchestrationwrite action

  Create a cache variable on a global event orchestration to store event data for use in orchestration rules, conditions, and actions.

• create_cache_variable_for_service_orchestrationwrite action

  Create a cache variable for a service event orchestration to store event data that can be referenced in orchestration rules for conditions and actions.

• create_escalation_policywrite action

  Creates a new escalation policy that defines which users should be alerted and when. At least one escalation rule must be provided in the request.

• create_event_orchestrationwrite action

  Create a Global Event Orchestration to define rules and routing logic for incoming events. Events ingested using the orchestration's routing key will be processed through Global Rules and then routed to the appropriate Service based on Router Rules.

• create_integration_for_event_orchestrationwrite action

  Create a new integration for an Event Orchestration to generate a routing key for sending events to PagerDuty. Each integration provides a unique routing key that can be used to route events through the orchestration's rules.

• delete_automation_actionwrite action

  Permanently delete an Automation Action by its ID. This operation removes the automation action and cannot be undone.

• delete_automation_actions_runnerwrite action

  Permanently delete an Automation Action runner by its ID. This operation removes the runner and cannot be undone.

• delete_business_servicewrite action

  Permanently delete a business service by its ID. Once deleted, the service will no longer be accessible in the web UI and cannot be associated with new incidents.

• delete_cache_variable_from_global_orchestrationwrite action

  Remove a cache variable from a global event orchestration. Cache variables store event data that can be referenced in orchestration rules for conditions and actions.

• delete_escalation_policywrite action

  Permanently delete an escalation policy and its associated rules. The escalation policy must not be actively used by any services before deletion.

• delete_external_data_cache_variable_datawrite action

  Delete stored data for an external data type Cache Variable on a Global Event Orchestration. This removes the cached values that were previously set via the dedicated API endpoint.

• delete_orchestrationwrite action

  Delete a Global Event Orchestration. Once deleted, the orchestration's Routing Key can no longer be used to ingest events into PagerDuty.

• delete_orchestration_integrationwrite action

  Delete an integration from an Event Orchestration, which stops PagerDuty from accepting events sent to the associated Routing Key. Once deleted, all future events using that Routing Key will be dropped.

• get_addon

  Retrieve details about a specific Add-on, which is a piece of functionality that extends PagerDuty's UI with custom features.

• get_aggregated_incident_metrics_across_services
• get_alert_grouping_setting

  Retrieve a specific Alert Grouping Setting by ID. Alert Grouping Settings define the configurations used by the Alert Grouper service to organize and group alerts.

• get_analytics_metrics_for_all_responders

  Retrieve aggregated incident metrics across all responders, including resolution time, engagement time, and sleep interruptions. Results can be filtered by date range, urgency, teams, and responders, with data updated periodically (up to 24 hours for new incidents).

• get_analytics_metrics_for_all_users

  Retrieve aggregated analytics metrics across all users in your account, including activity and performance statistics. Note: Analytics data updates periodically with up to 24 hours latency for new incidents.

• get_analytics_metrics_incidents_for_all_teams
• get_analytics_metrics_responders_by_team

  Retrieve incident response metrics aggregated by team, including resolution time, engagement time, and sleep interruptions. Analytics data updates periodically with up to 24-hour latency for new incidents.

• get_automation_action

  Retrieve a specific automation action by its ID. Returns the full details of the automation action resource.

• get_automation_action_invocation

  Retrieve details about a specific Automation Action Invocation by its ID. This returns the current state and metadata of an invocation execution.

• get_automation_action_service_association

  Retrieve the details of the relationship between a specific Automation Action and a service. This shows how an automation action is associated with and configured for a particular service.

• get_automation_action_team_association

  Retrieve the association details between a specific Automation Action and a team, including their relationship configuration and metadata.

• get_automation_actions_runner

  Retrieve a specific Automation Action runner by its ID. Use this to fetch details about a configured runner instance.

• get_business_service

  Retrieve details about a specific Business Service, which represents a capability spanning multiple technical services and potentially owned by several teams.

• get_business_service_priority_thresholds

  Retrieve the global priority threshold that determines when an Incident is considered to impact a Business Service. This threshold applies account-wide, affecting any Business Service that depends on the Service to which an Incident belongs.

• get_cache_variable_for_global_orchestration

  Retrieve a specific cache variable from a global event orchestration. Cache variables store event data that can be referenced in orchestration rules for conditions and actions.

• get_cache_variable_for_service_orchestration

  Retrieve a specific cache variable from a service's event orchestration. Cache variables store event data that can be referenced in orchestration rules for conditions and actions.

• get_change_event

  Retrieve detailed information about a specific Change Event by its ID. Returns the full Change Event resource with all associated metadata.

• get_escalation_policy

  Retrieve details about an escalation policy, including its rules that define which users should be alerted and when. Optionally include related services, teams, or escalation targets in the response.

• get_escalation_policy_incident_metrics
• get_escalation_policy_incident_metrics_aggregated
• get_event_orchestration_global

  Retrieve the Global Orchestration rules for an Event Orchestration. Global rules evaluate all incoming events and can modify, enhance, and route events for further processing within the orchestration.

• get_event_orchestration_router

  Retrieve the routing rules for an Event Orchestration. The router evaluates incoming events against a set of rules and directs them to the appropriate Service based on the first matching rule, or to a catch-all service if no rules match.

• get_external_data_cache_variable_data

  Retrieve the stored data for an external data type Cache Variable on a Global Event Orchestration. External data Cache Variables store string, number, or boolean values that can be referenced in Event Orchestration rules and conditions.

• get_incident_analytics

  Retrieve enriched analytics data and metrics for a single incident, including resolution time, engagement time, and sleep interruption metrics. Note: Analytics data updates periodically with up to 24 hours latency for new incidents.

• get_incident_analytics_aggregated
• get_incident_response_analytics

  Retrieve enriched responder analytics for a specific incident, including metrics like time to respond, responder type, and response status. Note: Analytics data updates daily with up to 24-hour latency for new incident responses.

• get_integration_for_orchestration

  Retrieve a specific integration associated with an event orchestration. Use the routing key from the returned integration to send events to PagerDuty.

• get_orchestration

  Retrieve a Global Event Orchestration by ID. Global Event Orchestrations define Global Rules and Router Rules that process and route incoming events to the appropriate Service based on event content.

• get_pd_advance_usage_metrics
• get_runner_team_association

  Retrieve the association details between a specific automation action runner and a team, including their relationship configuration and status.

• get_service_incident_analytics
• get_service_orchestration

  Retrieve the Event Orchestration configuration for a specific service. The orchestration defines a set of event rules that process and route incoming events through multiple rule sets for enhancement and conditional handling.

• get_service_orchestration_active_status

  Retrieve whether a Service Orchestration is active for a given service. When active (true), events are evaluated against the service orchestration path; when inactive (false), events are evaluated against the service ruleset instead.

• get_team_incident_analytics
• get_unrouted_orchestration

  Retrieve the Unrouted Orchestration rules for an Event Orchestration, which processes events that don't match any rules in the Global Orchestration's Router. The Unrouted Orchestration evaluates these events against its rule sets and can modify, enhance, or route them for further processing.

• invoke_automation_action

  Triggers an invocation of an automation action, optionally scoped to a specific incident or alert. This executes the action's defined workflow or automation logic.

• list_abilities

  Retrieve all capabilities available to your account based on your pricing plan and account state. Abilities are feature names (e.g., 'teams') that indicate what functionality your account can access.

• list_analytics_incidents

  Retrieve enriched incident data and metrics for multiple incidents, including resolution time, engagement time, and sleep interruptions. Analytics data updates periodically with up to 24-hour latency for new incidents.

• list_analytics_users

  Retrieve raw user analytics data for your account, including detailed user activity and configuration metrics. Note that analytics data updates periodically with up to 24 hours latency for new user data.

• list_audit_records

  Retrieve audit trail records for your PagerDuty account, filtered by date range and optional criteria like resource type, actor, or action. Results are sorted by execution time from newest to oldest and support cursor-based pagination.

• list_automation_action_invocations

  Retrieve a list of automation action invocations, optionally filtered by invocation state, incident, or action. Use this to track the execution history and status of automated actions.

• list_automation_action_runners

  Retrieve a list of Automation Action runners filtered by query parameters. Results are sorted alphabetically by runner name and support cursor-based pagination.

• list_automation_action_service_associations

  Retrieve all service references associated with a specific Automation Action. This returns the complete list of services linked to the automation action for management and visibility purposes.

• list_automation_action_team_associations

  Retrieve all teams associated with a specific Automation Action. Use this to view which teams are linked to an automation action for access control and assignment purposes.

• list_automation_actions

  Retrieves a list of automation actions filtered by optional criteria such as runner, classification, team, service, or action type. Results are sorted alphabetically by action name and support cursor-based pagination.

• list_business_service_impactors

  Retrieve the highest-priority Impactors (currently limited to Incidents) affecting top-level Business Services on your account, sorted by priority and creation date. Returns up to 200 results; use the ids[] parameter to filter for specific Business Services.

• list_business_service_subscribers

  Retrieve all notification subscribers configured for a specific Business Service. Only subscribers that have been explicitly added through the subscriber creation endpoint will be returned.

• list_business_services

  Retrieve a list of existing business services that span multiple technical services and may be owned by different teams. Use this to discover available business services in your PagerDuty instance.

• list_business_services_by_impact

  Retrieve the most impacted Business Services sorted by impact level, recency, and name. Without filtering by IDs, returns up to 200 of the highest-impact services; use the `ids[]` parameter to get impact data for a specific set of Business Services.

• list_cache_variables_for_global_orchestration

  Retrieve all cache variables stored on a global event orchestration. Cache variables store event data that can be referenced in orchestration rules for conditions and actions.

• list_cache_variables_for_service_orchestration

  Retrieve all cache variables configured for a service's event orchestration. Cache variables store event data that can be referenced in orchestration rules for conditions and actions.

• list_change_events

  Retrieve all change events, optionally filtered by teams, integrations, or date range. Change events track modifications across your PagerDuty account.

• list_escalation_policies

  Retrieve all escalation policies that define which users should be alerted and when. Optionally filter by users, teams, or include related service and target details.

• list_escalation_policy_audit_records

  Retrieve audit records for a specific escalation policy, sorted by execution time from newest to oldest. Use cursor-based pagination to navigate through results.

• list_event_orchestrations

  Retrieve all Global Event Orchestrations configured on your account. Global Event Orchestrations enable you to define rules that automatically process and route incoming events to the appropriate services based on event content.

• list_integrations_for_event_orchestration

  Retrieve all integrations associated with a specific Event Orchestration. Use the routing keys from these integrations to send events to PagerDuty.

• list_responder_incidents

  Retrieve enriched incident data and performance metrics for a specific responder, including resolution times, engagement times, and sleep interruptions. Note: Analytics data updates periodically and may take up to 24 hours to reflect new incidents.

• list_runner_team_associations

  Retrieve all teams associated with an automation action runner. Use this to view which teams have access to or are linked with a specific runner.

• list_supporting_service_impacts

  Retrieve the supporting Business Services for a given Business Service, sorted by impact level and recency. Returns up to 200 most impacted supporting services with their impact status.

• list_tags_for_entity

  Retrieve all tags associated with a specific user, team, or escalation policy. Tags are used to organize and filter these entities within PagerDuty.

• move_integration_between_orchestrations

  Relocate an Integration and its Routing Key from a source Event Orchestration to a target Event Orchestration. Future events sent to the Integration's Routing Key will be processed by the target orchestration's rules.

• remove_automation_action_service_associationwrite action

  Remove the association between an Automation Action and a service, effectively disabling that action for the specified service.

• remove_automation_action_team_associationwrite action

  Remove the association between an Automation Action and a specific team, effectively disassociating them from each other.

• remove_business_service_account_subscriptionwrite action

  Unsubscribe your account from a Business Service. This operation removes the subscription relationship between your account and the specified Business Service.

• remove_business_service_notification_subscriberswrite action

  Unsubscribe one or more subscribers from receiving notifications for a specific Business Service. This operation removes the notification subscriptions for the provided subscriber IDs.

• remove_runner_from_teamwrite action

  Removes the association between an automation action runner and a team, preventing the runner from executing actions for that team.

• send_change_eventwrite action

  Send a change event to PagerDuty to notify about infrastructure or application changes. This operation integrates with the V2 Events API for change event tracking.

• subscribe_account_to_business_service

  Subscribe your account to a Business Service, enabling access to its features and capabilities. Requires the `subscribers.write` OAuth scope.

• update_automation_actionwrite action

  Updates an existing Automation Action with new configuration. Specify the action ID and provide the updated action details in the request body.

• update_automation_actions_runnerwrite action

  Update the configuration and settings of an existing Automation Action runner. This operation allows you to modify runner properties such as name, status, or other operational parameters.

• update_business_servicewrite action

  Update an existing Business Service that spans multiple technical services and may be owned by several teams. Supports both PUT and PATCH HTTP methods.

• update_cache_variable_external_datawrite action

  Update the data value stored in an external data type cache variable on a global event orchestration. The updated value can then be referenced in event orchestration rules and conditions.

• update_cache_variable_for_global_orchestrationwrite action

  Update a cache variable on a global event orchestration. Cache variables store event data that can be referenced in orchestration rules for conditions and actions.

• update_cache_variable_for_service_orchestrationwrite action

  Update a cache variable on a service event orchestration. Cache variables store event data that can be referenced in orchestration rules for conditions and actions.

• update_change_eventwrite action

  Update an existing Change Event in PagerDuty. Modify the properties of a specific Change Event using its ID.

• update_escalation_policywrite action

  Update an existing escalation policy to modify alert routing rules and user notification timing. Escalation policies define the sequence and timing of which users should be alerted during an incident.

• update_event_orchestration_integrationwrite action

  Update an integration associated with an Event Orchestration. The integration's routing key can be used to send events to PagerDuty.

• update_service_orchestration_active_statuswrite action

  Enable or disable event evaluation against a service orchestration path for a specific service. When active, events are evaluated using the orchestration path; when inactive, they fall back to the service ruleset.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 48,255 servers

Tools

100

the typical server has 7

Tools that change things

33%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 92% of 28,688 servers

Pagerduty: common questions

Is Pagerduty MCP server safe?

Mostly: it is graded B (80/100). Read the Pagerduty safety report

How do I install Pagerduty?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Pagerduty need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Pagerduty maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.2.

What can I use instead of Pagerduty?

Servers from other publishers that do the same job: OneUptime MCP server.

How does Pagerduty compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,255 servers); tools 100 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.