# PagerDuty — how to use (mcp.ai) PagerDuty helps you proactively manage your digital operations by collecting data signals from anywhere, interpreting those signals using machine learning, automatically engaging the right people, and accelerating resolution and learning. ## Option A — via MCP (recommended) Remote MCP endpoint (HTTP, streamable): `https://api.mcp.ai/p_pagerduty?ms=1781857980000` Add it as a custom/remote MCP connector in your client (Claude, Cursor, VS Code…), then authenticate when prompted. Once connected, ask the agent to use the server's tools (e.g. `pagerduty_add_service_to_incident_workflow_trigger`). ## Option B — via direct REST API Base URL: `https://api.mcp.ai/api/pagerduty` Auth: `Authorization: Bearer sk_live_…` — create a workspace API key at https://mcp.ai/settings/api-keys Discover endpoints: `GET https://api.mcp.ai/api/pagerduty/_endpoints` ### Endpoints - `POST https://api.mcp.ai/api/pagerduty/add/service/to/incident/workflow/trigger` — 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 t - body: { id: string, service__id?: string } - `POST https://api.mcp.ai/api/pagerduty/aggregate/escalation/policy/incident/metrics` — 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 - body: { order?: string, order_by?: string, time_zone?: string, aggregate_unit?: string, filters__major?: boolean, filters__urgency?: string, filters__team__ids?: string[], filters__service__ids?: string[], filters__priority__ids?: string[], filters__priority__names?: string[], filters__created__at__end?: string, filters__pd__advance__used?: boolean, filters__created__at__start?: string, filters__min__ackowledgements?: integer, filters__escalation__policy__ids?: string[], filters__min__manual__escalations?: integer, filters__min__timeout__escalations?: integer } - `POST https://api.mcp.ai/api/pagerduty/associate/service/dependencies` — 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 se - body: { relationships?: object[] } - `POST https://api.mcp.ai/api/pagerduty/associate/team/with/automation/action` — 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 action - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/audit/escalation/policy/records` — 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 - body: { id: string, limit?: integer, since?: string, until?: string, cursor?: string } - `POST https://api.mcp.ai/api/pagerduty/convert/service/rule/by/id` — 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, improvi - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/count/paused/incident/reports` — 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 - body: { since?: string, until?: string, service_id?: string, suspended_by?: string } - `POST https://api.mcp.ai/api/pagerduty/create/a/custom/field/for/an/incident/type` — 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 featur - body: { field__name?: string, field__enabled?: boolean, type_id_or_name: string, field__data__type?: string, field__description?: string, field__field__type?: string, field__display__name?: string, field__default__value?: string, field__field__options?: string[] } - `POST https://api.mcp.ai/api/pagerduty/create/a/field/option/for/a/custom/field` — 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 - body: { field_id: string, type_id_or_name: string, field__option__data__value?: string, field__option__data__data__type?: string } - `POST https://api.mcp.ai/api/pagerduty/create/a/ruleset` — 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 - `POST https://api.mcp.ai/api/pagerduty/create/a/trigger` — Create new incident workflow trigger scoped oauth requires: `incident workflows.write` - `POST https://api.mcp.ai/api/pagerduty/create/an/incident/type` — 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. - body: { incident__type__name?: string, incident__type__enabled?: boolean, incident__type__description?: string, incident__type__parent__type?: string, incident__type__display__name?: string } - `POST https://api.mcp.ai/api/pagerduty/create/and/manage/custom/incident/fields` — 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 capabiliti - `POST https://api.mcp.ai/api/pagerduty/create/automation/runner/endpoint` — 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, wh - body: { runner: object } - `POST https://api.mcp.ai/api/pagerduty/create/business/service` — 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 t - body: { business__service__name?: string, business__service__team__id?: string, business__service__description?: string, business__service__point__of__contact?: string } - `POST https://api.mcp.ai/api/pagerduty/create/escalation/policy` — 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 incident - `POST https://api.mcp.ai/api/pagerduty/create/event/orchestration` — 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 - body: { orchestration__id?: string, orchestration__name?: string, orchestration__self?: string, orchestration__routes?: integer, orchestration__version?: string, orchestration__team__id?: string, orchestration__team__self?: string, orchestration__team__type?: string, orchestration__created__at?: string, orchestration__description?: string, orchestration__updated__at?: string, orchestration__integrations?: object[], orchestration__created__by__id?: string, orchestration__updated__by__id?: string, orchestration__created__by__self?: string, orchestration__created__by__type?: string, orchestration__updated__by__self?: string, orchestration__updated__by__type?: string } - `POST https://api.mcp.ai/api/pagerduty/create/event/rule/in/ruleset` — 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 - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/create/extension/object` — 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 specif - `POST https://api.mcp.ai/api/pagerduty/create/handoff/notification/rule` — 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 shif - body: { id: string, oncall__handoff__notification__rule__id?: string, oncall__handoff__notification__rule__handoff__type?: string, oncall__handoff__notification__rule__notify__advance__in__minutes?: integer } - `POST https://api.mcp.ai/api/pagerduty/create/incident/field/option` — 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 categori - body: { field_id: string } - `POST https://api.mcp.ai/api/pagerduty/create/incident/record` — 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 document - body: { incident__type?: string, incident__title?: string, incident__urgency?: string, incident__body__type?: string, incident__assignments?: object[], incident__service__id?: string, incident__priority__id?: string, incident__body__details?: string, incident__incident__key?: string, incident__service__type?: string, incident__priority__type?: string, incident__incident__type__id?: string, incident__incident__type__name?: string, incident__incident__type__type?: string, incident__conference__bridge__conference__url?: string, incident__conference__bridge__conference__type?: string, incident__conference__bridge__conference__number?: string } - `POST https://api.mcp.ai/api/pagerduty/create/incident/workflow` — 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 pr - `POST https://api.mcp.ai/api/pagerduty/create/incident/workflow/instance` — 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. - body: { id: string, incident__workflow__instance__incident__type?: string } - `POST https://api.mcp.ai/api/pagerduty/create/integration/for/orchestration` — 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 e - body: { id: string, integration__label?: string } - `POST https://api.mcp.ai/api/pagerduty/create/integration/for/service` — 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 c - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/create/maintenance/window/object` — 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 se - `POST https://api.mcp.ai/api/pagerduty/create/new/schedule/layer` — 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 patter - body: { overflow?: boolean } - `POST https://api.mcp.ai/api/pagerduty/create/new/service` — 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, - `POST https://api.mcp.ai/api/pagerduty/create/new/tag/in/system` — 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 res - `POST https://api.mcp.ai/api/pagerduty/create/new/team/with/details` — 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 schedul - `POST https://api.mcp.ai/api/pagerduty/create/new/webhook/subscription` — 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 trigg - body: { webhook__subscription__id?: string, webhook__subscription__type?: string, webhook__subscription__active?: boolean, webhook__subscription__events?: string[], webhook__subscription__filter__id?: string, webhook__subscription__description?: string, webhook__subscription__filter__type?: string, webhook__subscription__delivery__method__id?: string, webhook__subscription__delivery__method__url?: string, webhook__subscription__delivery__method__type?: string, webhook__subscription__delivery__method__secret?: string, webhook__subscription__delivery__method__custom__headers?: object[], webhook__subscription__delivery__method__temporarily__disabled?: boolean } - `POST https://api.mcp.ai/api/pagerduty/create/or/update/status/page/post` — 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 - body: { id: string, post__type?: string, post__title?: string, post__updates?: object[], post__ends__at?: string, post__post__type?: string, post__starts__at?: string, post__status__page__id?: string, post__status__page__type?: string } - `POST https://api.mcp.ai/api/pagerduty/create/or/update/status/page/postmortem` — 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 - body: { id: string, post_id: string, postmortem__type?: string, postmortem__message?: string, postmortem__post__id?: string, postmortem__post__type?: string, postmortem__notify__subscribers?: boolean } - `POST https://api.mcp.ai/api/pagerduty/create/response/play/for/incidents` — 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 su - `POST https://api.mcp.ai/api/pagerduty/create/schedule/overrides/configuration` — 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 use - body: { id: string, overrides?: string[] } - `POST https://api.mcp.ai/api/pagerduty/create/service/event/rule` — 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 - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/create/status/page/subscription` — 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 inf - body: { id: string, subscription__type?: string, subscription__channel?: string, subscription__contact?: string, subscription__status__page__id?: string, subscription__status__page__type?: string, subscription__subscribable__object__id?: string, subscription__subscribable__object__type?: string } - `POST https://api.mcp.ai/api/pagerduty/create/status/update/template` — 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 - body: { template__name?: string, template__description?: string, template__template__type?: string, template__templated__fields__message?: string, template__templated__fields__email__body?: string, template__templated__fields__email__subject?: string } - `POST https://api.mcp.ai/api/pagerduty/create/user/notification/rule` — 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 n - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/create/user/object` — 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 - `POST https://api.mcp.ai/api/pagerduty/create/user/status/update/notification/rule` — 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 not - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/create/workflow/integration/connection` — Create a new workflow integration connection. scoped oauth requires: `workflow integrations:connections.write` - body: { id?: string, name: string, type?: string, teams?: object[], scopes?: string[], is_default?: boolean, external_id?: string, service_url?: string, integration_id: string, external_id_label?: string, health__is__healthy?: boolean, health__health__message?: string, health__last__checked__at?: string } - `POST https://api.mcp.ai/api/pagerduty/delete/a/custom/field/for/an/incident/type` — 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 featur - body: { field_id: string, type_id_or_name: string } - `POST https://api.mcp.ai/api/pagerduty/delete/a/field/option/for/a/custom/field` — Delete a field option for a custom field. > ### 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 - body: { field_id: string, field_option_id: string, type_id_or_name: string } - `POST https://api.mcp.ai/api/pagerduty/delete/account/subscription/by/id` — 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 th - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/addon/by/id` — 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 - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/alert/grouping/setting` — 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 - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/all/oauth/delegations` — 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. - body: { type: string, user_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/automation/action/by/id` — 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. i - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/automation/action/service/by/id` — 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 f - body: { id: string, service_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/automation/actions/runner/by/id` — 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 s - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/business/service/by/id` — 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 organiza - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/business/service/priority/thresholds` — 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 the - `POST https://api.mcp.ai/api/pagerduty/delete/cache/variable/for/event` — 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 - body: { id: string, cache_variable_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/cache/variable/from/service` — 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 s - body: { service_id: string, cache_variable_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/custom/field/by/field/id` — 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 yo - body: { field_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/escalation/policy/by/id` — 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 escalat - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/event/by/id` — 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 ru - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/extension/by/id` — 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 acco - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/field/option` — 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 incide - body: { field_id: string, field_option_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/incident/workflow/by/id` — 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 - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/incident/workflow/trigger/by/id` — 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 sho - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/incident/workflow/trigger/service` — 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 fr - body: { service_id: string, trigger_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/integration/from/event/orchestration` — 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 fr - body: { id: string, integration_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/maintenance/window/by/id` — 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 in - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/oncall/handoff/notification/rule` — 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 be - body: { id: string, oncall_handoff_notification_rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/post/from/status/page` — 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 wit - body: { id: string, post_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/post/update/by/id` — 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 accur - body: { id: string, post_id: string, post_update_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/response/play` — 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 per - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/rule/from/ruleset/by/id` — 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 - body: { id: string, rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/ruleset/by/id` — 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 manageme - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/runner/team/association` — 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 - body: { id: string, team_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/schedule/by/id` — 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 incide - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/schedule/override/by/id` — 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 i - body: { id: string, override_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/service/by/id` — 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 - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/service/rule/by/id` — 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 - body: { id: string, rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/status/page/postmortem` — 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 - body: { id: string, post_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/status/update/notification/rule` — 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 notificati - body: { id: string, status_update_notification_rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/subscription/from/status/page` — Deletes a specific subscription associated with a pagerduty status page. this endpoint is used to remove a subscription, effectively stopping notifications or updates related to the status page for th - body: { id: string, subscription_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/tag/by/id` — Deletes a specific tag from the pagerduty system based on its unique identifier. this endpoint should be used when you need to remove a tag that is no longer relevant or necessary for categorizing inc - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/team/by/id` — Deletes a specific team from the pagerduty system based on the provided team id. this endpoint should be used when you need to remove a team that is no longer required in your incident management stru - body: { id: string, reassignment_team?: string } - `POST https://api.mcp.ai/api/pagerduty/delete/team/escalation/policy` — This endpoint removes an escalation policy association from a specific team in pagerduty. it is used to update team configurations by disassociating an escalation policy that is no longer needed or re - body: { id: string, escalation_policy_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/team/from/automation/action` — This endpoint removes a specific team's access to an automation action in pagerduty. it's used to revoke permissions when a team no longer needs to use or should not have access to a particular automa - body: { id: string, team_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/template/by/id` — Deletes a specific template from the pagerduty account. this endpoint is used to permanently remove a template configuration, which can be useful for cleaning up outdated or unnecessary incident respo - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/user/by/id` — Deletes a specific user from the pagerduty system using their unique identifier. this endpoint should be used when you need to permanently remove a user's account, such as when an employee leaves the - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/user/contact/method` — Deletes a specific contact method associated with a user in pagerduty. this endpoint should be used when you need to remove an outdated or unnecessary contact method from a user's profile. it permanen - body: { id: string, contact_method_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/user/from/team/by/id` — This endpoint removes a specific user from a designated team within the pagerduty incident management platform. it is used to update team compositions by disassociating a user from a particular team, - body: { id: string, user_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/user/notification/rule` — Deletes a specific notification rule for a user in pagerduty. this endpoint allows administrators or users with appropriate permissions to remove custom notification rules, modifying how and when a us - body: { id: string, notification_rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/user/session/by/id` — Deletes all active sessions for a specified user in the pagerduty system. this endpoint is used to forcibly log out a user from all devices and applications where they might be currently authenticated - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/user/session/by/type` — This endpoint deletes a specific user session in pagerduty. it is used to forcibly terminate an active session for a given user, effectively logging them out from a particular device or application. t - body: { id: string, type: string, session_id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/webhook/subscription/by/id` — Deletes a specific webhook subscription from your pagerduty account. this endpoint should be used when you want to stop receiving notifications for a particular webhook subscription, such as when the - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/delete/workflow/integration/connection` — Delete a workflow integration connection. scoped oauth requires: `workflow integrations:connections.write` - body: { id: string, integration_id: string } - `POST https://api.mcp.ai/api/pagerduty/disassociate/service/dependencies` — This endpoint disassociates service dependencies in pagerduty by deleting specified relationships between supporting and dependent services. it allows for the removal of multiple service dependencies - body: { relationships?: object[] } - `POST https://api.mcp.ai/api/pagerduty/edit/webhook/subscription/by/id` — The updatewebhooksubscription endpoint allows you to modify an existing webhook subscription in pagerduty. this put method enables users to update the events they want to be notified about, change the - body: { id: string, webhook__subscription__active?: boolean, webhook__subscription__events?: string[], webhook__subscription__filter__id?: string, webhook__subscription__description?: string, webhook__subscription__filter__type?: string } - `POST https://api.mcp.ai/api/pagerduty/enable/extension/by/id` — Enables a specific extension in the pagerduty system. this endpoint is used to activate an extension that has been previously configured but is currently inactive. it allows users to turn on additiona - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/enable/webhook/subscription/by/id` — Activates a specific webhook subscription in pagerduty, enabling the system to send notifications for the events configured in that subscription. this endpoint should be used when you want to start re - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/execute/response/play/by/id` — Executes a predefined response play for a specific incident in pagerduty. this endpoint allows you to trigger a sequence of automated actions designed to manage and respond to the given incident. it's - body: { response_play_id: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/cache/variable/for/event/orchestration` — Retrieves detailed information about a specific cache variable within an event orchestration in pagerduty. this endpoint allows users to fetch the current state and configuration of a cache variable, - body: { id: string, cache_variable_id: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/custom/incident/field/by/id` — Retrieves detailed information about a specific custom field associated with incidents in pagerduty. this endpoint allows users to fetch the configuration and attributes of a custom field by providing - body: { include?: string, field_id: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/escalation/polices/list` — Retrieves a list of escalation policies configured in the pagerduty account. this endpoint allows users to access detailed information about how incidents are escalated within their organization, incl - body: { limit?: integer, query?: string, total?: boolean, offset?: integer, include?: string, sort_by?: string, team__ids?: string[], user__ids?: string[] } - `POST https://api.mcp.ai/api/pagerduty/fetch/event/orchestrations` — Retrieves a list of event orchestrations configured in the pagerduty account. event orchestrations are used to manage and automate the routing and handling of events and incidents. this endpoint allow - body: { limit?: integer, offset?: integer, sort_by?: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/incident/analytics/by/id` — Retrieves raw analytics data for a specific incident in pagerduty. this endpoint provides unprocessed incident information, allowing for detailed analysis and custom reporting. it should be used when - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/incident/list` — Retrieves a list of incidents from pagerduty based on specified criteria. this endpoint allows users to fetch multiple incidents, making it useful for incident management, reporting, and analysis. it - body: { limit?: integer, since?: string, total?: boolean, until?: string, offset?: integer, include?: string, sort_by?: string[], statuses?: string, team__ids?: string[], time_zone?: string, urgencies?: string, user__ids?: string[], date_range?: string, incident_key?: string, service__ids?: string[] } - `POST https://api.mcp.ai/api/pagerduty/fetch/outlier/incident/by/id` — Retrieves detailed information about an outlier incident associated with a specific incident in pagerduty. this endpoint is used to gather insights on incidents that deviate significantly from normal - body: { id: string, since?: string, additional__details?: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/post/update/status` — Retrieves detailed information about a specific post update on a pagerduty status page. this endpoint allows you to fetch the content and metadata of a particular update made to a post, providing insi - body: { id: string, post_id: string, post_update_id: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/priorities/list` — Retrieves a list of existing priorities in the pagerduty system, ordered from most severe to least severe. this endpoint should be used when you need to obtain information about the current priority l - body: { limit?: integer, total?: boolean, offset?: integer } - `POST https://api.mcp.ai/api/pagerduty/fetch/related/change/events/for/incident` — Retrieves a list of change events related to a specific incident in pagerduty. this endpoint is used to gather contextual information about changes or updates associated with an incident, which can be - body: { id: string, limit?: integer } - `POST https://api.mcp.ai/api/pagerduty/fetch/related/incidents/by/id` — Retrieves a list of incidents that are potentially related to a specified incident in pagerduty. this endpoint utilizes machine learning algorithms to identify and return incidents that may be connect - body: { id: string, additional__details?: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/runner/teams/integration` — Retrieves a list of teams associated with a specific automation action runner in pagerduty. this endpoint allows users to identify which teams have access to or are responsible for a particular runner - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/status/pages` — Retrieves a list of all status pages configured in the pagerduty account. status pages provide real-time information about the operational status of services, ongoing incidents, and planned maintenanc - body: { status_page_type?: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/user/contact/method` — Retrieves detailed information about a specific contact method for a particular user in pagerduty. this endpoint allows you to fetch the configuration and settings of a single contact method, such as - body: { id: string, contact_method_id: string } - `POST https://api.mcp.ai/api/pagerduty/fetch/vendor/list` — Retrieves a list of vendors or third-party integrations available in the pagerduty platform. this endpoint allows users to access information about various services and tools that can be integrated wi - body: { limit?: integer, total?: boolean, offset?: integer } - `POST https://api.mcp.ai/api/pagerduty/filter/and/aggregate/incident/metrics` — Analyzes and aggregates incident metrics across teams in pagerduty, allowing for detailed filtering and customization of results. this endpoint is used to gain insights into incident patterns, team pe - body: { order?: string, order_by?: string, time_zone?: string, aggregate_unit?: string, filters__major?: boolean, filters__urgency?: string, filters__team__ids?: string[], filters__service__ids?: string[], filters__priority__ids?: string[], filters__priority__names?: string[], filters__created__at__end?: string, filters__pd__advance__used?: boolean, filters__created__at__start?: string, filters__min__ackowledgements?: integer, filters__escalation__policy__ids?: string[], filters__min__manual__escalations?: integer, filters__min__timeout__escalations?: integer } - `POST https://api.mcp.ai/api/pagerduty/get/a/field/option/on/a/custom/field` — Get a field option on a custom field > ### 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. - body: { field_id: string, field_option_id: string, type_id_or_name: string } - `POST https://api.mcp.ai/api/pagerduty/get/a/trigger` — Retrieve an existing incident workflows trigger scoped oauth requires: `incident workflows.read` - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/addons/list` — Retrieves a list of all addons associated with the pagerduty account. this endpoint allows users to view the additional features or integrations that have been added to enhance the platform's capabili - body: { limit?: integer, total?: boolean, filter?: string, offset?: integer, include?: string, service__ids?: string[] } - `POST https://api.mcp.ai/api/pagerduty/get/aggregated/pd/advance/usage/data` — Provides aggregated metrics for the usage of pd advance. > **note:** analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=data%20updat - body: { time_zone?: string, filters__major?: boolean, filters__urgency?: string, filters__team__ids?: string[], filters__service__ids?: string[], filters__priority__ids?: string[], filters__priority__names?: string[], filters__created__at__end?: string, filters__created__at__start?: string, filters__min__ackowledgements?: integer, filters__escalation__policy__ids?: string[], filters__min__manual__escalations?: integer, filters__min__timeout__escalations?: integer, filters__incident__created__at__end?: string, filters__incident__created__at__start?: string } - `POST https://api.mcp.ai/api/pagerduty/get/alert/grouping/settings` — Retrieves the current alert grouping settings for the pagerduty account. this endpoint provides information on how alerts are automatically grouped together in the incident management system. it shoul - body: { after?: string, limit?: integer, total?: boolean, before?: string, service__ids?: string[] } - `POST https://api.mcp.ai/api/pagerduty/get/alerts/by/incident/id` — Retrieves all alerts associated with a specific incident in pagerduty. this endpoint allows users to fetch detailed information about the notifications and alerts that were triggered as part of an inc - body: { id: string, limit?: integer, total?: boolean, offset?: integer, include?: string, sort_by?: string, statuses?: string, alert_key?: string } - `POST https://api.mcp.ai/api/pagerduty/get/an/incident/type` — Get detailed information about a single incident type. accepts either an incident type id, or an incident type name. incident types are a feature which will allow customers to categorize incidents, su - body: { type_id_or_name: string } - `POST https://api.mcp.ai/api/pagerduty/get/an/incident/type/custom/field` — Get 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 - body: { include?: string, field_id: string, type_id_or_name: string } - `POST https://api.mcp.ai/api/pagerduty/get/audit/records` — Retrieves a list of audit records from the pagerduty system. this endpoint allows users to access logs of configuration changes made to pagerduty resources, such as account objects. the records are so - body: { limit?: integer, since?: string, until?: string, cursor?: string, actions?: string, actor_id?: string, actor_type?: string, method_type?: string, root__resource__types?: string, method_truncated_token?: string } - `POST https://api.mcp.ai/api/pagerduty/get/automation/action/by/id` — Retrieves detailed information about a specific automation action in pagerduty's incident management platform. this endpoint allows users to fetch the configuration and attributes of a predefined auto - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/automation/action/runner/by/id` — Retrieves detailed information about a specific automation action runner in pagerduty. this endpoint allows users to fetch the configuration, status, and other relevant details of a runner by providin - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/automation/action/team/by/team/id` — Retrieves detailed information about a specific automation action's association with a particular team in pagerduty. this endpoint allows you to examine how an automation action is configured or appli - body: { id: string, team_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/automation/actions/runners` — Retrieves a list of automation action runners associated with the pagerduty account. this endpoint allows users to view all available runners that can execute automation actions within their incident - body: { name?: string, limit?: integer, cursor?: string, include?: string[] } - `POST https://api.mcp.ai/api/pagerduty/get/business/service/subscribers/by/id` — Retrieves a list of subscribers for a specific business service in pagerduty. this endpoint allows you to fetch all users or teams configured to receive notifications for incidents related to the spec - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/business/services/priority/thresholds` — Retrieves the current priority threshold settings for all business services in pagerduty. this endpoint allows users to fetch the configured thresholds that determine incident prioritization and escal - `POST https://api.mcp.ai/api/pagerduty/get/cache/variable/by/id` — Retrieves detailed information about a specific cache variable associated with a particular service within an event orchestration in pagerduty. this endpoint allows you to access the current state and - body: { service_id: string, cache_variable_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/cache/variables/for/service` — Retrieves the cache variables associated with a specific service in pagerduty's event orchestration system. this endpoint allows you to access temporary storage data used within event orchestration wo - body: { service_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/escalation/policy/by/id` — Retrieves detailed information about a specific escalation policy in pagerduty. this endpoint allows you to fetch the complete configuration of an escalation policy, including its name, description, e - body: { id: string, include?: string } - `POST https://api.mcp.ai/api/pagerduty/get/event/integrations/by/id` — Retrieves a list of integrations associated with a specific event orchestration in pagerduty. this endpoint allows users to fetch all the integrations that are configured for a particular event orches - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/event/orchestration/by/id` — Retrieves detailed information about a specific event orchestration in pagerduty using its unique identifier. this endpoint allows users to fetch the configuration and settings of a particular event o - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/event/orchestration/cache/variables` — Retrieves the cache variables associated with a specific event orchestration in pagerduty. this endpoint allows you to access temporary data storage elements used during event orchestration processes, - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/event/orchestration/global` — Get the global orchestration for an event orchestration. global orchestration rules allows you to create a set of event rules. these rules evaluate against all events sent to an event orchestration. w - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/event/orchestration/integration` — Retrieves detailed information about a specific integration associated with an event orchestration in pagerduty. this endpoint allows you to fetch the configuration and settings of a particular integr - body: { id: string, integration_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/extension/schema/by/id` — Retrieves a specific extension schema from pagerduty by its unique identifier. this endpoint is used to fetch detailed information about a custom data structure that extends the functionality of the p - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/impact/by/status/page/id` — Retrieves detailed information about a specific impact on a pagerduty status page. this endpoint allows you to fetch the current state and details of a particular impact, such as its severity, affecte - body: { id: string, impact_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/incident/alert/details` — Retrieves detailed information about a specific alert associated with a particular incident in pagerduty. this endpoint is used when you need to access the properties and current state of an individua - body: { id: string, alert_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/incident/log/entries/by/id` — Retrieves all log entries associated with a specific incident in pagerduty. this endpoint provides a comprehensive history of actions, notifications, and status changes related to the incident. it sho - body: { id: string, limit?: integer, since?: string, total?: boolean, until?: string, offset?: integer, include?: string, time_zone?: string, is_overview?: boolean } - `POST https://api.mcp.ai/api/pagerduty/get/incident/workflow/action/by/id` — Retrieves detailed information about a specific action within an incident workflow in pagerduty. this endpoint allows users to fetch the configuration, settings, and other relevant details of a partic - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/incident/workflows` — Retrieves a list of incident workflows configured in the pagerduty account. this endpoint allows users to fetch information about automated sequences of actions set up to respond to incidents. it's us - body: { limit?: integer, query?: string, total?: boolean, offset?: integer, include?: string } - `POST https://api.mcp.ai/api/pagerduty/get/incident/workflows/actions` — Retrieves a list of all available actions that can be used in incident workflows within pagerduty. this endpoint provides information about the various automated tasks and responses that can be config - body: { limit?: integer, cursor?: string, keyword?: string } - `POST https://api.mcp.ai/api/pagerduty/get/log/entries` — Retrieves log entries from the pagerduty system, providing a detailed history of events and actions related to incidents and system activities. this endpoint is crucial for auditing purposes, allowing - body: { limit?: integer, since?: string, total?: boolean, until?: string, offset?: integer, include?: string, team__ids?: string[], time_zone?: string, is_overview?: boolean } - `POST https://api.mcp.ai/api/pagerduty/get/maintenance/window/by/id` — Retrieves detailed information about a specific maintenance window in pagerduty. this endpoint allows users to access the configuration, schedule, and status of a particular maintenance window using i - body: { id: string, include?: string } - `POST https://api.mcp.ai/api/pagerduty/get/oauth/delegations/revocation/requests/status` — Get the status of all oauth delegations revocation requests for this account, specifically how many requests are still pending. this endpoint is limited to account owners and admins. scoped oauth requ - body: { requested_at_end?: string } - `POST https://api.mcp.ai/api/pagerduty/get/paused/incident/alerts` — Retrieves alerts associated with paused incident reports in pagerduty. this endpoint allows users to fetch information about alerts that have been temporarily halted in the reporting process. it's use - body: { since?: string, until?: string, service_id?: string, suspended_by?: string } - `POST https://api.mcp.ai/api/pagerduty/get/post/from/status/page/by/id` — Retrieves detailed information about a specific post on a pagerduty status page. this endpoint allows you to fetch the content, timestamp, and any associated metadata for a particular update or messag - body: { id: string, include?: string[], post_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/response/plays` — Retrieves a list of response plays configured in the pagerduty account. response plays are predefined sets of actions that can be automatically executed when an incident occurs, helping to streamline - body: { query?: string, filter_for_manual_run?: boolean } - `POST https://api.mcp.ai/api/pagerduty/get/rule/from/ruleset/by/id` — Retrieves detailed information about a specific rule within a pagerduty ruleset. this endpoint allows users to fetch the configuration and settings of an individual rule, which is essential for unders - body: { id: string, rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/schedules` — Retrieves a list of all schedules from your pagerduty account. this endpoint provides essential information about on-call rotations, helping teams manage and organize their incident response workflows - body: { limit?: integer, query?: string, total?: boolean, offset?: integer, include?: string, time_zone?: string } - `POST https://api.mcp.ai/api/pagerduty/get/service/impacts/by/url/slug` — Retrieves service impacts for a specific status dashboard in pagerduty. this endpoint allows users to fetch real-time information about how incidents or maintenance activities are affecting services d - body: { url_slug: string, additional__fields?: string } - `POST https://api.mcp.ai/api/pagerduty/get/severity/for/status/page` — Retrieves detailed information about a specific severity level on a particular status page in pagerduty. this endpoint is used to fetch the configuration and metadata associated with a severity, which - body: { id: string, severity_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/specific/post/update/status` — Retrieves the updates for a specific post on a pagerduty status page. this endpoint allows users to fetch the chronological list of updates made to a particular post, providing detailed information ab - body: { id: string, post_id: string, reviewed_status?: string } - `POST https://api.mcp.ai/api/pagerduty/get/status/dashboard/by/id` — Retrieves detailed information about a specific status dashboard in pagerduty. this endpoint allows users to fetch the current configuration, components, and status of a particular dashboard, which is - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/status/for/status/page/by/id` — Retrieves the current status of a specific item on a pagerduty status page. this endpoint is used to fetch up-to-date information about the operational state of a particular service or component liste - body: { id: string, status_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/status/page/impacts/by/id` — Retrieves the impacts associated with a specific status page in pagerduty. this endpoint allows users to fetch detailed information about service disruptions, incidents, or other events affecting the - body: { id: string, post_type?: string } - `POST https://api.mcp.ai/api/pagerduty/get/status/page/subscription` — Retrieves detailed information about a specific subscription associated with a particular status page in pagerduty. this endpoint allows users to fetch subscription details such as the subscriber's co - body: { id: string, subscription_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/team/members/by/id` — Retrieves a list of all members associated with a specific team in pagerduty. this endpoint is useful for obtaining detailed information about the composition of a team, including user ids, names, rol - body: { id: string, limit?: integer, total?: boolean, offset?: integer, include?: string } - `POST https://api.mcp.ai/api/pagerduty/get/team/notification/subscriptions` — Retrieves the notification subscriptions for a specific team in pagerduty. this endpoint allows you to fetch detailed information about how a team is configured to receive notifications for various ev - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/teams/associated/with/action/id` — Retrieves the list of teams associated with a specific automation action in pagerduty. this endpoint is useful for understanding which teams are responsible for or have access to a particular automate - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/template/by/id` — Retrieves detailed information about a specific template in pagerduty by its unique identifier. this endpoint is used to access the configuration and settings of a pre-defined template, which can incl - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/the/service/orchestration/for/a/service` — Get a service orchestration. a service orchestration allows you to create a set of event rules. the service orchestration evaluates events sent to this service against each of its rules, beginning wit - body: { include?: string, service_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/user/notification/subscriptions` — Retrieves the notification subscriptions for a specific user in pagerduty. this endpoint allows you to fetch detailed information about how a user is configured to receive various types of notificatio - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/user/session/by/type` — Retrieves detailed information about a specific user session in pagerduty. this endpoint allows you to fetch session-related data for a particular user, filtered by session type and identified by a un - body: { id: string, type: string, session_id: string } - `POST https://api.mcp.ai/api/pagerduty/get/user/sessions/by/id` — Retrieves all active sessions for a specific user in pagerduty. this endpoint allows you to fetch information about a user's current login sessions, which can be useful for auditing, security monitori - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/user/status/update/notification/rules` — Retrieves the status update notification rules for a specific user in pagerduty. this endpoint allows you to fetch the configured rules that determine how and when a user receives notifications about - body: { id: string, include?: string } - `POST https://api.mcp.ai/api/pagerduty/get/webhook/subscription/by/id` — Retrieves detailed information about a specific webhook subscription in pagerduty. this endpoint allows you to fetch the configuration and status of a webhook subscription, including its delivery meth - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/workflow/integration` — Get details about a workflow integration. scoped oauth requires: `workflow integrations.read` - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/get/workflow/integration/connection` — Get details about a workflow integration connection. scoped oauth requires: `workflow integrations:connections.read` - body: { id: string, integration_id: string } - `POST https://api.mcp.ai/api/pagerduty/install/add/on/endpoint` — This endpoint allows you to install a new add-on to your pagerduty account, enhancing its functionality with custom integrations. add-ons can be either full-page or incident-specific, providing additi - `POST https://api.mcp.ai/api/pagerduty/invoke/automation/action/by/id` — Invokes a specific automation action in pagerduty, associating it with a particular incident. this endpoint allows you to trigger pre-defined automated tasks or workflows within the pagerduty incident - body: { id: string, invocation__metadata__incident__id?: string } - `POST https://api.mcp.ai/api/pagerduty/list/all/workflow/integration/connections` — List all workflow integration connections. scoped oauth requires: `workflow integrations:connections.read` - body: { name?: string, limit?: integer, cursor?: string } - `POST https://api.mcp.ai/api/pagerduty/list/automation/action/details` — This endpoint retrieves a list of automation actions configured in the pagerduty account. automation actions are predefined tasks or operations that can be executed automatically in response to incide - body: { name?: string, limit?: integer, cursor?: string, team_id?: string, runner_id?: string, service_id?: string, action_type?: string, classification?: string } - `POST https://api.mcp.ai/api/pagerduty/list/extension/schemas` — Retrieves all available extension schemas from the pagerduty api. this endpoint allows users to fetch custom schema extensions that have been defined for their pagerduty account. extension schemas are - body: { limit?: integer, total?: boolean, offset?: integer } - `POST https://api.mcp.ai/api/pagerduty/list/field/options/on/a/custom/field` — List field options 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 su - body: { field_id: string, type_id_or_name: string } - `POST https://api.mcp.ai/api/pagerduty/list/incident/status/update/subscribers` — Retrieves a list of subscribers to status updates for a specific incident in pagerduty. this endpoint allows you to see all users or services that are currently subscribed to receive notifications abo - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/list/incident/type/custom/fields` — List the custom fields 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 featu - body: { include?: string, type_id_or_name: string } - `POST https://api.mcp.ai/api/pagerduty/list/incident/types` — List the available incident types incident types are a feature which will allow customers to categorize incidents, such as a security incident, a major incident, or a fraud incident. these can be filt - body: { filter?: string } - `POST https://api.mcp.ai/api/pagerduty/list/licenses` — The listlicenses endpoint retrieves a comprehensive list of all licenses associated with the authenticated pagerduty account. this tool is essential for administrators and account managers who need to - `POST https://api.mcp.ai/api/pagerduty/list/supporting/service/impacts` — Retrieves information about the impacts of supporting services on a specific business service in pagerduty. this endpoint is used to understand the relationships and dependencies between a primary bus - body: { id: string, ids?: string, additional__fields?: string } - `POST https://api.mcp.ai/api/pagerduty/list/templates` — Retrieves a list of templates available in the pagerduty system. templates are pre-defined configurations used for creating alerts, notifications, and other automated processes within pagerduty. this - body: { limit?: integer, query?: string, total?: boolean, offset?: integer, sort_by?: string, template_type?: string } - `POST https://api.mcp.ai/api/pagerduty/list/workflow/integration/connections` — List all workflow integration connections for a specific workflow integration. scoped oauth requires: `workflow integrations:connections.read` - body: { name?: string, limit?: integer, cursor?: string, integration_id: string } - `POST https://api.mcp.ai/api/pagerduty/list/workflow/integrations` — List available workflow integrations. scoped oauth requires: `workflow integrations.read` - body: { limit?: integer, cursor?: string, include_deprecated?: boolean } - `POST https://api.mcp.ai/api/pagerduty/manage/cache/variables/for/event/service` — Creates a new cache variable for a specific service in pagerduty's event orchestrations. this endpoint allows you to define a cache variable that can store either the most recent value from an event f - body: { service_id: string, cache__variable__id?: string, cache__variable__name?: string, cache__variable__disabled?: boolean, cache__variable__conditions?: object[], cache__variable__created__at?: string, cache__variable__updated__at?: string, cache__variable__configuration?: object, cache__variable__created__by__id?: string, cache__variable__updated__by__id?: string, cache__variable__created__by__self?: string, cache__variable__created__by__type?: string, cache__variable__updated__by__self?: string, cache__variable__updated__by__type?: string } - `POST https://api.mcp.ai/api/pagerduty/merge/source/incidents/into/target/incident` — Merges multiple source incidents into a target incident in pagerduty's incident management system. this endpoint allows users to consolidate related or duplicate incidents into a single, primary incid - body: { id: string, source_incidents: string[] } - `POST https://api.mcp.ai/api/pagerduty/migrate/integration/between/orchestrations` — This endpoint facilitates the migration of an integration from one event orchestration to another within pagerduty. it allows users to reassign an existing integration to a different event orchestrati - body: { id: string, source_id: string, source_type: string, integration_id: string } - `POST https://api.mcp.ai/api/pagerduty/modify/entity/tags` — This endpoint allows you to modify the tags associated with a specific entity in pagerduty. it provides functionality to both add new tags and remove existing ones in a single api call. the endpoint i - body: { id: string, add?: object[], remove?: object[], entity_type: string } - `POST https://api.mcp.ai/api/pagerduty/pagerduty/aggregate/incident/metrics/with/filters` — 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 operatio - body: { order?: string, order_by?: string, time_zone?: string, aggregate_unit?: string, filters__major?: boolean, filters__urgency?: string, filters__team__ids?: string[], filters__service__ids?: string[], filters__priority__ids?: string[], filters__priority__names?: string[], filters__created__at__end?: string, filters__pd__advance__used?: boolean, filters__created__at__start?: string, filters__min__ackowledgements?: integer, filters__escalation__policy__ids?: string[], filters__min__manual__escalations?: integer, filters__min__timeout__escalations?: integer } - `POST https://api.mcp.ai/api/pagerduty/ping/webhook/subscription` — The pingwebhooksubscription endpoint sends a test post request to a specified webhook subscription in your pagerduty account. this tool is used to verify that a webhook subscription is correctly confi - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/post/account/subscription/for/business/service` — This endpoint creates or updates an account subscription for a specific business service in pagerduty. it allows users to manage subscription settings, such as notification preferences or service-leve - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/post/alert/grouping/settings` — Creates a new alert grouping setting in pagerduty, defining how alerts will be automatically grouped into incidents based on specified configurations. this endpoint allows users to set up intelligent - body: { alert__grouping__setting__id?: string, alert__grouping__setting__name?: string, alert__grouping__setting__type?: string, alert__grouping__setting__config?: object, alert__grouping__setting__services?: string[], alert__grouping__setting__created__at?: string, alert__grouping__setting__description?: string, alert__grouping__setting__updated__at?: string } - `POST https://api.mcp.ai/api/pagerduty/post/analytic/metrics/on/escalation/policies` — Retrieves and aggregates analytics metrics for incidents related to escalation policies in pagerduty. this endpoint allows for detailed filtering and customization of incident data, enabling users to - body: { order?: string, order_by?: string, time_zone?: string, aggregate_unit?: string, filters__major?: boolean, filters__urgency?: string, filters__team__ids?: string[], filters__service__ids?: string[], filters__priority__ids?: string[], filters__priority__names?: string[], filters__created__at__end?: string, filters__pd__advance__used?: boolean, filters__created__at__start?: string, filters__min__ackowledgements?: integer, filters__escalation__policy__ids?: string[], filters__min__manual__escalations?: integer, filters__min__timeout__escalations?: integer } - `POST https://api.mcp.ai/api/pagerduty/post/analytics/metrics/responder/filters` — The analyzerespondermetrics endpoint aggregates and analyzes responder performance metrics for pagerduty incidents. it provides insights into response times, efficiency, and workload distribution. thi - body: { order?: string, order_by?: string, time_zone?: string, filters__urgency?: string, filters__team__ids?: string[], filters__priority__ids?: string[], filters__responder__ids?: string[], filters__priority__names?: string[], filters__date__range__end?: string, filters__date__range__start?: string } - `POST https://api.mcp.ai/api/pagerduty/post/change/events` — Creates a new change event in the pagerduty system. this endpoint allows you to record and track significant changes or updates within your infrastructure or services. use this when you want to log im - `POST https://api.mcp.ai/api/pagerduty/post/event/orchestration/cache/variables` — Creates a new cache variable within a pagerduty event orchestration. this endpoint allows you to define a cache variable that can store dynamic data related to events, either based on recent values ex - body: { id: string, cache__variable__id?: string, cache__variable__name?: string, cache__variable__disabled?: boolean, cache__variable__conditions?: object[], cache__variable__created__at?: string, cache__variable__updated__at?: string, cache__variable__configuration?: object, cache__variable__created__by__id?: string, cache__variable__updated__by__id?: string, cache__variable__created__by__self?: string, cache__variable__created__by__type?: string, cache__variable__updated__by__self?: string, cache__variable__updated__by__type?: string } - `POST https://api.mcp.ai/api/pagerduty/post/incident/metrics` — This endpoint retrieves analytics metrics for responder teams based on incident data in pagerduty. it allows for detailed filtering and customization of the data set, enabling users to analyze team an - body: { order?: string, order_by?: string, time_zone?: string, filters__urgency?: string, filters__team__ids?: string[], filters__priority__ids?: string[], filters__responder__ids?: string[], filters__priority__names?: string[], filters__date__range__end?: string, filters__date__range__start?: string } - `POST https://api.mcp.ai/api/pagerduty/post/incident/metrics/with/filters` — This endpoint retrieves and aggregates analytics metrics for incidents across all teams in pagerduty. it allows users to apply various filters and parameters to analyze incident data, such as creation - body: { order?: string, order_by?: string, time_zone?: string, aggregate_unit?: string, filters__major?: boolean, filters__urgency?: string, filters__team__ids?: string[], filters__service__ids?: string[], filters__priority__ids?: string[], filters__priority__names?: string[], filters__created__at__end?: string, filters__pd__advance__used?: boolean, filters__created__at__start?: string, filters__min__ackowledgements?: integer, filters__escalation__policy__ids?: string[], filters__min__manual__escalations?: integer, filters__min__timeout__escalations?: integer } - `POST https://api.mcp.ai/api/pagerduty/post/incident/note/using/id` — Adds a new note to an existing incident in pagerduty. this endpoint allows users to append additional information, updates, or comments to a specific incident identified by its unique id. it's particu - body: { id: string, note__content?: string } - `POST https://api.mcp.ai/api/pagerduty/post/incident/status/update` — Posts a status update for a specific incident in pagerduty. this endpoint allows you to add new information or progress reports to an ongoing incident, keeping stakeholders informed about the current - body: { id: string, message: string, subject?: string, html_message?: string } - `POST https://api.mcp.ai/api/pagerduty/post/incidents/analytics/with/filters` — The analyzerawincidents endpoint retrieves and analyzes raw incident data from pagerduty. it allows users to fetch detailed information about incidents with various filtering options. this endpoint is - body: { limit?: integer, order?: string, order_by?: string, time_zone?: string, ending_before?: string, filters__major?: boolean, starting_after?: string, filters__urgency?: string, filters__team__ids?: string[], filters__service__ids?: string[], filters__priority__ids?: string[], filters__updated__after?: string, filters__priority__names?: string[], filters__created__at__end?: string, filters__created__at__start?: string } - `POST https://api.mcp.ai/api/pagerduty/post/incidents/metrics/filtered/by/service` — The analyzeincidentmetrics endpoint aggregates and analyzes incident data for pagerduty services based on specified filters and parameters. it allows users to generate detailed reports and insights on - body: { order?: string, order_by?: string, time_zone?: string, aggregate_unit?: string, filters__major?: boolean, filters__urgency?: string, filters__team__ids?: string[], filters__service__ids?: string[], filters__priority__ids?: string[], filters__priority__names?: string[], filters__created__at__end?: string, filters__pd__advance__used?: boolean, filters__created__at__start?: string, filters__min__ackowledgements?: integer, filters__escalation__policy__ids?: string[], filters__min__manual__escalations?: integer, filters__min__timeout__escalations?: integer } - `POST https://api.mcp.ai/api/pagerduty/post/responder/incidents/with/filters` — Retrieves a list of incidents associated with a specific responder in the pagerduty incident management system. this endpoint allows for detailed filtering and pagination of incident data, making it i - body: { limit?: integer, order?: string, order_by?: string, time_zone?: string, responder_id: string, ending_before?: string, filters__major?: boolean, starting_after?: string, filters__urgency?: string, filters__team__ids?: string[], filters__service__ids?: string[], filters__priority__ids?: string[], filters__priority__names?: string[], filters__created__at__end?: string, filters__created__at__start?: string } - `POST https://api.mcp.ai/api/pagerduty/post/service/automation/action` — This endpoint adds a service to an existing automation action in pagerduty. it allows users to associate a specific service with an automation action, enabling the action to be applied to incidents or - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/post/team/notification/subscription` — Creates notification subscriptions for a specific team in pagerduty. this endpoint allows you to subscribe a team to receive notifications for one or more incidents or business services. use this when - body: { id: string, subscribables: object[] } - `POST https://api.mcp.ai/api/pagerduty/post/team/to/runner` — This endpoint adds a team to an automation action runner in pagerduty. it allows you to associate a specific team with a runner, enabling better organization and management of automation processes wit - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/preview/schedule/object` — The preview schedule endpoint allows you to simulate and visualize a pagerduty schedule configuration before actually creating or updating it. this tool is essential for validating complex on-call rot - body: { since?: string, until?: string, overflow?: boolean } - `POST https://api.mcp.ai/api/pagerduty/render/template/for/incident` — Renders a specific template for a given incident in pagerduty. this endpoint allows you to generate a formatted report or message based on a pre-defined template and the provided incident information. - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/abilities/list` — Retrieves a list of abilities or capabilities available in the pagerduty system. this endpoint allows users to query and understand the features and functionalities they can access or perform within p - `POST https://api.mcp.ai/api/pagerduty/retrieve/ability/by/id` — Retrieves detailed information about a specific ability (feature capability) associated with a pagerduty account using its unique identifier. this endpoint allows users to query the system for the sta - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/action/services/by/id` — Retrieves a list of services associated with a specific automation action in pagerduty. this endpoint allows users to fetch all services that are linked to a particular automation action, providing in - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/active/service/event/by/id` — Retrieves the active event orchestration configuration for a specific pagerduty service. this endpoint allows you to fetch the current rules and settings that determine how incidents are created and r - body: { service_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/addon/by/id` — Retrieves detailed information about a specific addon installed on a pagerduty account. this endpoint allows users to fetch the current configuration, status, and other relevant details of an addon wi - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/alert/grouping/settings/by/id` — Retrieves the alert grouping settings for a specific configuration identified by its unique id in pagerduty. this endpoint allows users to access detailed information about how alerts are grouped for - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/automation/action/invocation/by/id` — Retrieves detailed information about a specific automation action invocation in pagerduty. this endpoint allows you to fetch the current state, results, and metadata of a previously executed automatio - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/automation/action/invocations` — Retrieves a list of automation action invocations from the pagerduty incident management platform. this endpoint allows users to query and review the history of automated actions that have been execut - body: { action_id?: string, incident_id?: string, invocation_state?: string, not_invocation_state?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/automation/action/runner/teams` — Retrieves detailed information about a specific team associated with an automation actions runner in pagerduty. this endpoint is used to get insights into the relationship between a runner and a parti - body: { id: string, team_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/automation/service/action` — Retrieves information about how a specific automation action is associated with a particular service in pagerduty. this endpoint allows users to query the relationship between an automation action and - body: { id: string, service_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/business/service/by/id` — Retrieves detailed information about a specific business service in pagerduty using its unique identifier. this endpoint allows users to fetch the current configuration, settings, and metadata associa - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/business/service/dependencies` — Retrieves the service dependencies for a specific business service in pagerduty. this endpoint allows you to fetch a list of services that are dependent on or related to the specified business service - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/business/service/impactors` — Retrieves a list of impactors currently affecting business services in pagerduty. impactors are entities or events that have the potential to negatively impact the performance, availability, or functi - body: { ids?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/business/service/impacts` — Retrieves the impacts of a specific incident on business services within pagerduty. this endpoint allows users to assess the scope and severity of an ongoing incident by providing detailed information - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/business/services` — The listbusinessservices endpoint retrieves a comprehensive list of all business services configured within a pagerduty account. this get operation provides an overview of the critical business functi - body: { limit?: integer, total?: boolean, offset?: integer } - `POST https://api.mcp.ai/api/pagerduty/retrieve/change/event/by/id` — Retrieves detailed information about a specific change event in pagerduty using its unique identifier. this endpoint is crucial for tracking and auditing changes within your incident management workfl - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/change/event/information` — Retrieves a list of change events from the pagerduty system within a specified time range. change events represent notifications or updates that occur within a pagerduty account, such as modifications - body: { limit?: integer, since?: string, total?: boolean, until?: string, offset?: integer, team__ids?: string[], integration__ids?: string[] } - `POST https://api.mcp.ai/api/pagerduty/retrieve/current/user/info` — Retrieves the profile information of the currently authenticated user in the pagerduty system. this endpoint provides access to personal details, settings, and account information associated with the - body: { include?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/entity/tags/by/id` — Retrieves the tags associated with a specific entity in the pagerduty system. this endpoint allows you to fetch all tags that have been assigned to a particular resource, such as a user, team, service - body: { id: string, limit?: integer, total?: boolean, offset?: integer, entity_type: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/entity/tags/by/id/and/type` — Retrieves the tags associated with a specific entity in pagerduty. this endpoint allows you to fetch all tags linked to a particular resource, such as an incident, service, user, team, or escalation p - body: { id: string, limit?: integer, total?: boolean, offset?: integer, entity_type: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/event/orchestration/router/by/id` — Retrieves the router configuration for a specific event orchestration in pagerduty. this endpoint allows you to fetch detailed information about how incidents and events are routed within a particular - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/extension/by/id` — Retrieves detailed information about a specific extension in pagerduty. this endpoint allows users to fetch the configuration and status of an individual extension by providing its unique identifier. - body: { id: string, include?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/extension/list` — Retrieves a list of all extensions associated with the authenticated pagerduty account. extensions are additional features or integrations that enhance pagerduty's functionality, such as custom notifi - body: { limit?: integer, query?: string, total?: boolean, offset?: integer, include?: string, extension_object_id?: string, extension_schema_id?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/incident/by/incident/id` — Retrieves detailed information about a specific incident in pagerduty using its unique identifier. this endpoint allows users to access comprehensive data about an individual incident, including its c - body: { id: string, include?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/incident/custom/field/values` — Retrieves the custom field values associated with a specific incident in pagerduty. this endpoint allows users to access additional metadata that has been added to an incident, providing more context - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/incident/custom/fields` — Retrieves a list of custom fields associated with incidents in pagerduty. custom fields are additional data points that can be added to incidents to provide more detailed information tailored to speci - body: { include?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/incident/field/options` — Retrieves the available field options for a specific custom field associated with incidents in pagerduty. this endpoint allows users to fetch the predefined set of values that can be assigned to a par - body: { field_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/incident/workflow/by/id` — Retrieves detailed information about a specific incident workflow in pagerduty. this endpoint allows users to fetch the configuration, steps, and other relevant details of an incident workflow based o - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/incident/workflow/triggers` — Retrieves a list of triggers associated with incident workflows in pagerduty. this endpoint allows you to fetch information about the conditions or events that initiate automated incident response pro - body: { limit?: integer, cursor?: string, sort_by?: string, service_id?: string, incident_id?: string, is_disabled?: boolean, workflow_id?: string, trigger_type?: string, workflow_name_contains?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/integration/by/service/id` — Retrieves detailed information about a specific integration associated with a particular service in pagerduty. this endpoint allows you to fetch the configuration and status of an integration, which c - body: { id: string, include?: string, integration_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/license/allocations` — Retrieves the current license allocations for the pagerduty account. this endpoint provides an overview of how licenses are distributed across users, teams, or other entities within the organization. - body: { limit?: integer, offset?: integer } - `POST https://api.mcp.ai/api/pagerduty/retrieve/list/of/services` — Retrieves a list of services configured in the pagerduty account. this endpoint allows you to fetch details about various services set up for incident management and alerting. it's particularly useful - body: { name?: string, limit?: integer, query?: string, total?: boolean, offset?: integer, include?: string, sort_by?: string, team__ids?: string[], time_zone?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/log/entry/by/id` — Retrieves detailed information about a specific log entry in the pagerduty system. this endpoint is used to access the complete record of an event or action that occurred within pagerduty, such as inc - body: { id: string, include?: string, time_zone?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/maintenance/windows` — Retrieves a list of maintenance windows from the pagerduty incident management platform. maintenance windows are scheduled periods during which alerts and notifications for specified services are supp - body: { limit?: integer, query?: string, total?: boolean, filter?: string, offset?: integer, include?: string, team__ids?: string[], service__ids?: string[] } - `POST https://api.mcp.ai/api/pagerduty/retrieve/notes/for/incident` — Retrieves all notes associated with a specific incident in pagerduty. this endpoint allows users to access the complete history of comments, updates, and additional information added to an incident th - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/notifications` — Retrieves notifications from the pagerduty system. this endpoint allows users to fetch information about alerts, incidents, and other important notifications generated within the pagerduty platform. i - body: { limit?: integer, since: string, total?: boolean, until: string, filter?: string, offset?: integer, include?: string, time_zone?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/oncall/handoff/notification/rule` — Retrieves detailed information about a specific on-call handoff notification rule for a given user in pagerduty. this endpoint is crucial for managing and reviewing the notification settings that gove - body: { id: string, oncall_handoff_notification_rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/oncall/handoff/notification/rules` — Retrieves the on-call handoff notification rules for a specific user in pagerduty. this endpoint allows you to fetch the configured rules that determine how and when a user is notified about on-call s - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/oncall/list` — Retrieves the current on-call information for your pagerduty account. this endpoint provides a comprehensive view of who is currently on-call across various schedules and escalation policies. it's par - body: { limit?: integer, since?: string, total?: boolean, until?: string, offset?: integer, include?: string, earliest?: boolean, time_zone?: string, user__ids?: string[], schedule__ids?: string[], escalation__policy__ids?: string[] } - `POST https://api.mcp.ai/api/pagerduty/retrieve/past/incidents` — Retrieves a list of past incidents related to a specific incident in pagerduty. this endpoint allows users to explore the historical context of an incident by fetching previous occurrences or related - body: { id: string, limit?: integer, total?: boolean } - `POST https://api.mcp.ai/api/pagerduty/retrieve/postmortem/by/id` — Retrieves the postmortem analysis for a specific post on a pagerduty status page. this endpoint allows users to access detailed information about an incident after it has been resolved, including root - body: { id: string, post_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/response/play/by/id` — Retrieves detailed information about a specific response play in the pagerduty incident management system. this endpoint allows users to access the configuration and actions associated with a predefin - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/rule/by/service/id` — Retrieves a specific rule associated with a particular service in pagerduty. this endpoint allows you to access detailed information about a single rule, including its configuration and conditions, wi - body: { id: string, rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/rules/for/service/id` — Retrieves all rules associated with a specific pagerduty service. this endpoint allows users to fetch the set of rules that define when and how incidents are triggered for a particular service. it's e - body: { id: string, limit?: integer, total?: boolean, offset?: integer, include?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/rules/from/ruleset/by/id` — Retrieves a list of all rules associated with a specific ruleset in pagerduty. this endpoint is used to examine the configuration of event routing within a particular ruleset, allowing users to review - body: { id: string, limit?: integer, total?: boolean, offset?: integer } - `POST https://api.mcp.ai/api/pagerduty/retrieve/ruleset/by/id` — Retrieves detailed information about a specific ruleset in pagerduty using its unique identifier. this endpoint allows you to fetch the complete configuration and settings of a single ruleset, which i - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/ruleset/list` — Retrieves a list of rulesets from the pagerduty system. rulesets are collections of event rules that define how incidents are managed and alerts are configured. this endpoint allows you to view all av - body: { limit?: integer, total?: boolean, offset?: integer } - `POST https://api.mcp.ai/api/pagerduty/retrieve/schedule/audit/records/by/id` — Retrieves the audit records for a specific pagerduty schedule. this endpoint allows you to access a comprehensive log of all changes made to the specified schedule, including modifications to on-call - body: { id: string, limit?: integer, since?: string, until?: string, cursor?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/schedule/by/id` — Retrieves detailed information about a specific schedule in pagerduty using its unique identifier. this endpoint is essential for viewing the configuration of an existing on-call schedule, including i - body: { id: string, since?: string, until?: string, overflow?: boolean, time_zone?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/schedule/override/by/id` — Retrieves the list of overrides for a specific schedule in pagerduty. this endpoint allows users to fetch temporary modifications to the regular on-call rotation, providing insight into any manual adj - body: { id: string, since: string, until: string, editable?: boolean, overflow?: boolean } - `POST https://api.mcp.ai/api/pagerduty/retrieve/service/audit/records/by/id` — Retrieves the audit records for a specific pagerduty service. this endpoint allows you to fetch a historical log of all configuration changes made to the service, providing transparency and accountabi - body: { id: string, limit?: integer, since?: string, until?: string, cursor?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/service/by/id` — Retrieves detailed information about a specific pagerduty service using its unique identifier. this endpoint allows users to access configuration details, integration settings, and other relevant info - body: { id: string, include?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/service/change/events/by/id` — Retrieves change events associated with a specific pagerduty service. this endpoint allows you to fetch informational updates about recent changes such as code deploys, system configuration modificati - body: { id: string, limit?: integer, since?: string, total?: boolean, until?: string, offset?: integer, team__ids?: string[], integration__ids?: string[] } - `POST https://api.mcp.ai/api/pagerduty/retrieve/service/impacts/from/status/dashboards` — Retrieves the service impacts associated with a specific status dashboard in pagerduty. this endpoint allows users to fetch detailed information about how incidents are affecting various services with - body: { id: string, additional__fields?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/service/status/by/id` — Retrieves a list of services associated with a specific status page in pagerduty. this endpoint is used to fetch detailed information about the services that are being monitored and displayed on a par - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/service/status/page` — Retrieves detailed information about a specific service associated with a particular status page in pagerduty. this endpoint is used to fetch the current status, configuration, and other relevant deta - body: { id: string, service_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/standards/list` — Retrieves the current set of standards defined in the pagerduty account. standards in pagerduty refer to the policies and best practices for incident response and alerting. this endpoint allows users - body: { active?: boolean, resource_type?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/standards/scores` — Retrieves the standards scores for a specific resource in pagerduty. this endpoint allows users to fetch performance or compliance metrics for a given resource type (such as incidents, services, or te - body: { id: string, resource_type: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/standards/scores/by/resource/type` — Retrieves the standards scores for a specified resource type in pagerduty. this endpoint allows users to access performance metrics and evaluations based on predefined standards for different componen - body: { ids: string[], resource_type: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/status/dashboard/by/slug` — Retrieves detailed information about a specific pagerduty status dashboard using its url slug. this endpoint allows users to fetch the current state, components, and other relevant data associated wit - body: { url_slug: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/status/dashboards/information` — Retrieves a list of status dashboards and their associated information from the pagerduty system. this endpoint provides a comprehensive overview of the current operational status, performance metrics - `POST https://api.mcp.ai/api/pagerduty/retrieve/status/page/post` — Retrieves all posts associated with a specific status page in pagerduty. this endpoint allows users to fetch updates, messages, and status information that have been posted to a particular status page - body: { id: string, status?: string[], post_type?: string, reviewed_status?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/status/page/severities/by/id` — Retrieves the list of severities associated with a specific status page in pagerduty. this endpoint allows users to fetch the current severity levels configured for a particular status page, which is - body: { id: string, post_type?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/status/page/subscription/by/id` — Retrieves a list of subscriptions associated with a specific pagerduty status page. this endpoint allows users to fetch all current subscriptions for a given status page, enabling them to monitor who - body: { id: string, status?: string, channel?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/status/pages/status` — Retrieves the current statuses for a specified pagerduty status page. this endpoint allows users to fetch real-time status information for a given status page, providing up-to-date details on service - body: { id: string, post_type?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/tag/by/id` — Retrieves detailed information about a specific tag in the pagerduty system using its unique identifier. this endpoint allows users to fetch the properties and metadata associated with a particular ta - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/tags` — Retrieves a list of all tags currently used within the pagerduty account. this endpoint provides a comprehensive view of the tags used for categorization and labeling of incidents across the system. i - body: { limit?: integer, query?: string, total?: boolean, offset?: integer } - `POST https://api.mcp.ai/api/pagerduty/retrieve/team/audit/records` — Retrieves the audit records for a specific team in pagerduty. this endpoint allows users to access a detailed history of configuration changes made to the team, including modifications to team members - body: { id: string, limit?: integer, since?: string, until?: string, cursor?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/team/details/by/id` — Retrieves detailed information about a specific team in pagerduty based on the provided team id. this endpoint allows users to fetch comprehensive data about a team, including its members, roles, and - body: { id: string, include?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/team/list` — The listteams endpoint retrieves a list of teams within a pagerduty account. it provides an overview of all teams or a filtered subset based on the optional query parameter. this endpoint is useful fo - body: { limit?: integer, query?: string, total?: boolean, offset?: integer } - `POST https://api.mcp.ai/api/pagerduty/retrieve/technical/service/details` — Retrieves detailed information about a specific technical service and its dependencies within the pagerduty incident management platform. this endpoint is used to fetch comprehensive data about a sing - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/template/fields` — Retrieves the available fields for pagerduty templates. this endpoint provides a comprehensive list of all possible fields that can be used when creating or modifying templates within the pagerduty pl - `POST https://api.mcp.ai/api/pagerduty/retrieve/unrouted/event/orchestration/by/id` — Retrieves a list of unrouted events for a specific event orchestration in pagerduty. this endpoint is used to identify and review events that have not yet been assigned or processed within the designa - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/user/audit/records/by/id` — Retrieves the audit records for a specific user in the pagerduty system. this endpoint allows you to access a historical log of activities and changes associated with the user, providing valuable insi - body: { id: string, limit?: integer, since?: string, until?: string, cursor?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/user/by/id` — Retrieves detailed information about a specific user in the pagerduty platform using their unique identifier. this endpoint is used to fetch user account details, such as contact information, role ass - body: { id: string, include?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/user/contact/methods/via/id` — Retrieves all contact methods associated with a specific user in pagerduty. this endpoint allows you to fetch the various ways a user can be contacted during an incident, such as email addresses, phon - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/user/license/information` — Retrieves the license information for a specific user in the pagerduty system. this endpoint allows you to check the current licensing status, type, and any associated details for a given user. it sho - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/user/notification/rule` — Retrieves a specific notification rule for a given user in pagerduty. this endpoint allows you to fetch detailed information about how and when a particular user receives alerts and notifications. it' - body: { id: string, include?: string, notification_rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/user/notification/rules` — Retrieves the notification rules for a specific user in pagerduty. this endpoint allows you to fetch all configured notification rules associated with a given user, providing insight into how and when - body: { id: string, include?: string, urgency?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/user/status/update/notification/rule` — Retrieves a specific status update notification rule for a given user in pagerduty. this endpoint allows you to fetch detailed information about how and when a particular user receives notifications f - body: { id: string, include?: string, status_update_notification_rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/users/by/schedule/id` — Retrieves a list of users associated with a specific pagerduty schedule. this endpoint is essential for managing on-call rotations and understanding who is responsible for incident response during dif - body: { id: string, since?: string, until?: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/users/list` — Retrieves a list of users from the pagerduty system. this endpoint allows you to fetch information about multiple users in your pagerduty account, which can be useful for user management, generating r - body: { limit?: integer, query?: string, total?: boolean, offset?: integer, include?: string, team__ids?: string[] } - `POST https://api.mcp.ai/api/pagerduty/retrieve/vendor/by/id` — Retrieves detailed information about a specific vendor integrated with pagerduty. this endpoint allows users to access comprehensive data about a vendor, including its name, type of integration, capab - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/retrieve/webhook/subscriptions` — Retrieves a list of all webhook subscriptions associated with the authenticated pagerduty account. this endpoint allows users to view and manage their existing webhook configurations, which are used t - body: { limit?: integer, total?: boolean, offset?: integer, filter_id?: string, filter_type?: string } - `POST https://api.mcp.ai/api/pagerduty/send/responder/requests/for/incidents` — This endpoint allows you to send responder requests for a specific incident in pagerduty. it is used to request additional help or notify specific users or escalation policies about an ongoing inciden - body: { id: string, message: string, requester_id: string, responder_request_targets: string } - `POST https://api.mcp.ai/api/pagerduty/set/business/service/impact/status` — This endpoint updates the impact status of a specific incident on a particular business service in pagerduty. it allows you to either set a business service as impacted by an incident or remove the im - body: { id: string, relation: string, business_service_id: string } - `POST https://api.mcp.ai/api/pagerduty/set/global/priority/threshold` — Sets the global priority threshold for business services in pagerduty, determining which incidents can impact these services based on their priority level. this endpoint allows you to configure the mi - body: { global__threshold__id?: string, global__threshold__order?: integer } - `POST https://api.mcp.ai/api/pagerduty/snooze/incident/by/duration` — This endpoint allows you to snooze a specific incident in pagerduty for a defined duration. it temporarily pauses alerts and notifications for the incident, after which it automatically returns to an - body: { id: string, duration: integer } - `POST https://api.mcp.ai/api/pagerduty/subscribe/entities/to/business/services` — This endpoint allows you to subscribe users or teams to a specific business service in pagerduty. it enables you to add multiple subscribers in a single request, streamlining the process of setting up - body: { id: string, subscribers: object[] } - `POST https://api.mcp.ai/api/pagerduty/subscribe/entities/to/incident/status/updates` — Subscribes specified users or teams to receive status updates for a particular incident in pagerduty. this endpoint allows you to add multiple subscribers at once, ensuring that relevant parties are k - body: { id: string, subscribers: object[] } - `POST https://api.mcp.ai/api/pagerduty/subscribe/to/user/notifications` — Creates notification subscriptions for a specific user in pagerduty. this endpoint allows you to subscribe a user to multiple incidents or business services in a single api call. it's particularly use - body: { id: string, subscribables: object[] } - `POST https://api.mcp.ai/api/pagerduty/unsubscribe/business/service/entity` — This endpoint unsubscribes specified users or teams from receiving notifications for a particular business service in pagerduty. it allows bulk unsubscription of multiple entities in a single api call - body: { id: string, subscribers: object[] } - `POST https://api.mcp.ai/api/pagerduty/unsubscribe/from/incident/status/updates` — Unsubscribes specified users or teams from receiving status updates for a particular incident in pagerduty. this endpoint is used when certain entities no longer need to be notified about changes to a - body: { id: string, subscribers: object[] } - `POST https://api.mcp.ai/api/pagerduty/unsubscribe/team/notification/subscriptions` — Unsubscribes a team from notifications for specific incidents or business services in pagerduty. this endpoint is used to stop a team from receiving alerts and updates about particular entities. it's - body: { id: string, subscribables: object[] } - `POST https://api.mcp.ai/api/pagerduty/unsubscribe/user/notification/subscriptions` — This endpoint allows unsubscribing a user from notifications for specific incidents or business services in pagerduty. it's used to modify a user's notification preferences, removing them from receivi - body: { id: string, subscribables: object[] } - `POST https://api.mcp.ai/api/pagerduty/update/a/custom/field/for/an/incident/type` — Update 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 featur - body: { field_id: string, field__enabled?: boolean, type_id_or_name: string, field__description?: string, field__display__name?: string, field__default__value?: string } - `POST https://api.mcp.ai/api/pagerduty/update/a/field/option/for/a/custom/field` — Update a field option for a custom field. > ### 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 - body: { field_id: string, field_option_id: string, type_id_or_name: string, field__option__data__value?: string, field__option__data__data__type?: string } - `POST https://api.mcp.ai/api/pagerduty/update/a/trigger` — Update an existing incident workflow trigger scoped oauth requires: `incident workflows.write` - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/add/on/by/id` — Updates an existing add-on in pagerduty with new properties. this endpoint allows you to modify the type, name, and source url of a specific add-on identified by its unique id. it's used when you need - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/alert/grouping/settings/by/id` — This endpoint allows you to update an existing alert grouping setting in pagerduty. alert grouping settings define how alerts are automatically grouped into incidents, helping to streamline incident m - body: { id: string, alert__grouping__setting__id?: string, alert__grouping__setting__name?: string, alert__grouping__setting__type?: string, alert__grouping__setting__config?: object, alert__grouping__setting__services?: string[], alert__grouping__setting__created__at?: string, alert__grouping__setting__description?: string, alert__grouping__setting__updated__at?: string } - `POST https://api.mcp.ai/api/pagerduty/update/alert/in/incident` — Updates the status of a specific alert within an incident in pagerduty. this endpoint allows you to modify an alert's status, primarily to mark it as resolved. it's crucial for managing the lifecycle - body: { id: string, alert_id: string, alert__status?: string, alert__incident__id?: string, alert__incident__type?: string } - `POST https://api.mcp.ai/api/pagerduty/update/an/incident/type` — Update an 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. > - body: { type_id_or_name: string, incident__type__enabled?: boolean, incident__type__description?: string, incident__type__display__name?: string } - `POST https://api.mcp.ai/api/pagerduty/update/automation/runner/info` — This endpoint allows you to update an existing automation action runner in pagerduty. it is used to modify the properties of a runner, such as its name, description, and, for runbook runners, the runb - body: { id: string, runner: object } - `POST https://api.mcp.ai/api/pagerduty/update/business/service/by/id` — This endpoint allows you to update an existing business service in pagerduty. it is used to modify the details of a specific service, such as its name, description, point of contact, or the team respo - body: { id: string, business__service__name?: string, business__service__team__id?: string, business__service__description?: string, business__service__point__of__contact?: string } - `POST https://api.mcp.ai/api/pagerduty/update/change/event/by/id` — Updates an existing change event in pagerduty. this endpoint allows you to modify certain attributes of a change event, such as its summary or custom details. it's used when you need to amend or add i - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/custom/field/display/name` — This endpoint updates an existing custom field for incidents in pagerduty. it allows you to modify the display name, description, and default value of a custom field identified by its unique field id. - body: { field_id: string, field__description?: string, field__display__name?: string, field__default__value?: object } - `POST https://api.mcp.ai/api/pagerduty/update/custom/field/option` — Updates a specific field option for a custom field in pagerduty's incident management system. this endpoint allows you to modify the value of an existing field option, providing flexibility in managin - body: { field_id: string, field_option_id: string, field__option__id?: string, field__option__data?: object, field__option__type?: string, field__option__created__at?: string, field__option__updated__at?: string } - `POST https://api.mcp.ai/api/pagerduty/update/escalation/policy/by/id` — Updates an existing escalation policy in pagerduty with new settings and rules. this endpoint allows you to modify various aspects of an escalation policy, including its name, description, escalation - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/escalation/policy/for/team` — This endpoint updates an existing escalation policy for a specific team in pagerduty. it modifies incident escalation rules within the team context, crucial for maintaining up-to-date response workflo - body: { id: string, escalation_policy_id: string } - `POST https://api.mcp.ai/api/pagerduty/update/event/orchestration/by/id` — Updates an existing event orchestration in pagerduty. this endpoint allows you to modify the name, description, and team ownership of a specific orchestration identified by its id. it's used to refine - body: { id: string, orchestration__id?: string, orchestration__name?: string, orchestration__self?: string, orchestration__routes?: integer, orchestration__version?: string, orchestration__team__id?: string, orchestration__team__self?: string, orchestration__team__type?: string, orchestration__created__at?: string, orchestration__description?: string, orchestration__updated__at?: string, orchestration__integrations?: object[], orchestration__created__by__id?: string, orchestration__updated__by__id?: string, orchestration__created__by__self?: string, orchestration__created__by__type?: string, orchestration__updated__by__self?: string, orchestration__updated__by__type?: string } - `POST https://api.mcp.ai/api/pagerduty/update/event/orchestration/cache/variable` — This endpoint allows you to update an existing cache variable within a specific event orchestration in pagerduty. cache variables are used to store and manipulate dynamic data extracted from events, e - body: { id: string, cache_variable_id: string, cache__variable__id?: string, cache__variable__name?: string, cache__variable__disabled?: boolean, cache__variable__conditions?: object[], cache__variable__created__at?: string, cache__variable__updated__at?: string, cache__variable__configuration?: object, cache__variable__created__by__id?: string, cache__variable__updated__by__id?: string, cache__variable__created__by__self?: string, cache__variable__created__by__type?: string, cache__variable__updated__by__self?: string, cache__variable__updated__by__type?: string } - `POST https://api.mcp.ai/api/pagerduty/update/event/rule/by/id` — This endpoint allows you to update an existing event rule within a specified ruleset in pagerduty. event rules define conditions for matching events and actions to take when those conditions are met. - body: { id: string, rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/update/event/rule/for/service` — This endpoint allows you to update an existing event rule for a specific service in pagerduty. event rules are used to define how incoming events should be processed, including conditions for matching - body: { id: string, rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/update/extension/by/id` — Updates an existing extension in pagerduty. this endpoint allows you to modify the configuration of a previously created extension, such as a webhook or custom integration. you can update properties l - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/global/orchestration` — Update the global orchestration for an event orchestration. global orchestration rules allows you to create a set of event rules. these rules evaluate against all events sent to an event orchestration - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/incident/alerts` — This endpoint allows you to update the status of multiple alerts associated with a specific incident in pagerduty. it is particularly useful for bulk operations when you need to resolve or update the - body: { id: string, limit?: integer, total?: boolean, alerts: object[], offset?: integer } - `POST https://api.mcp.ai/api/pagerduty/update/incident/by/id` — The updateincident endpoint allows you to modify various attributes of an existing incident in pagerduty's incident management system. this put operation enables users to update incident status, prior - body: { id: string, incident__type?: string, incident__title?: string, incident__status?: string, incident__urgency?: string, incident__resolution?: string, incident__assignments?: string[], incident__escalation__level?: integer, incident__incident__type__id?: string, incident__incident__type__name?: string, incident__conference__bridge__conference__url?: string, incident__conference__bridge__conference__number?: string } - `POST https://api.mcp.ai/api/pagerduty/update/incident/custom/field/values` — This endpoint updates custom field values for a specific incident in pagerduty. it allows you to modify or add custom fields to provide additional context or information about the incident. the endpoi - body: { id: string, custom_fields: object[] } - `POST https://api.mcp.ai/api/pagerduty/update/incident/details` — This endpoint allows for bulk updating of multiple pagerduty incidents in a single api call. it can be used to modify various attributes of incidents such as status, priority, assignments, and more. t - body: { limit?: integer, total?: boolean, offset?: integer, incidents: string[] } - `POST https://api.mcp.ai/api/pagerduty/update/incident/workflow` — This endpoint updates an existing incident workflow in pagerduty by its unique identifier. it allows you to modify various aspects of the workflow, including its name, description, associated team, an - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/integration/by/id/and/integration/id` — Updates an existing integration for a specific pagerduty service. this endpoint allows you to modify the configuration of an integration, including its type, name, and various settings related to emai - body: { id: string, integration_id: string } - `POST https://api.mcp.ai/api/pagerduty/update/integration/label` — This endpoint updates the label (name) of an integration associated with a specific event orchestration in pagerduty. it allows users to rename integrations for better organization and clarity within - body: { id: string, integration_id: string, integration__label?: string } - `POST https://api.mcp.ai/api/pagerduty/update/log/entry/channel` — Updates the channel information for a specific log entry in pagerduty. this endpoint allows you to modify the details of how notifications are delivered for a particular log entry, while maintaining t - body: { id: string, channel__type?: string, channel__details?: string } - `POST https://api.mcp.ai/api/pagerduty/update/maintenance/window/by/id` — Updates an existing maintenance window in pagerduty's incident management system. this endpoint allows you to modify the details of a scheduled maintenance period, including its start and end times, a - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/oncall/handoff/notification/rule` — This endpoint updates an existing on-call handoff notification rule for a specific user in pagerduty. it allows you to modify the notification delay, handoff type, and contact method for the rule. use - body: { id: string, oncall_handoff_notification_rule_id: string, oncall__handoff__notification__rule__id?: string, oncall__handoff__notification__rule__handoff__type?: string, oncall__handoff__notification__rule__notify__advance__in__minutes?: integer } - `POST https://api.mcp.ai/api/pagerduty/update/orchestration/router/details` — Updates the configuration of an existing event orchestration router in pagerduty. this endpoint allows you to modify the rules and routing logic for incoming events, determining how they are directed - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/response/play/by/id` — Updates an existing response play in pagerduty's incident management system. this endpoint allows you to modify various aspects of a response play, including its name, description, associated team, su - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/ruleset/by/id` — Updates an existing ruleset in the pagerduty incident management system. this endpoint allows you to modify the name of a ruleset or change its team association. it's used when you need to adjust the - body: { id: string, ruleset__id?: string, ruleset__name?: string, ruleset__self?: string, ruleset__type?: string, ruleset__team__id?: string, ruleset__team__self?: string, ruleset__team__type?: string, ruleset__created__at?: string, ruleset__creator__id?: string, ruleset__updated__at?: string, ruleset__updater__id?: string, ruleset__creator__self?: string, ruleset__creator__type?: string, ruleset__routing__keys?: string[], ruleset__updater__self?: string, ruleset__updater__type?: string } - `POST https://api.mcp.ai/api/pagerduty/update/schedule/by/id` — The updateschedule endpoint modifies an existing on-call schedule in pagerduty. it updates the schedule's name, time zone, description, and layers. each layer defines a rotation pattern for on-call du - body: { id: string, overflow?: boolean } - `POST https://api.mcp.ai/api/pagerduty/update/service/by/id` — Updates an existing service in pagerduty with the provided configuration. this endpoint allows you to modify various aspects of a service, such as its name, description, escalation policy, incident ur - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/service/orchestration/active/status` — This endpoint updates the active status of a specific service orchestration in pagerduty. it allows you to activate or deactivate a service orchestration by setting its 'active' status. use this endpo - body: { active?: boolean, service_id: string } - `POST https://api.mcp.ai/api/pagerduty/update/standard/by/id` — Updates an existing standard in the pagerduty incident management platform. this endpoint allows you to modify various attributes of a standard, including its active status, filtering criteria, descri - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/status/page/post` — Updates an existing post update on a pagerduty status page. this endpoint allows you to modify the details of a specific post update, including its message, status, severity, impacted services, and no - body: { id: string, post_id: string, post_update_id: string, post__update__self?: string, post__update__type?: string, post__update__message?: string, post__update__post__id?: string, post__update__post__type?: string, post__update__status__id?: string, post__update__reported__at?: string, post__update__severity__id?: string, post__update__status__type?: string, post__update__severity__type?: string, post__update__impacted__services?: object[], post__update__notify__subscribers?: boolean, post__update__update__frequency__ms?: integer } - `POST https://api.mcp.ai/api/pagerduty/update/status/page/post/info` — Creates or updates a post update on a specific pagerduty status page. this endpoint allows you to add new information or modify existing updates related to an incident or maintenance event. use this w - body: { id: string, post_id: string, post__update__self?: string, post__update__type?: string, post__update__message?: string, post__update__post__id?: string, post__update__post__type?: string, post__update__status__id?: string, post__update__reported__at?: string, post__update__severity__id?: string, post__update__status__type?: string, post__update__severity__type?: string, post__update__impacted__services?: object[], post__update__notify__subscribers?: boolean, post__update__update__frequency__ms?: integer } - `POST https://api.mcp.ai/api/pagerduty/update/status/page/post/postmortem` — Updates or creates a postmortem for a specific post on a pagerduty status page. this endpoint allows users to add detailed analysis and insights about an incident after its resolution. it's primarily - body: { id: string, post_id: string, postmortem__type?: string, postmortem__message?: string, postmortem__post__id?: string, postmortem__post__type?: string, postmortem__notify__subscribers?: boolean } - `POST https://api.mcp.ai/api/pagerduty/update/status/page/post/resource` — This endpoint allows you to update an existing status page post on a specific pagerduty status page. it is used to modify the details of a post, such as its title, type (incident or maintenance), and - body: { id: string, post_id: string, post__type?: string, post__title?: string, post__ends__at?: string, post__post__type?: string, post__starts__at?: string, post__status__page__id?: string, post__status__page__type?: string } - `POST https://api.mcp.ai/api/pagerduty/update/team/by/id` — This endpoint allows you to update an existing team's information in pagerduty. it is used to modify team properties such as name, description, and access permissions (public/private). the endpoint sh - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/template/by/id` — The updatetemplate endpoint allows you to modify an existing status update template in pagerduty. this tool is used to customize notification templates for incident status updates, enabling consistent - body: { id: string, template__name?: string, template__description?: string, template__template__type?: string, template__templated__fields__message?: string, template__templated__fields__email__body?: string, template__templated__fields__email__subject?: string } - `POST https://api.mcp.ai/api/pagerduty/update/the/service/orchestration/for/a/service` — Update a service orchestration. a service orchestration allows you to create a set of event rules. the service orchestration evaluates events sent to this service against each of its rules, beginning - body: { service_id: string } - `POST https://api.mcp.ai/api/pagerduty/update/unrouted/orchestration/rules` — Updates the unrouted orchestration rules for a specific event orchestration in pagerduty. this endpoint allows you to define how events that don't match any service-specific rules should be handled. i - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/user/information` — This endpoint allows updating an existing user's information in pagerduty. it is used to modify various attributes of a user's profile, including their name, email, time zone, role, and other details. - body: { id: string } - `POST https://api.mcp.ai/api/pagerduty/update/user/notification/rule/by/id` — Updates a specific status update notification rule for a pagerduty user. this endpoint allows you to modify how a user receives notifications about incident status changes. it's used to change the con - body: { id: string, status_update_notification_rule_id: string } - `POST https://api.mcp.ai/api/pagerduty/update/user/role/on/team` — Updates the role of a specific user within a pagerduty team. this endpoint allows you to modify a user's permissions and responsibilities by changing their role in the team structure. use this when yo - body: { id: string, role?: string, user_id: string } - `POST https://api.mcp.ai/api/pagerduty/update/workflow/integration/connection` — Update an existing workflow integration connection. scoped oauth requires: `workflow integrations:connections.write` - body: { id: string, name: string, type?: string, teams?: object[], scopes?: string[], is_default?: boolean, external_id?: string, service_url?: string, integration_id: string, external_id_label?: string, health__is__healthy?: boolean, health__health__message?: string, health__last__checked__at?: string } ## More - Page: https://mcp.ai/pagerduty - Agent spec (llms.txt): https://mcp.ai/pagerduty/llms.txt - Postman collection: https://mcp.ai/pagerduty/postman.json