Summary
PagerDuty's official MCP server gives you full incident lifecycle management without leaving your IDE. You get tools for creating and triaging incidents, managing on-call schedules and overrides, configuring escalation policies, and working with event orchestrations. What stands out are the embedded React apps: an incident command center with AI-powered similar incident detection, an on-call manager for schedule overrides, a compensation report tracking hours and compliance metrics, and a service dependency graph visualizer. Configure it with your User API Token and enable write-tools flag to go beyond read-only operations. Works with VS Code, Cursor, and Claude Desktop via stdio transport.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Tools
Public tool metadata for what this MCP can expose to an agent.
80 tools
PAGERDUTY_ADD_SERVICE_TO_INCIDENT_WORKFLOW_TRIGGERThis endpoint adds a service to an existing incident workflow trigger in PagerDuty. It allows you to associate a specific service with a trigger, enabling automated incident management processes for that service. Use this endpoint when you need to connect a service to an incid...2 params
This endpoint adds a service to an existing incident workflow trigger in PagerDuty. It allows you to associate a specific service with a trigger, enabling automated incident management processes for that service. Use this endpoint when you need to connect a service to an incid...
Parameters* required
idstringThe ID of the resource.
service__idstringId
PAGERDUTY_AGGREGATE_ESCALATION_POLICY_INCIDENT_METRICSThis endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty. It allows for detailed filtering and customization of the analysis, enabling users to gain insights into incident patterns, response times, and escalation effectiveness. The end...17 params
This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty. It allows for detailed filtering and customization of the analysis, enabling users to gain insights into incident patterns, response times, and escalation effectiveness. The end...
Parameters* required
orderstringThe order in which the results were sorted; asc for ascending, desc for descending. one of
asc · descorder_bystringThe column that was used for ordering the results.
time_zonestringThe time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
aggregate_unitstringThe time unit to aggregate metrics by. If no value is provided, the metrics will be aggregated for the entire period. one of
day · week · monthfilters__majorbooleanA boolean flag including whether results should contain *only* [major incidents](https://support.pagerduty.com/docs/operational-reviews#major-incidents), or exclude major incidents. If no value is provided all incidents will be included.
filters__urgencystringAny incidents whose urgency does not match the provided string will be omitted from the results. one of
high · lowfilters__team__idsarrayAn array of team IDs. Only incidents related to these teams will be included in the results. If omitted, all teams the requestor has access to will be included in the results.
filters__service__idsarrayAn array of service IDs. Only incidents related to these services will be included in the results. If omitted, all services the requestor has access to will be included in the results.
filters__priority__idsarrayAn array of priority IDs. Only incidents with these priorities will be included in the results. If omitted, all priorities will be included in the results.
filters__priority__namesarrayAn array of user-defined priority names. Only incidents with these priorities will be included in the results. If omitted, all priorities will be included in the results.
filters__created__at__endstringAccepts an ISO8601 DateTime string. Any incidents with a created_at greater than or equal to this value will be omitted from the results. The maximum supported time range in conjunction with created_at_start is one year.
filters__pd__advance__usedbooleanIf true, only incidents where PD Advance was used will be included in the results, and vice versa. If omitted, all incidents will be included.
filters__created__at__startstringAccepts an ISO8601 DateTime string. Any incidents with a created_at less than this value will be omitted from the results. The maximum supported time range in conjunction with created_at_end is one year.
filters__min__ackowledgementsintegerAn integer that sets the requirement for the minimum number of acknowledgements to occur on an incident. For example, setting this to 1 will return only incidents that have at least 1 acknowledgement. If no value is provided, all incidents will be included.
filters__escalation__policy__idsarrayAn array of escalation policy IDs. Only incidents related to these escalation policies will be included in the results. If omitted, all escalation policies the requestor has access to will be included in the results.
filters__min__manual__escalationsintegerAn integer that sets the requirement for the minimum number of manual escalations to occur on an incident. For example, setting this to 1 will return only incidents that have at least 1 manual escalation. If no value is provided, all incidents will be included.
filters__min__timeout__escalationsintegerAn integer that sets the requirement for the minimum number of timeout escalations to occur on an incident. For example, setting this to 1 will return only incidents that have at least 1 timeout escalation. If no value is provided, all incidents will be included.
PAGERDUTY_AGGREGATE_INCIDENT_METRICS_WITH_FILTERSRetrieves and aggregates metrics for incidents across all services in PagerDuty. This endpoint allows for extensive filtering and customization of incident data, enabling detailed analysis of operational performance. It's particularly useful for generating reports, identifying...17 params
Retrieves and aggregates metrics for incidents across all services in PagerDuty. This endpoint allows for extensive filtering and customization of incident data, enabling detailed analysis of operational performance. It's particularly useful for generating reports, identifying...
Parameters* required
orderstringThe order in which the results were sorted; asc for ascending, desc for descending. one of
asc · descorder_bystringThe column that was used for ordering the results.
time_zonestringThe time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
aggregate_unitstringThe time unit to aggregate metrics by. If no value is provided, the metrics will be aggregated for the entire period. one of
day · week · monthfilters__majorbooleanA boolean flag including whether results should contain *only* [major incidents](https://support.pagerduty.com/docs/operational-reviews#major-incidents), or exclude major incidents. If no value is provided all incidents will be included.
filters__urgencystringAny incidents whose urgency does not match the provided string will be omitted from the results. one of
high · lowfilters__team__idsarrayAn array of team IDs. Only incidents related to these teams will be included in the results. If omitted, all teams the requestor has access to will be included in the results.
filters__service__idsarrayAn array of service IDs. Only incidents related to these services will be included in the results. If omitted, all services the requestor has access to will be included in the results.
filters__priority__idsarrayAn array of priority IDs. Only incidents with these priorities will be included in the results. If omitted, all priorities will be included in the results.
filters__priority__namesarrayAn array of user-defined priority names. Only incidents with these priorities will be included in the results. If omitted, all priorities will be included in the results.
filters__created__at__endstringAccepts an ISO8601 DateTime string. Any incidents with a created_at greater than or equal to this value will be omitted from the results. The maximum supported time range in conjunction with created_at_start is one year.
filters__pd__advance__usedbooleanIf true, only incidents where PD Advance was used will be included in the results, and vice versa. If omitted, all incidents will be included.
filters__created__at__startstringAccepts an ISO8601 DateTime string. Any incidents with a created_at less than this value will be omitted from the results. The maximum supported time range in conjunction with created_at_end is one year.
filters__min__ackowledgementsintegerAn integer that sets the requirement for the minimum number of acknowledgements to occur on an incident. For example, setting this to 1 will return only incidents that have at least 1 acknowledgement. If no value is provided, all incidents will be included.
filters__escalation__policy__idsarrayAn array of escalation policy IDs. Only incidents related to these escalation policies will be included in the results. If omitted, all escalation policies the requestor has access to will be included in the results.
filters__min__manual__escalationsintegerAn integer that sets the requirement for the minimum number of manual escalations to occur on an incident. For example, setting this to 1 will return only incidents that have at least 1 manual escalation. If no value is provided, all incidents will be included.
filters__min__timeout__escalationsintegerAn integer that sets the requirement for the minimum number of timeout escalations to occur on an incident. For example, setting this to 1 will return only incidents that have at least 1 timeout escalation. If no value is provided, all incidents will be included.
PAGERDUTY_ASSOCIATE_SERVICE_DEPENDENCIESAssociates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services. This endpoint is used to establish a hierarchical structure of services, which is crucial for effective incident management and impact analysi...1 params
Associates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services. This endpoint is used to establish a hierarchical structure of services, which is crucial for effective incident management and impact analysi...
Parameters* required
relationshipsarrayList of all service dependencies to be created.
PAGERDUTY_ASSOCIATE_TEAM_WITH_AUTOMATION_ACTIONThis endpoint associates a specific team with an automation action in PagerDuty. It allows you to link a team to an automated workflow, enabling better organization and management of automation actions within your incident response processes. Use this endpoint when you need to...1 params
This endpoint associates a specific team with an automation action in PagerDuty. It allows you to link a team to an automated workflow, enabling better organization and management of automation actions within your incident response processes. Use this endpoint when you need to...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_AUDIT_ESCALATION_POLICY_RECORDSRetrieves the audit records for a specific escalation policy in PagerDuty. This endpoint allows users to access a detailed history of changes made to the escalation policy, including modifications to escalation rules, associated services, and on-call schedules. It's particular...5 params
Retrieves the audit records for a specific escalation policy in PagerDuty. This endpoint allows users to access a detailed history of changes made to the escalation policy, including modifications to escalation rules, associated services, and on-call schedules. It's particular...
Parameters* required
idstringThe ID of the resource.
limitintegerThe minimum of the `limit` parameter used in the request or the maximum request size of the API.
sincestringThe start of the date range over which you want to search. If not specified, defaults to `now() - 24 hours` (past 24 hours)
untilstringThe end of the date range over which you want to search. If not specified, defaults to `now()`. May not be more than 31 days after `since`.
cursorstringOptional parameter used to request the "next" set of results from an API. The value provided here is most commonly obtained from the `next_cursor` field of the previous request. When no value is provided, the request starts at the beginning of the result set.
PAGERDUTY_CONVERT_SERVICE_RULE_BY_IDConverts the rules associated with a specific PagerDuty service to a new or optimized format. This endpoint is used to update and standardize the incident management rules for a given service, improving the efficiency and consistency of alert handling. It should be used when t...1 params
Converts the rules associated with a specific PagerDuty service to a new or optimized format. This endpoint is used to update and standardize the incident management rules for a given service, improving the efficiency and consistency of alert handling. It should be used when t...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_COUNT_PAUSED_INCIDENT_REPORTSRetrieves the count of paused incident reports in the PagerDuty system. This endpoint is part of PagerDuty's Incident Management and Analytics features, providing a quick way to quantify the number of incidents that are currently in a paused state. It's particularly useful for...4 params
Retrieves the count of paused incident reports in the PagerDuty system. This endpoint is part of PagerDuty's Incident Management and Analytics features, providing a quick way to quantify the number of incidents that are currently in a paused state. It's particularly useful for...
Parameters* required
sincestringThe start of the date range over which you want to search.
untilstringThe end of the date range over which you want to search.
service_idstringSpecifies a filter to limit the scope of reporting to a particular service
suspended_byvalueSpecifies a filter to scope the response to either alerts suspended by Auto Pause or Event Rules.
PAGERDUTY_CREATE_A_CUSTOM_FIELD_FOR_AN_INCIDENT_TYPECreate a Custom Field for an Incident Type. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be a...9 params
Create a Custom Field for an Incident Type. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be a...
Parameters* required
field__namestringThe name of the custom field.
field__enabledbooleanWhether the custom field is enabled.
type_id_or_namestringThe ID or name of the Incident Type.
field__data__typestringThe data type of the custom field.
field__descriptionstringThe description of the custom field.
field__field__typestringThe field type of the custom field.one of
single_value · single_value_fixed · multi_value · multi_value_fixedfield__display__namestringThe display name of the Incident Type.
field__default__valuestringThe default value of the custom field.
field__field__optionsarrayThe options for the custom field. Can only be applied to fields with a type of multi_value or multi_value_fixed.
PAGERDUTY_CREATE_A_FIELD_OPTION_FOR_A_CUSTOM_FIELDCreate a field option for a custom field. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be app...4 params
Create a field option for a custom field. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be app...
Parameters* required
field_idstringThe ID of the field.
type_id_or_namestringThe ID or name of the Incident Type.
field__option__data__valuestringThe value of the Field Option for the Custom Field.
field__option__data__data__typestringThe data type of the Field Option for the Custom Field.
PAGERDUTY_CREATE_AND_MANAGE_CUSTOM_INCIDENT_FIELDSCreates a new custom field for incidents in PagerDuty. This endpoint allows you to define additional data points to be associated with incidents, enhancing incident management and reporting capabilities. Custom fields can be used to store various types of information such as e...
Creates a new custom field for incidents in PagerDuty. This endpoint allows you to define additional data points to be associated with incidents, enhancing incident management and reporting capabilities. Custom fields can be used to store various types of information such as e...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_AN_INCIDENT_TYPECreate a new incident type. Incident Types are a feature which will allow customers to categorize incidents, such as a security incident, a major incident, or a fraud incident. <!-- theme: warning --> > ### Early Access > This endpoint is in Early Access and may change at any...5 params
Create a new incident type. Incident Types are a feature which will allow customers to categorize incidents, such as a security incident, a major incident, or a fraud incident. <!-- theme: warning --> > ### Early Access > This endpoint is in Early Access and may change at any...
Parameters* required
incident__type__namestringThe name of the Incident Type. Usage of the suffix `_default` is prohibited. This cannot be changed once the incident type has been created.
incident__type__enabledbooleanWhether the Incident Type is enabled. Defaults to true if not provided.
incident__type__descriptionstringThe description of the Incident Type.
incident__type__parent__typestringThe parent type of the Incident Type. Either name or id of the parent type can be used.
incident__type__display__namestringThe display name of the Incident Type. Usage of the prefix `PD`, `PagerDuty`, `Default` is prohibited.
PAGERDUTY_CREATE_A_RULESETCreates a new Ruleset in PagerDuty for managing incident routing and notification rules. This endpoint allows you to define a named set of rules that determine how incidents are processed and directed to specific teams or users. It's particularly useful when setting up or modi...
Creates a new Ruleset in PagerDuty for managing incident routing and notification rules. This endpoint allows you to define a named set of rules that determine how incidents are processed and directed to specific teams or users. It's particularly useful when setting up or modi...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_A_TRIGGERCreate new Incident Workflow Trigger Scoped OAuth requires: `incident_workflows.write`
Create new Incident Workflow Trigger Scoped OAuth requires: `incident_workflows.write`
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_AUTOMATION_RUNNER_ENDPOINTCreates a new automation runner in the PagerDuty incident management system. This endpoint allows you to set up either a sidecar runner, which polls for invocations externally, or a runbook runner, which communicates directly with a runbook instance. Use this when you need to...1 params
Creates a new automation runner in the PagerDuty incident management system. This endpoint allows you to set up either a sidecar runner, which polls for invocations externally, or a runbook runner, which communicates directly with a runbook instance. Use this when you need to...
Parameters* required
runnerobjectRunner
PAGERDUTY_CREATE_BUSINESS_SERVICEThis endpoint creates a new Business Service in PagerDuty, which represents a specific service or application that can be monitored and managed within the incident management platform. It allows you to define essential properties of the service, including its name, description...4 params
This endpoint creates a new Business Service in PagerDuty, which represents a specific service or application that can be monitored and managed within the incident management platform. It allows you to define essential properties of the service, including its name, description...
Parameters* required
business__service__namestringThe name of the Business Service.
business__service__team__idstringThe Team ID
business__service__descriptionstringThe description of the Business Service.
business__service__point__of__contactstringThe owner of the Business Service.
PAGERDUTY_CREATE_ESCALATION_POLICYCreates a new escalation policy in PagerDuty, defining how incidents are escalated to different responders or teams. This endpoint allows you to set up a structured response plan for managing incidents, including escalation rules, targets, and associated services or teams. Use...
Creates a new escalation policy in PagerDuty, defining how incidents are escalated to different responders or teams. This endpoint allows you to set up a structured response plan for managing incidents, including escalation rules, targets, and associated services or teams. Use...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_EVENT_ORCHESTRATIONCreates a new Event Orchestration in PagerDuty, which defines how incoming events are processed and routed to appropriate services. This endpoint allows you to set up a configuration that manages the flow of events from various integrations, ensuring efficient incident handlin...18 params
Creates a new Event Orchestration in PagerDuty, which defines how incoming events are processed and routed to appropriate services. This endpoint allows you to set up a configuration that manages the flow of events from various integrations, ensuring efficient incident handlin...
Parameters* required
orchestration__idstringID of the Orchestration.
orchestration__namestringName of the Orchestration.
orchestration__selfstringThe API show URL at which the object is accessible
orchestration__routesintegerNumber of different Service Orchestration being routed to
orchestration__versionstringVersion of the Orchestration.
orchestration__team__idstringId
orchestration__team__selfstringThe API show URL at which the object is accessible
orchestration__team__typestringA string that determines the schema of the object
orchestration__created__atstringThe date the Orchestration was created at.
orchestration__descriptionstringA description of this Orchestration"s purpose.
orchestration__updated__atstringThe date the Orchestration was last updated.
orchestration__integrationsarrayIntegrations
orchestration__created__by__idstringId
orchestration__updated__by__idstringId
orchestration__created__by__selfstringThe API show URL at which the object is accessible
orchestration__created__by__typestringA string that determines the schema of the object
orchestration__updated__by__selfstringThe API show URL at which the object is accessible
orchestration__updated__by__typestringA string that determines the schema of the object
PAGERDUTY_CREATE_EVENT_RULE_IN_RULESETCreates a new Event Rule within a specified Ruleset in PagerDuty's incident management system. This endpoint allows you to define complex conditions for event matching and specify actions to be taken when an event meets those conditions. Use this to automate incident response,...1 params
Creates a new Event Rule within a specified Ruleset in PagerDuty's incident management system. This endpoint allows you to define complex conditions for event matching and specify actions to be taken when an event meets those conditions. Use this to automate incident response,...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_CREATE_EXTENSION_OBJECTCreates a new extension in PagerDuty, allowing for additional functionality or integrations to be added to your services. This endpoint is used to set up webhooks, custom integrations, or other specific features that enhance the capabilities of your PagerDuty account. The exte...
Creates a new extension in PagerDuty, allowing for additional functionality or integrations to be added to your services. This endpoint is used to set up webhooks, custom integrations, or other specific features that enhance the capabilities of your PagerDuty account. The exte...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_HANDOFF_NOTIFICATION_RULECreates a new on-call handoff notification rule for a specific user in PagerDuty. This endpoint allows you to set up automated notifications for when a user is about to start or end their on-call shift. It defines how and when the user should be notified about upcoming handoff...4 params
Creates a new on-call handoff notification rule for a specific user in PagerDuty. This endpoint allows you to set up automated notifications for when a user is about to start or end their on-call shift. It defines how and when the user should be notified about upcoming handoff...
Parameters* required
idstringThe ID of the resource.
oncall__handoff__notification__rule__idstringId
oncall__handoff__notification__rule__handoff__typestringThe type of handoff being created.one of
both · oncall · offcalldefault: bothoncall__handoff__notification__rule__notify__advance__in__minutesintegerThe delay before firing the rule, in minutes.
PAGERDUTY_CREATE_INCIDENT_FIELD_OPTIONCreates a new field option for a specific custom field in PagerDuty's incident management system. This endpoint allows you to add predefined options to custom fields, enhancing the ability to categorize and filter incidents with consistent, structured data. Use this when you n...1 params
Creates a new field option for a specific custom field in PagerDuty's incident management system. This endpoint allows you to add predefined options to custom fields, enhancing the ability to categorize and filter incidents with consistent, structured data. Use this when you n...
Parameters* required
field_idstringThe ID of the field.
PAGERDUTY_CREATE_INCIDENT_RECORDCreates a new incident in PagerDuty with specified details and assignments. Use this endpoint when an event requires immediate attention from on-call teams. It supports comprehensive incident documentation, including priority, urgency, and conference bridge information. The 'i...17 params
Creates a new incident in PagerDuty with specified details and assignments. Use this endpoint when an event requires immediate attention from on-call teams. It supports comprehensive incident documentation, including priority, urgency, and conference bridge information. The 'i...
Parameters* required
incident__typestringSpecifies the type of object being created. Always set to "incident" for incident creation. This field helps ensure API consistency and proper object handling. default: incident
incident__titlestringA clear, descriptive title for the incident that helps responders quickly understand the issue. Best Practice Format: "<System/Service> - <Problem> - <Impact>" Examples: - "Production Database - CPU Usage 95% - Customer Queries Delayed" - "Payment API - 500 Error Rate >5% - Orders Failing" - "Website - SSL Certificate Expiring - Security Risk" default: New Incident
incident__urgencystringDetermines the immediacy of notifications and escalations. Options: - high: Immediate notifications, aggressive escalation - low: Respect service"s notification rules, standard escalation Choose based on: - Business impact - Time sensitivity - Service criticality - Customer impact default: low
incident__body__typestringSpecifies the type of body contentdefault: Test
incident__assignmentsarrayList of users to assign to the incident. Maximum 10 assignees allowed. Important Notes: - Cannot be used with escalation_policy - Users must have access to the service - Assignments override default escalation - Order matters for primary/secondary
incident__service__idstringUnique identifier for the PagerDuty service. Found in service settings or via API. Example: "PSVC123"
incident__priority__idstringUnique identifier for the priority level. Example: "PRIO123"
incident__body__detailsstringComprehensive incident details in structured format. Recommended Structure: ``` CURRENT STATUS: [Brief description of current situation] IMPACT: - Business Impact: [Description] - User Impact: [Number of affected users/systems] - Revenue Impact: [If applicable] ACTIONS TAKEN: 1. [Action 1] 2. [Action 2] METRICS: - Error Rate: [Value] - Response Time: [Value] LINKS: - Dashboard: [URL] - Logs: [URL] - Runbook: [URL] ``` default: Incident details pending
incident__incident__keystringUnique identifier for deduplicating incidents within a service. Best Practice Format: "<source>-<type>-<identifier>-<timestamp>" Examples: - "datadog-cpu-alert-prod-db1-1640995200" - "cloudwatch-memory-warning-cache-1640995200" - "synthetic-api-failure-payments-1640995200" Notes: - Must be unique per service - Used to prevent duplicate incidents - Should be consistent and meaningful
incident__service__typestringObject type identifier. Always "service_reference" for service objects. one of
service_referencedefault: service_referenceincident__priority__typestringObject type for priority reference
incident__incident__type__idstringUnique identifier for incident type
incident__incident__type__namestringPredefined incident type categories. Used for reporting and analytics. one of
major_incident · security_incident · engineering_incident · customer_incidentdefault: engineering_incidentincident__incident__type__typestringObject type for incident type referencedefault: incident_type_reference
incident__conference__bridge__conference__urlstringWeb conference URL. Should be accessible to all responders. default: https://meet.example.com/incident
incident__conference__bridge__conference__typestringPlatform used for conference bridge. Helps responders prepare right tools. one of
zoom · meet · teams · webex · otherincident__conference__bridge__conference__numberstringPhone number with access sequence. Format: "+1-555-123-4567,,,,1234#" Commas (,) represent one-second pauses
PAGERDUTY_CREATE_INCIDENT_WORKFLOWThis endpoint creates a new Incident Workflow in PagerDuty, allowing users to define a series of automated steps to be executed during incident response. It enables the setup of complex, multi-step processes that can include actions like sending notifications, updating statuse...
This endpoint creates a new Incident Workflow in PagerDuty, allowing users to define a series of automated steps to be executed during incident response. It enables the setup of complex, multi-step processes that can include actions like sending notifications, updating statuse...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_INCIDENT_WORKFLOW_INSTANCECreates a new instance of an incident workflow for a specific incident in PagerDuty. This endpoint allows you to initiate a predefined workflow process for managing and resolving an ongoing incident. It links the workflow instance to a particular incident, enabling automated a...2 params
Creates a new instance of an incident workflow for a specific incident in PagerDuty. This endpoint allows you to initiate a predefined workflow process for managing and resolving an ongoing incident. It links the workflow instance to a particular incident, enabling automated a...
Parameters* required
idstringThe ID of the resource.
incident__workflow__instance__incident__typestringTypeone of
incident_referencePAGERDUTY_CREATE_INTEGRATION_FOR_ORCHESTRATIONCreates a new integration within an existing event orchestration in PagerDuty. This endpoint allows users to set up connections between PagerDuty and external systems or services, enabling automated event management and incident response. It should be used when adding a new in...2 params
Creates a new integration within an existing event orchestration in PagerDuty. This endpoint allows users to set up connections between PagerDuty and external systems or services, enabling automated event management and incident response. It should be used when adding a new in...
Parameters* required
idstringThe ID of an Event Orchestration.
integration__labelstringName of the Integration.
PAGERDUTY_CREATE_INTEGRATION_FOR_SERVICEThis endpoint creates a new integration for a specific PagerDuty service. It allows you to set up various types of integrations, including email-based and Events API v2 integrations. The primary use case is to establish new channels for incident creation and management within...1 params
This endpoint creates a new integration for a specific PagerDuty service. It allows you to set up various types of integrations, including email-based and Events API v2 integrations. The primary use case is to establish new channels for incident creation and management within...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_CREATE_MAINTENANCE_WINDOW_OBJECTCreates a new maintenance window in PagerDuty, allowing you to schedule periods of planned maintenance for specific services. During a maintenance window, incidents are not created for the affected services, preventing unnecessary alerts and notifications. This endpoint is use...
Creates a new maintenance window in PagerDuty, allowing you to schedule periods of planned maintenance for specific services. During a maintenance window, incidents are not created for the affected services, preventing unnecessary alerts and notifications. This endpoint is use...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_NEW_SCHEDULE_LAYERCreates a new on-call schedule in PagerDuty, defining rotation patterns for team members. This endpoint allows you to set up complex schedules with multiple layers, each having its own rotation pattern, user assignments, and time restrictions. Use it to establish new on-call r...1 params
Creates a new on-call schedule in PagerDuty, defining rotation patterns for team members. This endpoint allows you to set up complex schedules with multiple layers, each having its own rotation pattern, user assignments, and time restrictions. Use it to establish new on-call r...
Parameters* required
overflowbooleanAny on-call schedule entries that pass the date range bounds will be truncated at the bounds, unless the parameter `overflow=true` is passed. This parameter defaults to false. For instance, if your schedule is a rotation that changes daily at midnight UTC, and your date range is from `2011-06-01T10:00:00Z` to `2011-06-01T14:00:00Z`: - If you don"t pass the `overflow=true` parameter, you will get one schedule entry returned with a start of `2011-06-01T10:00:00Z` and end of `2011-06-01T14:00:00Z`. - If you do pass the `overflow=true` parameter, you will get one schedule entry returned with a start of `2011-06-01T00:00:00Z` and end of `2011-06-02T00:00:00Z`. default: false
PAGERDUTY_CREATE_NEW_SERVICECreates a new service in PagerDuty, which is a key component for managing incidents and alerts. This endpoint allows you to set up a service with various configurations including escalation policies, incident urgency rules, support hours, and alert grouping parameters. Use thi...
Creates a new service in PagerDuty, which is a key component for managing incidents and alerts. This endpoint allows you to set up a service with various configurations including escalation policies, incident urgency rules, support hours, and alert grouping parameters. Use thi...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_NEW_TAG_IN_SYSTEMCreates a new tag in PagerDuty for labeling and categorizing entities. This endpoint allows users to add a custom label to their PagerDuty account, which can be used to organize and filter various resources such as incidents, services, or teams. The created tag can be subseque...
Creates a new tag in PagerDuty for labeling and categorizing entities. This endpoint allows users to add a custom label to their PagerDuty account, which can be used to organize and filter various resources such as incidents, services, or teams. The created tag can be subseque...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILSCreates a new team within your PagerDuty account. This endpoint allows you to establish a group of users with shared responsibilities, often used for organizing incident management and on-call schedules. Use this when setting up a new department, project team, or any other gro...
Creates a new team within your PagerDuty account. This endpoint allows you to establish a group of users with shared responsibilities, often used for organizing incident management and on-call schedules. Use this when setting up a new department, project team, or any other gro...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_NEW_WEBHOOK_SUBSCRIPTIONCreates a new webhook subscription in PagerDuty to receive specific event notifications. This endpoint allows users to set up automated notifications for various incident-related events, such as triggers, acknowledgments, and resolutions. The webhook can be configured to filte...13 params
Creates a new webhook subscription in PagerDuty to receive specific event notifications. This endpoint allows users to set up automated notifications for various incident-related events, such as triggers, acknowledgments, and resolutions. The webhook can be configured to filte...
Parameters* required
webhook__subscription__idstringId
webhook__subscription__typestringThe type indicating the schema of the object.one of
webhook_subscriptiondefault: webhook_subscriptionwebhook__subscription__activebooleanDetermines whether this subscription will produce webhook events.default: true
webhook__subscription__eventsarrayThe set of outbound event types the webhook will receive.
webhook__subscription__filter__idstringThe id of the object being used as the filter. This field is required for all filter types except account_reference.
webhook__subscription__descriptionstringA short description of the webhook subscription.
webhook__subscription__filter__typestringThe type of object being used as the filter.one of
account_reference · service_reference · team_referencewebhook__subscription__delivery__method__idstringId
webhook__subscription__delivery__method__urlstringThe destination URL for webhook delivery.
webhook__subscription__delivery__method__typestringIndicates the type of the delivery method.one of
http_delivery_methoddefault: http_delivery_methodwebhook__subscription__delivery__method__secretstringThe secret used to sign webhook payloads. Only provided on the initial create response.
webhook__subscription__delivery__method__custom__headersarrayOptional headers to be set on this webhook subscription when sent. The header values are redacted in GET requests, but are not redacted on the webhook when delivered to the webhook"s endpoint.
webhook__subscription__delivery__method__temporarily__disabledbooleanWhether or not this webhook subscription is temporarily disabled. Becomes `true` if the delivery method URL is repeatedly rejected by the server.
PAGERDUTY_CREATE_OR_UPDATE_STATUS_PAGE_POSTCreates a new post on a specified PagerDuty Status Page. This endpoint allows you to publish information about incidents or scheduled maintenance, including details such as the post type, timing, and associated updates. Use this to communicate service status, planned downtime,...9 params
Creates a new post on a specified PagerDuty Status Page. This endpoint allows you to publish information about incidents or scheduled maintenance, including details such as the post type, timing, and associated updates. Use this to communicate service status, planned downtime,...
Parameters* required
idstringThe ID of the resource.
post__typestringThe type of the object returned by the API - in this case, a Status Page Post. one of
status_page_postpost__titlestringThe title given to a Post.
post__updatesarrayPost Updates to be associated with a Post
post__ends__atstringThe date and time the Post intent is concluded - only for maintenance post type.
post__post__typestringThe type of the Post.one of
incident · maintenancepost__starts__atstringThe date and time the Post intent becomes effective - only for maintenance post type.
post__status__page__idstringStatus page unique identifier
post__status__page__typestringA string that determines the schema of the object.
PAGERDUTY_CREATE_OR_UPDATE_STATUS_PAGE_POSTMORTEMCreates or updates a postmortem for a specific status page post in PagerDuty. This endpoint allows you to add detailed analysis and insights about an incident after its resolution. The postmortem can include rich-text content and offers the option to notify subscribers. Use th...7 params
Creates or updates a postmortem for a specific status page post in PagerDuty. This endpoint allows you to add detailed analysis and insights about an incident after its resolution. The postmortem can include rich-text content and offers the option to notify subscribers. Use th...
Parameters* required
idstringThe ID of the resource.
post_idstringThe ID of the Status Page Post.
postmortem__typestringThe type of the object returned by the API - in this case, a Status Page Post Postmortem. one of
status_page_post_postmortemdefault: status_page_post_postmortempostmortem__messagestringThe message of the Postmortem (supports Rich-Text).
postmortem__post__idstringStatus page post unique identifier
postmortem__post__typestringA string that determines the schema of the object.
postmortem__notify__subscribersbooleanWhether or not subscribers of the Status Page should be notified about the Postmortem.
PAGERDUTY_CREATE_RESPONSE_PLAY_FOR_INCIDENTSCreates a new Response Play in PagerDuty, which is a predefined set of actions to be executed in response to an incident. This endpoint allows you to configure automated responses, including adding subscribers, assigning responders, setting up conference details, and defining...
Creates a new Response Play in PagerDuty, which is a predefined set of actions to be executed in response to an incident. This endpoint allows you to configure automated responses, including adding subscribers, assigning responders, setting up conference details, and defining...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATIONCreates one or more overrides for a specific schedule in PagerDuty. This endpoint allows you to temporarily modify the on-call schedule by assigning different users for specific time periods. It's useful for handling planned absences, shift swaps, or special coverage requireme...2 params
Creates one or more overrides for a specific schedule in PagerDuty. This endpoint allows you to temporarily modify the on-call schedule by assigning different users for specific time periods. It's useful for handling planned absences, shift swaps, or special coverage requireme...
Parameters* required
idstringThe ID of the resource.
overridesarrayOverrides
PAGERDUTY_CREATE_SERVICE_EVENT_RULECreates a new event rule for a specific service in PagerDuty. This endpoint allows you to define complex conditions and actions for handling incoming events, enabling automated incident management and alert routing. Use this when you need to set up custom logic for processing...1 params
Creates a new event rule for a specific service in PagerDuty. This endpoint allows you to define complex conditions and actions for handling incoming events, enabling automated incident management and alert routing. Use this when you need to set up custom logic for processing...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_CREATE_STATUS_PAGE_SUBSCRIPTIONCreates a new subscription for a PagerDuty status page. This endpoint allows users to set up notifications for specific status pages or components within those pages. It's used to keep subscribers informed about updates, incidents, or changes to the monitored services. The sub...8 params
Creates a new subscription for a PagerDuty status page. This endpoint allows users to set up notifications for specific status pages or components within those pages. It's used to keep subscribers informed about updates, incidents, or changes to the monitored services. The sub...
Parameters* required
idstringThe ID of the resource.
subscription__typestringA string that determines the schema of the object.
subscription__channelstringThe channel of the Subscription.one of
webhook · emailsubscription__contactstringThe subscriber"s contact - email address or webhook URL.
subscription__status__page__idstringThe id of the status page.
subscription__status__page__typestringA string that determines the schema of the object.
subscription__subscribable__object__idstringThe ID of the subscribed entity for a given subscription.
subscription__subscribable__object__typestringThe type of the subscribed entity for a given subscription.one of
status_page · status_page_service · status_page_postPAGERDUTY_CREATE_STATUS_UPDATE_TEMPLATECreates a new template in PagerDuty for standardized status updates. This endpoint allows users to define customizable templates for various notification types, including emails and short messages. It's primarily used to streamline communication during incident management by p...6 params
Creates a new template in PagerDuty for standardized status updates. This endpoint allows users to define customizable templates for various notification types, including emails and short messages. It's primarily used to streamline communication during incident management by p...
Parameters* required
template__namestringThe name of the template
template__descriptionstringDescription of the template
template__template__typestringThe type of template (`status_update` is the only supported template at this time) one of
status_updatetemplate__templated__fields__messagestringThe short-message of the template (SMS, Push notification, Slack, etc)
template__templated__fields__email__bodystringThe HTML body of the e-mail message
template__templated__fields__email__subjectstringThe subject of the e-mail
PAGERDUTY_CREATE_USER_NOTIFICATION_RULECreates a new notification rule for a specific user in PagerDuty. This endpoint allows you to define how and when a user should be notified about assigned incidents. You can specify the delay before notification, the method of contact, and the urgency level of incidents that t...1 params
Creates a new notification rule for a specific user in PagerDuty. This endpoint allows you to define how and when a user should be notified about assigned incidents. You can specify the delay before notification, the method of contact, and the urgency level of incidents that t...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_CREATE_USER_OBJECTCreates a new user in the PagerDuty system with the specified attributes. This endpoint should be used when onboarding new team members or adding users to your PagerDuty account. It allows you to set up essential user information, including name, email, role, and time zone pre...
Creates a new user in the PagerDuty system with the specified attributes. This endpoint should be used when onboarding new team members or adding users to your PagerDuty account. It allows you to set up essential user information, including name, email, role, and time zone pre...
No parameter schema in public metadata yet.
PAGERDUTY_CREATE_USER_STATUS_UPDATE_NOTIFICATION_RULECreates a new status update notification rule for a specific user in PagerDuty. This endpoint allows you to define how a user will be notified about incident status updates. It's used to customize notification preferences for individual users, ensuring they receive timely upda...1 params
Creates a new status update notification rule for a specific user in PagerDuty. This endpoint allows you to define how a user will be notified about incident status updates. It's used to customize notification preferences for individual users, ensuring they receive timely upda...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_CREATE_WORKFLOW_INTEGRATION_CONNECTIONCreate a new Workflow Integration Connection. Scoped OAuth requires: `workflow_integrations:connections.write`13 params
Create a new Workflow Integration Connection. Scoped OAuth requires: `workflow_integrations:connections.write`
Parameters* required
idstringThe ID of the connection
namestringThe name given to the connection
typestringThe type of the connection
teamsarrayThe teams whose managers are allowed to use or edit this connection
scopesarrayScopes
is_defaultbooleanWhether or not this connection is the default connection for this integration
external_idstringThe ID of the external system that this connection is used to connect to
service_urlstringThe URL of the service that this connection is associated with
integration_idstringThe integration ID that this connection is associated with
external_id_labelstringThe label of the external system that this connection is used to connect to
health__is__healthybooleanWhether or not the connection is healthy
health__health__messagestringA message describing the health of the connection
health__last__checked__atstringThe timestamp of the last health check
PAGERDUTY_DELETE_ACCOUNT_SUBSCRIPTION_BY_IDDeletes the account subscription associated with a specific business service in PagerDuty. This endpoint is used to terminate the subscription or billing relationship between a business service and the account. It should be used when you need to discontinue the subscription fo...1 params
Deletes the account subscription associated with a specific business service in PagerDuty. This endpoint is used to terminate the subscription or billing relationship between a business service and the account. It should be used when you need to discontinue the subscription fo...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_A_CUSTOM_FIELD_FOR_AN_INCIDENT_TYPEDelete a custom field for an incident type. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be a...2 params
Delete a custom field for an incident type. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be a...
Parameters* required
field_idstringThe ID of the field.
type_id_or_namestringThe ID or name of the Incident Type.
PAGERDUTY_DELETE_ADDON_BY_IDDeletes a specific add-on from the PagerDuty account using its unique identifier. This endpoint should be used when you want to remove an integration or extension that is no longer needed or active in your PagerDuty setup. It's important to note that this action is irreversibl...1 params
Deletes a specific add-on from the PagerDuty account using its unique identifier. This endpoint should be used when you want to remove an integration or extension that is no longer needed or active in your PagerDuty setup. It's important to note that this action is irreversibl...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_A_FIELD_OPTION_FOR_A_CUSTOM_FIELDDelete a field option for a custom field. <!-- theme: warning --> > ### Early Access > This endpoint is in Early Access and may change at any time. You must pass in the X-EARLY-ACCESS header to access it. Scoped OAuth requires: `custom_fields.write`3 params
Delete a field option for a custom field. <!-- theme: warning --> > ### Early Access > This endpoint is in Early Access and may change at any time. You must pass in the X-EARLY-ACCESS header to access it. Scoped OAuth requires: `custom_fields.write`
Parameters* required
field_idstringThe ID of the field.
field_option_idstringThe ID of the field option.
type_id_or_namestringThe ID or name of the Incident Type.
PAGERDUTY_DELETE_ALERT_GROUPING_SETTINGThis endpoint allows you to delete specific alert grouping settings in PagerDuty. It is used to remove outdated or unnecessary configurations that determine how alerts are grouped into incidents. The deletion is permanent and cannot be undone, so it should be used with caution...1 params
This endpoint allows you to delete specific alert grouping settings in PagerDuty. It is used to remove outdated or unnecessary configurations that determine how alerts are grouped into incidents. The deletion is permanent and cannot be undone, so it should be used with caution...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_ALL_OAUTH_DELEGATIONSDelete all OAuth delegations as per provided query parameters. An OAuth delegation represents an instance of a user or account's authorization to an app (via OAuth) to access their PagerDuty account. Common apps include the PagerDuty mobile app, Slack, Microsoft Teams, and thi...2 params
Delete all OAuth delegations as per provided query parameters. An OAuth delegation represents an instance of a user or account's authorization to an app (via OAuth) to access their PagerDuty account. Common apps include the PagerDuty mobile app, Slack, Microsoft Teams, and thi...
Parameters* required
typestringThe type of OAuth delegations this request should target.one of
mobileuser_idstringThe ID of the user for whom this request is applicable.
PAGERDUTY_DELETE_AUTOMATION_ACTION_BY_IDDeletes a specific Automation Action from the PagerDuty system. This endpoint is used to permanently remove an Automation Action, which includes any associated scripts or jobs in Runbook Automation. It should be used when an Automation Action is no longer needed or has become...1 params
Deletes a specific Automation Action from the PagerDuty system. This endpoint is used to permanently remove an Automation Action, which includes any associated scripts or jobs in Runbook Automation. It should be used when an Automation Action is no longer needed or has become...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_AUTOMATION_ACTION_SERVICE_BY_IDThis endpoint removes a specific automation action from a particular service in PagerDuty. It is used to disassociate an automated workflow or action from a service, effectively stopping that action from being triggered for incidents related to the specified service. This oper...2 params
This endpoint removes a specific automation action from a particular service in PagerDuty. It is used to disassociate an automated workflow or action from a service, effectively stopping that action from being triggered for incidents related to the specified service. This oper...
Parameters* required
idstringThe ID of the resource.
service_idstringThe service ID
PAGERDUTY_DELETE_AUTOMATION_ACTIONS_RUNNER_BY_IDDeletes a specific automation runner from the PagerDuty system. This endpoint is used to permanently remove an automation runner, which is responsible for executing automated tasks and workflows. It should be used when an automation runner is no longer needed or needs to be re...1 params
Deletes a specific automation runner from the PagerDuty system. This endpoint is used to permanently remove an automation runner, which is responsible for executing automated tasks and workflows. It should be used when an automation runner is no longer needed or needs to be re...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_BUSINESS_SERVICE_BY_IDDeletes a specific business service from the PagerDuty system. This endpoint should be used when you want to permanently remove a business service that is no longer needed or relevant to your organization's incident management structure. It's important to note that this action...1 params
Deletes a specific business service from the PagerDuty system. This endpoint should be used when you want to permanently remove a business service that is no longer needed or relevant to your organization's incident management structure. It's important to note that this action...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_BUSINESS_SERVICE_PRIORITY_THRESHOLDSDeletes all priority thresholds for business services in the PagerDuty account. This endpoint is used to remove the configured priority settings that determine how incidents are escalated based on their urgency for business services. It should be used when you want to reset or...
Deletes all priority thresholds for business services in the PagerDuty account. This endpoint is used to remove the configured priority settings that determine how incidents are escalated based on their urgency for business services. It should be used when you want to reset or...
No parameter schema in public metadata yet.
PAGERDUTY_DELETE_CACHE_VARIABLE_FOR_EVENTDeletes a specific cache variable associated with an event orchestration in PagerDuty. This endpoint is used to remove temporary data storage that was previously set up for use in event orchestration workflows. It should be used when you need to clean up or remove outdated cac...2 params
Deletes a specific cache variable associated with an event orchestration in PagerDuty. This endpoint is used to remove temporary data storage that was previously set up for use in event orchestration workflows. It should be used when you need to clean up or remove outdated cac...
Parameters* required
idstringThe ID of an Event Orchestration.
cache_variable_idstringThe ID of a Cache Variable.
PAGERDUTY_DELETE_CACHE_VARIABLE_FROM_SERVICEThis endpoint deletes a specific cache variable associated with a service in PagerDuty's event orchestration system. It is used to remove temporary data that is no longer needed, helping to maintain system efficiency. The endpoint should be used when you want to permanently re...2 params
This endpoint deletes a specific cache variable associated with a service in PagerDuty's event orchestration system. It is used to remove temporary data that is no longer needed, helping to maintain system efficiency. The endpoint should be used when you want to permanently re...
Parameters* required
service_idstringThe service ID
cache_variable_idstringThe ID of a Cache Variable.
PAGERDUTY_DELETE_CUSTOM_FIELD_BY_FIELD_IDDeletes a specific custom field from incidents in PagerDuty. This endpoint allows users to remove a custom field that is no longer needed or relevant for incident management. It should be used when you want to permanently delete a custom field from all incidents, both existing...1 params
Deletes a specific custom field from incidents in PagerDuty. This endpoint allows users to remove a custom field that is no longer needed or relevant for incident management. It should be used when you want to permanently delete a custom field from all incidents, both existing...
Parameters* required
field_idstringThe ID of the field.
PAGERDUTY_DELETE_ESCALATION_POLICY_BY_IDPermanently removes a specific escalation policy from the PagerDuty system. This endpoint should be used when an escalation policy is no longer needed or has become obsolete. Once deleted, the escalation policy cannot be recovered, and any services or incidents associated with...1 params
Permanently removes a specific escalation policy from the PagerDuty system. This endpoint should be used when an escalation policy is no longer needed or has become obsolete. Once deleted, the escalation policy cannot be recovered, and any services or incidents associated with...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_EVENT_BY_IDDeletes a specific Event Orchestration from the PagerDuty system. This endpoint should be used when you want to permanently remove an Event Orchestration configuration, including all its associated rules and routing logic. It's important to note that this action is irreversibl...1 params
Deletes a specific Event Orchestration from the PagerDuty system. This endpoint should be used when you want to permanently remove an Event Orchestration configuration, including all its associated rules and routing logic. It's important to note that this action is irreversibl...
Parameters* required
idstringThe ID of an Event Orchestration.
PAGERDUTY_DELETE_EXTENSION_BY_IDDeletes a specific extension from the PagerDuty service. This endpoint should be used when you want to remove an additional feature or integration that has been previously added to your PagerDuty account. It's particularly useful for cleaning up obsolete integrations or disabl...1 params
Deletes a specific extension from the PagerDuty service. This endpoint should be used when you want to remove an additional feature or integration that has been previously added to your PagerDuty account. It's particularly useful for cleaning up obsolete integrations or disabl...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_FIELD_OPTIONThis endpoint deletes a specific field option from a custom field in PagerDuty's incident management system. It allows you to remove predefined options that are no longer needed or relevant for incident categorization or data collection. Use this endpoint when you want to upda...2 params
This endpoint deletes a specific field option from a custom field in PagerDuty's incident management system. It allows you to remove predefined options that are no longer needed or relevant for incident categorization or data collection. Use this endpoint when you want to upda...
Parameters* required
field_idstringThe ID of the field.
field_option_idstringThe ID of the field option.
PAGERDUTY_DELETE_INCIDENT_WORKFLOW_BY_IDDeletes a specific incident workflow from the PagerDuty system. This endpoint should be used when you want to permanently remove a customized sequence of automated actions and triggers associated with incident management. It's important to note that this action is irreversible...1 params
Deletes a specific incident workflow from the PagerDuty system. This endpoint should be used when you want to permanently remove a customized sequence of automated actions and triggers associated with incident management. It's important to note that this action is irreversible...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_INCIDENT_WORKFLOW_TRIGGER_BY_IDDeletes a specific trigger associated with an incident workflow in PagerDuty. This endpoint is used to remove an automated trigger that initiates a predefined workflow in response to incidents. It should be used when you need to modify your incident response automation by remo...1 params
Deletes a specific trigger associated with an incident workflow in PagerDuty. This endpoint is used to remove an automated trigger that initiates a predefined workflow in response to incidents. It should be used when you need to modify your incident response automation by remo...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_INCIDENT_WORKFLOW_TRIGGER_SERVICEThis endpoint removes a specific service from a trigger within an incident workflow in PagerDuty. It is used to modify the configuration of an existing incident workflow by disassociating a service from a particular trigger. This action is useful when you need to update the au...2 params
This endpoint removes a specific service from a trigger within an incident workflow in PagerDuty. It is used to modify the configuration of an existing incident workflow by disassociating a service from a particular trigger. This action is useful when you need to update the au...
Parameters* required
service_idstringIdentifier for the Service
trigger_idstringIdentifier for the Trigger
PAGERDUTY_DELETE_INTEGRATION_FROM_EVENT_ORCHESTRATIONRemoves a specific integration from an event orchestration in PagerDuty. This endpoint is used to disconnect a particular tool or service from the event orchestration setup, effectively stopping it from triggering or modifying incidents within that orchestration. It's particul...2 params
Removes a specific integration from an event orchestration in PagerDuty. This endpoint is used to disconnect a particular tool or service from the event orchestration setup, effectively stopping it from triggering or modifying incidents within that orchestration. It's particul...
Parameters* required
idstringThe ID of an Event Orchestration.
integration_idstringThe ID of an Integration.
PAGERDUTY_DELETE_MAINTENANCE_WINDOW_BY_IDDeletes a specific maintenance window in PagerDuty's incident management system. This endpoint is used to permanently remove a scheduled maintenance window, effectively re-enabling any services and integrations that were temporarily disabled during the maintenance period. It s...1 params
Deletes a specific maintenance window in PagerDuty's incident management system. This endpoint is used to permanently remove a scheduled maintenance window, effectively re-enabling any services and integrations that were temporarily disabled during the maintenance period. It s...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_ONCALL_HANDOFF_NOTIFICATION_RULEThis endpoint deletes a specific on-call handoff notification rule for a given user in PagerDuty. It is used to remove custom notification settings for when on-call responsibilities are transferred between team members. This operation is permanent and cannot be undone, so it s...2 params
This endpoint deletes a specific on-call handoff notification rule for a given user in PagerDuty. It is used to remove custom notification settings for when on-call responsibilities are transferred between team members. This operation is permanent and cannot be undone, so it s...
Parameters* required
idstringThe ID of the resource.
oncall_handoff_notification_rule_idstringThe oncall handoff notification rule ID on the user.
PAGERDUTY_DELETE_POST_FROM_STATUS_PAGEThis endpoint deletes a specific post from a PagerDuty status page. It is used to remove outdated or irrelevant information from a status page, helping to maintain clear and accurate communication with users about service status. The operation is irreversible, so it should be...2 params
This endpoint deletes a specific post from a PagerDuty status page. It is used to remove outdated or irrelevant information from a status page, helping to maintain clear and accurate communication with users about service status. The operation is irreversible, so it should be...
Parameters* required
idstringThe ID of the resource.
post_idstringThe ID of the Status Page Post.
PAGERDUTY_DELETE_POST_UPDATE_BY_IDThis endpoint deletes a specific post update from a status page post in PagerDuty. It allows users to remove outdated or incorrect information from a status page, ensuring that only relevant and accurate updates are displayed. The endpoint should be used when an organization n...3 params
This endpoint deletes a specific post update from a status page post in PagerDuty. It allows users to remove outdated or incorrect information from a status page, ensuring that only relevant and accurate updates are displayed. The endpoint should be used when an organization n...
Parameters* required
idstringThe ID of the resource.
post_idstringThe ID of the Status Page Post.
post_update_idstringThe ID of the Status Page Post Update.
PAGERDUTY_DELETE_RESPONSE_PLAYDeletes a specific Response Play from the PagerDuty system. This endpoint should be used when you need to remove an outdated or unnecessary Response Play from your incident management workflow. It permanently eliminates the predefined sequence of actions associated with the sp...1 params
Deletes a specific Response Play from the PagerDuty system. This endpoint should be used when you need to remove an outdated or unnecessary Response Play from your incident management workflow. It permanently eliminates the predefined sequence of actions associated with the sp...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_RULE_FROM_RULESET_BY_IDDeletes a specific rule from a ruleset in PagerDuty's incident management platform. This endpoint allows users to remove individual event rules, providing flexibility in managing and updating rulesets. It should be used when you need to eliminate an outdated, unnecessary, or i...2 params
Deletes a specific rule from a ruleset in PagerDuty's incident management platform. This endpoint allows users to remove individual event rules, providing flexibility in managing and updating rulesets. It should be used when you need to eliminate an outdated, unnecessary, or i...
Parameters* required
idstringThe ID of the resource.
rule_idstringThe id of the Event Rule to retrieve.
PAGERDUTY_DELETE_RULESET_BY_IDDeletes a specific ruleset from the PagerDuty system based on the provided ID. This endpoint should be used when you need to remove an existing ruleset, which may be necessary during incident management reconfiguration or when cleaning up obsolete rulesets. The deletion is per...1 params
Deletes a specific ruleset from the PagerDuty system based on the provided ID. This endpoint should be used when you need to remove an existing ruleset, which may be necessary during incident management reconfiguration or when cleaning up obsolete rulesets. The deletion is per...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_RUNNER_TEAM_ASSOCIATIONThis endpoint removes a team's association from a specific Automation Action runner in PagerDuty. It is used to revoke a team's access to execute or manage tasks on a particular runner. The operation is permanent and should be used when you no longer want a team to have access...2 params
This endpoint removes a team's association from a specific Automation Action runner in PagerDuty. It is used to revoke a team's access to execute or manage tasks on a particular runner. The operation is permanent and should be used when you no longer want a team to have access...
Parameters* required
idstringThe ID of the resource.
team_idstringThe team ID
PAGERDUTY_DELETE_SCHEDULE_BY_IDThe DeleteSchedule endpoint removes a specific schedule from the PagerDuty system. It is used to delete outdated or unnecessary on-call schedules, helping to maintain an organized and efficient incident management workflow. This operation is permanent and cannot be undone, so...1 params
The DeleteSchedule endpoint removes a specific schedule from the PagerDuty system. It is used to delete outdated or unnecessary on-call schedules, helping to maintain an organized and efficient incident management workflow. This operation is permanent and cannot be undone, so...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_SCHEDULE_OVERRIDE_BY_IDThis endpoint deletes a specific override from a PagerDuty schedule. It allows users to remove temporary changes made to the regular schedule, reverting it back to its original state. This operation is useful for canceling previously set overrides that are no longer needed, su...2 params
This endpoint deletes a specific override from a PagerDuty schedule. It allows users to remove temporary changes made to the regular schedule, reverting it back to its original state. This operation is useful for canceling previously set overrides that are no longer needed, su...
Parameters* required
idstringThe ID of the resource.
override_idstringThe override ID on the schedule.
PAGERDUTY_DELETE_SERVICE_BY_IDDeletes a specific service from the PagerDuty account. This endpoint should be used when you need to permanently remove a service that is no longer required or active. It's important to note that this operation is irreversible and will delete all associated incidents, alerts,...1 params
Deletes a specific service from the PagerDuty account. This endpoint should be used when you need to permanently remove a service that is no longer required or active. It's important to note that this operation is irreversible and will delete all associated incidents, alerts,...
Parameters* required
idstringThe ID of the resource.
PAGERDUTY_DELETE_SERVICE_RULE_BY_IDDeletes a specific rule from a PagerDuty service. This endpoint is used to permanently remove a rule that defines conditions for incident creation or automation within a particular service. It should be used when you need to eliminate an outdated, incorrect, or no longer neede...2 params
Deletes a specific rule from a PagerDuty service. This endpoint is used to permanently remove a rule that defines conditions for incident creation or automation within a particular service. It should be used when you need to eliminate an outdated, incorrect, or no longer neede...
Parameters* required
idstringThe ID of the resource.
rule_idstringThe id of the Event Rule to retrieve.
PAGERDUTY_DELETE_STATUS_PAGE_POSTMORTEMThis endpoint allows you to delete a postmortem associated with a specific post on a PagerDuty status page. It is used to remove the detailed analysis and lessons learned from an incident after it has been resolved and documented. This action is permanent and should be used wi...2 params
This endpoint allows you to delete a postmortem associated with a specific post on a PagerDuty status page. It is used to remove the detailed analysis and lessons learned from an incident after it has been resolved and documented. This action is permanent and should be used wi...
Parameters* required
idstringThe ID of the resource.
post_idstringThe ID of the Status Page Post.
PAGERDUTY_DELETE_STATUS_UPDATE_NOTIFICATION_RULEDeletes a specific status update notification rule associated with a user in the PagerDuty system. This endpoint allows administrators or users with appropriate permissions to remove custom notification rules for status updates, helping to manage and streamline the user's noti...2 params
Deletes a specific status update notification rule associated with a user in the PagerDuty system. This endpoint allows administrators or users with appropriate permissions to remove custom notification rules for status updates, helping to manage and streamline the user's noti...
Parameters* required
idstringThe ID of the resource.
status_update_notification_rule_idstringThe status update notification rule ID on the user.
PagerDuty's official MCP Server
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.
Embedded MCP Apps (Developer Experience)
Interactive React UIs for PagerDuty incident management, embedded directly in the Python MCP server for seamless IDE integration. Manage your full incident lifecycle without leaving your IDE.
Available Apps:
1. Incident Command Center 🚨
Full incident lifecycle management from your IDE:
- Real-time incident feed with auto-refresh
- Deep incident details: timeline, notes, alerts, changes
- Quick actions: acknowledge, resolve, escalate
- AI-powered similar incident detection
- Alert inspection with raw data
Usage in VS Code: Ask Claude: Show me the incident command center
2. On-Call Manager 📅
Schedule management with override CRUD and coverage wizards:
- View current on-call rotations across schedules
- Create, edit, and delete schedule overrides
- Escalation policy management with modal-based UI
Usage in VS Code: Ask Claude: Show me the on-call manager
3. On-Call Compensation Report 💰
Per-user on-call metrics with compliance tracking:
- Hours worked, incident counts, interruption rates
- Business hours vs. off-hours breakdown
- Compliance status with EU Working Time Directive limits
- Fairness/equity scoring across responders
- CSV export
Usage in VS Code: Ask Claude: Show me the oncall compensation report
4. Service Dependency Graph 🕸️
Interactive graph of service relationships and dependencies:
- Directed graph visualization
- Impact sidebar showing upstream/downstream services
Usage in VS Code: Ask Claude: Show me the service dependency graph
5. Onboarding Wizard 🧙
Step-by-step PagerDuty account setup:
- Team creation and user onboarding
- Schedule setup with timezone support
- Escalation policy and service configuration
- AIOps / alert grouping configuration
- Incident workflow setup
Usage in VS Code: Ask Claude: Open the onboarding wizard
Architecture:
- ✅ Native VS Code integration (MCP resources)
- ✅ Single process, no HTTP server management
- ✅ Direct access to all PagerDuty MCP tools
- ✅ Simple deployment:
uv run pagerduty-mcp
See mcp-apps/README.md for development instructions and customization.
Prerequisites
-
asdf-vm installed.
-
uv installed globally.
-
A PagerDuty User API Token. To obtain a PagerDuty User API Token, follow these steps:
- Navigate to User Settings. Click on your user profile icon, then select My Profile and then User Settings.
For Freemium accounts, the permissions for generating User API tokens are limited to the user role as defined here.
- In your user settings, locate the API Access section.
- Click the Create API User Token button and follow the prompts to generate a new token.
- Copy the generated token and store it securely. You will need this token to configure the MCP server.
Use of the PagerDuty User API Token is subject to the PagerDuty Developer Agreement.
- Navigate to User Settings. Click on your user profile icon, then select My Profile and then User Settings.
Using with MCP Clients
Cursor Integration
You can configure this MCP server directly within Cursor's settings.json file, by following these steps:
-
Open Cursor settings (Cursor Settings > Tools > Add MCP, or
Cmd+,on Mac, orCtrl+,on Windows/Linux). -
Add the following configuration:
{ "mcpServers": { "pagerduty-mcp": { "type": "stdio", "command": "uvx", "args": [ "pagerduty-mcp", "--enable-write-tools" // This flag enables write operations on the MCP Server enabling you to creating incidents, schedule overrides and much more ], "env": { "PAGERDUTY_USER_API_KEY": "${input:pagerduty-api-key}" } } } }
VS Code Integration
You can configure this MCP server directly within Visual Studio Code's settings.json file, allowing VS Code to manage the server lifecycle.
-
Open VS Code settings (File > Preferences > Settings, or
Cmd+,on Mac, orCtrl+,on Windows/Linux). -
Search for "mcp" and ensure "Mcp: Enabled" is checked under Features > Chat.
-
Click "Edit in settings.json" under "Mcp > Discovery: Servers".
-
Add the following configuration:
{ "mcp": { "inputs": [ { "type": "promptString", "id": "pagerduty-api-key", "description": "PagerDuty API Key", "password": true } ], "servers": { "pagerduty-mcp": { "type": "stdio", "command": "uvx", "args": [ "pagerduty-mcp", "--enable-write-tools" // This flag enables write operations on the MCP Server enabling you to creating incidents, schedule overrides and much more ], "env": { "PAGERDUTY_USER_API_KEY": "${input:pagerduty-api-key}", "PAGERDUTY_API_HOST": "https://api.pagerduty.com" // If your PagerDuty account is located in EU update your API host to https://api.eu.pagerduty.com } } } } }
Trying it in VS Code Chat (Agent)
- Ensure MCP is enabled in VS Code settings (Features > Chat > "Mcp: Enabled").
- Configure the server as described above.
- Open the Chat view in VS Code (
View>Chat). - Make sure
Agentmode is selected. In the Chat view, you can enable or disable specific tools by clicking the 🛠️ icon. - Enter a command such as
Show me the latest incidentorList my event orchestrationsto interact with your PagerDuty account through the MCP server. - You can start, stop, and manage your MCP servers using the command palette (
Cmd+Shift+P/Ctrl+Shift+P) and searching forMCP: List Servers. Ensure the server is running before sending commands. You can also try to restart the server if you encounter any issues.
Claude Desktop Integration
You can configure this MCP server to work with Claude Desktop by adding it to Claude's configuration file.
-
Locate your Claude Desktop configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
-
Create or edit the configuration file and add the following configuration:
{ "mcpServers": { "pagerduty-mcp": { "command": "uvx", "args": [ "pagerduty-mcp", "--enable-write-tools" ], "env": { "PAGERDUTY_USER_API_KEY": "your-pagerduty-api-key-here", "PAGERDUTY_API_HOST": "https://api.pagerduty.com" } } } } -
Replace the placeholder values:
- Replace
/path/to/your/mcp-server-directorywith the full path to the directory where you cloned the MCP server (e.g.,/Users/yourname/code/pagerduty-mcp) - Replace
your-pagerduty-api-key-herewith your actual PagerDuty User API Token - If your PagerDuty account is located in the EU, update the API host to
https://api.eu.pagerduty.com
- Replace
-
Restart Claude Desktop completely for the changes to take effect.
-
Test the integration by starting a conversation with Claude and asking something like "Show me my latest PagerDuty incidents" or "List my event orchestrations" to verify the MCP server is working.
Security Note: Unlike VS Code's secure input prompts, Claude Desktop requires you to store your API key directly in the configuration file. Ensure this file has appropriate permissions (readable only by your user account) and consider the security implications of storing credentials in plain text.
Running with Docker
The PagerDuty MCP server can be run in a Docker container, providing an isolated and portable deployment option. The Docker image uses stdio transport for MCP communication.
Prerequisites
- Docker installed
- A PagerDuty User API Token (see Prerequisites)
Quick Start
Build the Docker image:
docker build -t pagerduty-mcp:latest .
Run in read-only mode (default):
docker run -i --rm \
-e PAGERDUTY_USER_API_KEY="your-api-key-here" \
pagerduty-mcp:latest
Run with write tools enabled:
docker run -i --rm \
-e PAGERDUTY_USER_API_KEY="your-api-key-here" \
pagerduty-mcp:latest --enable-write-tools
For EU region:
docker run -i --rm \
-e PAGERDUTY_USER_API_KEY="your-api-key-here" \
-e PAGERDUTY_API_HOST="https://api.eu.pagerduty.com" \
pagerduty-mcp:latest
Using with MCP Clients via Docker
To integrate the Docker container with MCP clients, you can use Docker as the command:
Claude Desktop example:
{
"mcpServers": {
"pagerduty-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PAGERDUTY_USER_API_KEY=your-api-key-here",
"pagerduty-mcp:latest"
]
}
}
}
Note: The Docker container uses stdio transport, making it compatible with MCP clients that expect standard input/output communication. Ensure you build the image first using
docker build -t pagerduty-mcp:latest .
Set up locally
-
Clone the repository
-
Install
asdfpluginsasdf plugin add python asdf plugin add nodejs https://github.com/asdf-vm/asdf-nodejs.git asdf plugin add uv -
Install tool versions using
asdf:asdf install -
Create a virtual environment and install dependencies using
uv(now thatasdfhas set the correct Python anduvversions):uv sync -
Ensure
uvis available globally.The MCP server can be run from different places so you need
uvto be available globally. To do so, follow the official documentation.Tip: You may need to restart your terminal and/or VS Code for the changes to take effect.
-
Run it locally
To run your cloned PagerDuty MCP Server you need to update your configuration to use
uvinstead ofuvx."pagerduty-mcp": { "type": "stdio", "command": "uv", "args": [ "run", "--directory", "/path/to/your/mcp-server-directory", // Replace with the full path to the directory where you cloned the MCP server, e.g. "/Users/yourname/code/mcp-server", "python", "-m", "pagerduty_mcp", "--enable-write-tools" // This flag enables write operations on the MCP Server enabling you to creating incidents, schedule overrides and much more ], "env": { "PAGERDUTY_USER_API_KEY": "${input:pagerduty-api-key}", "PAGERDUTY_API_HOST": "https://api.pagerduty.com" // If your PagerDuty account is located in EU update your API host to https://api.eu.pagerduty.com } }
Configuration
The MCP server is configured via environment variables:
| Environment Variable | Required | Default | Description |
|---|---|---|---|
PAGERDUTY_USER_API_KEY | Yes | — | Your PagerDuty User API Token. |
PAGERDUTY_API_HOST | No | https://api.pagerduty.com | PagerDuty API base URL. Use https://api.eu.pagerduty.com for EU accounts. |
Available Tools and Resources
This section describes the tools provided by the PagerDuty MCP server. They are categorized based on whether they only read data or can modify data in your PagerDuty account.
Important: By default, the MCP server only exposes read-only tools. To enable tools that can modify your PagerDuty account (write-mode tools), you must explicitly start the server with the
--enable-write-toolsflag. This helps prevent accidental changes to your PagerDuty data.
| Tool | Area | Description | Read-only |
|---|---|---|---|
| create_alert_grouping_setting | Alert Grouping | Creates a new alert grouping setting | ❌ |
| delete_alert_grouping_setting | Alert Grouping | Deletes an alert grouping setting | ❌ |
| get_alert_grouping_setting | Alert Grouping | Retrieves a specific alert grouping setting | ✅ |
| list_alert_grouping_settings | Alert Grouping | Lists alert grouping settings with filtering | ✅ |
| update_alert_grouping_setting | Alert Grouping | Updates an existing alert grouping setting | ❌ |
| get_change_event | Change Events | Retrieves a specific change event | ✅ |
| list_change_events | Change Events | Lists change events with optional filtering | ✅ |
| list_incident_change_events | Change Events | Lists change events related to a specific incident | ✅ |
| list_service_change_events | Change Events | Lists change events for a specific service | ✅ |
| get_event_orchestration | Event Orchestrations | Retrieves a specific event orchestration | ✅ |
| get_event_orchestration_global | Event Orchestrations | Gets the global orchestration configuration for an event orchestration | ✅ |
| get_event_orchestration_router | Event Orchestrations | Gets the router configuration for an event orchestration | ✅ |
| get_event_orchestration_service | Event Orchestrations | Gets the service orchestration configuration for a specific service | ✅ |
| list_event_orchestrations | Event Orchestrations | Lists event orchestrations with optional filtering | ✅ |
| update_event_orchestration_router | Event Orchestrations | Updates the router configuration for an event orchestration | ❌ |
| append_event_orchestration_router_rule | Event Orchestrations | Adds a new routing rule to an event orchestration router | ❌ |
| list_escalation_policies | Escalation Policy | Lists escalation policies | ✅ |
| get_escalation_policy | Escalation Policy | Retrieves a specific escalation policy | ✅ |
| add_note_to_incident | Incidents | Adds note to an incident | ❌ |
| add_responders | Incidents | Adds responders to an incident | ❌ |
| create_incident | Incidents | Creates a new incident | ❌ |
| get_alert_from_incident | Incidents | Retrieves a specific alert from an incident | ✅ |
| get_incident | Incidents | Retrieves a specific incident | ✅ |
| get_outlier_incident | Incidents | Retrieves outlier incident information for a specific incident | ✅ |
| get_past_incidents | Incidents | Retrieves past incidents related to a specific incident | ✅ |
| get_related_incidents | Incidents | Retrieves related incidents for a specific incident | ✅ |
| list_alerts_from_incident | Incidents | Lists all alerts for a specific incident with pagination | ✅ |
| list_incident_notes | Incidents | Lists all notes for a specific incident | ✅ |
| list_incidents | Incidents | Lists incidents | ✅ |
| manage_incidents | Incidents | Updates status, urgency, assignment, or escalation level | ❌ |
| get_incident_workflow | Incident Workflows | Retrieves a specific incident workflow | ✅ |
| list_incident_workflows | Incident Workflows | Lists incident workflows with optional filtering | ✅ |
| start_incident_workflow | Incident Workflows | Starts a workflow instance for an incident | ❌ |
| get_log_entry | Log Entries | Retrieves a specific log entry by ID | ✅ |
| list_log_entries | Log Entries | Lists all log entries across the account with time filtering | ✅ |
| add_team_member | Teams | Adds a user to a team with a specific role | ❌ |
| create_team | Teams | Creates a new team | ❌ |
| delete_team | Teams | Deletes a team | ❌ |
| get_team | Teams | Retrieves a specific team | ✅ |
| list_team_members | Teams | Lists members of a team | ✅ |
| list_teams | Teams | Lists teams | ✅ |
| remove_team_member | Teams | Removes a user from a team | ❌ |
| update_team | Teams | Updates an existing team | ❌ |
| get_user_data | Users | Gets the current user's data | ✅ |
| list_users | Users | Lists users in the PagerDuty account | ✅ |
| list_oncalls | On-call | Lists on-call schedules | ✅ |
| create_schedule_override | Schedules | Creates an override for a schedule | ❌ |
| get_schedule | Schedules | Retrieves a specific schedule | ✅ |
| list_schedule_users | Schedules | Lists users in a schedule | ✅ |
| list_schedules | Schedules | Lists schedules | ✅ |
| create_schedule | Schedules | Creates a new on-call schedule | ❌ |
| update_schedule | Schedules | Updates an existing schedule | ❌ |
| create_service | Services | Creates a new service | ❌ |
| get_service | Services | Retrieves a specific service | ✅ |
| list_services | Services | Lists services | ✅ |
| update_service | Services | Updates an existing service | ❌ |
| create_status_page_post | Status Pages | Creates a new post (incident or maintenance) on a status page | ❌ |
| create_status_page_post_update | Status Pages | Adds a new update to an existing status page post | ❌ |
| get_status_page_post | Status Pages | Retrieves details of a specific status page post | ✅ |
| list_status_page_impacts | Status Pages | Lists available impact levels for a status page | ✅ |
| list_status_page_post_updates | Status Pages | Lists all updates for a specific status page post | ✅ |
| list_status_page_severities | Status Pages | Lists available severity levels for a status page | ✅ |
| list_status_page_statuses | Status Pages | Lists available statuses for a status page | ✅ |
| list_status_pages | Status Pages | Lists all status pages with optional filtering | ✅ |
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.
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →Configuration
PAGERDUTY_USER_API_KEYPagerDuty User API Token - obtain from User Settings > API Access in your PagerDuty account
PAGERDUTY_API_HOSTPagerDuty API host URL (default: https://api.pagerduty.com, EU: https://api.eu.pagerduty.com)