The MCP tool directory.

Creates a new Organization Domain.

Permanently deletes an organization domain. It cannot be undone.

Get the details of an existing organization domain.

Initiates verification process for an Organization Domain.

Creates an API key owned by the organization. Requires admin role.

Create a new API key for an organization.

Deletes an API key belonging to the organization. Requires admin role.

Returns all API keys belonging to the organization. Requires admin role. Key values are not included in the response.

Get a list of all API keys for an organization.

Get the unified view of audit log trail and stream configuration for an organization.

Get the configured event retention period for the given Organization.

Set the event retention period for the given Organization.

Creates a new organization in the current environment.

Permanently deletes an organization in the current environment. It cannot be undone.

Get the details of an existing organization by an [external identifier](/authkit/metadata/external-identifiers).

Get a list of all enabled feature flags for an organization.

Get the details of an existing organization.

Get a list of all of your existing organizations matching the criteria specified.

Updates an organization in the current environment.

This endpoint adds a service to an existing incident workflow trigger in PagerDuty. It allows you to associate a specific service with a trigger, enabling automated incident management processes for that service. Use this endpoint when you need to connect a service to an incident workflow, typically during the setup or modification of your incident response procedures. The endpoint requires the trigger's ID and the service's ID to make the association. It's important to note that this operation doesn't create new services or triggers, but rather links existing ones. Ensure that both the trigger and service exist in your PagerDuty account before making this call.

This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty. It allows for detailed filtering and customization of the analysis, enabling users to gain insights into incident patterns, response times, and escalation effectiveness. The endpoint is particularly useful for operational reviews, performance analysis, and identifying areas for improvement in incident management processes. It provides flexibility in data selection through various filters and supports different time-based aggregations for comprehensive reporting.

Retrieves and aggregates metrics for incidents across all services in PagerDuty. This endpoint allows for extensive filtering and customization of incident data, enabling detailed analysis of operational performance. It's particularly useful for generating reports, identifying trends, and assessing incident management efficiency over specified time periods. The endpoint supports various filtering criteria, time zone adjustments, and aggregation options, making it a powerful tool for both high-level overviews and granular incident analytics. However, users should be aware of the complexity of the filtering options and ensure they provide accurate parameters to obtain relevant data.

Associates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services. This endpoint is used to establish a hierarchical structure of services, which is crucial for effective incident management and impact analysis. It enables you to create multiple dependencies in a single API call, improving efficiency when setting up complex service relationships. Use this endpoint when you need to define or update the dependency structure of your services in PagerDuty, such as during initial setup, service restructuring, or when adding new services to your incident management workflow.

This endpoint associates a specific team with an automation action in PagerDuty. It allows you to link a team to an automated workflow, enabling better organization and management of automation actions within your incident response processes. Use this endpoint when you need to assign responsibility for an automation action to a particular team or when restructuring your automation workflows. The association helps in tracking, auditing, and managing permissions for automation actions across different teams in your organization. Note that this endpoint only creates the association; it does not create new teams or automation actions.

Retrieves the audit records for a specific escalation policy in PagerDuty. This endpoint allows users to access a detailed history of changes made to the escalation policy, including modifications to escalation rules, associated services, and on-call schedules. It's particularly useful for compliance tracking, troubleshooting, and understanding how the incident response process has been adjusted over time. The audit records provide transparency into who made changes, what was changed, and when the changes occurred, helping teams maintain accountability and optimize their incident management workflows.

Converts the rules associated with a specific PagerDuty service to a new or optimized format. This endpoint is used to update and standardize the incident management rules for a given service, improving the efficiency and consistency of alert handling. It should be used when there's a need to modernize rule sets, apply best practices, or adapt rules to changing service requirements. The conversion process is applied to all rules linked to the specified service ID, potentially modifying their structure or behavior. It's important to note that this operation may impact existing incident routing and alerting patterns, so it should be used cautiously and preferably during a maintenance window.

Retrieves the count of paused incident reports in the PagerDuty system. This endpoint is part of PagerDuty's Incident Management and Analytics features, providing a quick way to quantify the number of incidents that are currently in a paused state. It's particularly useful for generating high-level analytics, tracking incident management efficiency, and identifying trends in incident handling. The endpoint returns a simple count, making it ideal for dashboard displays or periodic system status checks. It should be used when a rapid overview of paused incidents is needed, but it won't provide detailed information about individual incidents.

Create a Custom Field for an Incident Type. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types. <!-- theme: warning --> > ### Early Access > This endpoint is in Early Access and may change at any time. You must pass in the X-EARLY-ACCESS header to access it. Scoped OAuth requires: `custom_fields.write`

Create a field option for a custom field. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types. <!-- theme: warning --> > ### Early Access > This endpoint is in Early Access and may change at any time. You must pass in the X-EARLY-ACCESS header to access it. Scoped OAuth requires: `custom_fields.write`

Creates a new Ruleset in PagerDuty for managing incident routing and notification rules. This endpoint allows you to define a named set of rules that determine how incidents are processed and directed to specific teams or users. It's particularly useful when setting up or modifying your incident management workflow. The created Ruleset can be global, affecting all incoming incidents, or assigned to a specific team for more targeted incident routing. Note that while you can create the Ruleset structure with this call, the actual rules within the Ruleset must be added separately using other API endpoints.