HomeMarketplace

Pagerduty MCP Integration - AI Agent Tools

Connect Pagerduty with AI agents using Model Context Protocol (MCP). Seamlessly integrate Pagerduty tools and actions into Claude, Cursor, Windsurf, and other AI applications for enhanced workflow automation.

Features

  • Easy MCP setup with one command
  • Compatible with Claude, Cursor, Windsurf
  • 354+ available tools and actions
  • Built-in authentication and security
  • Real-time synchronization
  • No coding required

Category

Developer Tools & DevOps tools for AI automation

Setup Instructions

Install Pagerduty MCP server in minutes. Choose your AI platform: Cursor, Claude Desktop, Windsurf, or use HTTP endpoint for custom integrations. Follow our step-by-step guide to connect Pagerduty with your AI agent.

Benefits

  • Automate Pagerduty workflows with AI
  • Increase productivity with AI-powered Pagerduty operations
  • Seamless integration with popular AI platforms
  • Enterprise-grade security and reliability
  • 24/7 support and documentation

Related Integrations

Explore other MCP integrations: Gmail MCP, Notion MCP, GitHub MCP, Linear MCP, Slack MCP, Google Sheets MCP, and 100+ more AI agent tools.

Pagerduty
Pagerduty

Integrate PagerDuty to manage incidents, schedules, and alerts directly from your application.

VerifiedComposioComposio Managed
Users
6819
Tools
354
Last Updated
12h ago

Category

Developer Tools & DevOps

6819VIEWS
2928USERS

Tools

Page 1 of 59

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 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.

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 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.

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 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.

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 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.

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 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.

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, 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.