PagerDuty Event Orchestrations (BYOK)
Read your PagerDuty global and service event orchestrations, their router, global and service rule sets, cache variables and legacy rulesets with your own REST API key
6 PagerDuty connectors for AI agents, one per API surface (Event Orchestrations, core, Account Config, Business Services, Incident Config, Status Pages). Each is a hosted MCP server and REST API that reads your own PagerDuty data with your own key (bring your own key); ConnectorBay is independent of PagerDuty.
6 connectors · 53 tools · hosted MCP servers with REST APIs and OpenAI tool lists
Read your PagerDuty global and service event orchestrations, their router, global and service rule sets, cache variables and legacy rulesets with your own REST API key
Read your PagerDuty incidents, services, on-call shifts, schedules, escalation policies and users with BYOK
Read your PagerDuty teams, maintenance windows, tags, vendors, alert grouping settings, change events, service standards and account abilities with your own REST API key
Read your PagerDuty business services, their impact status, impactors, priority threshold and service dependencies with your own REST API key
Read your PagerDuty incident types, incident custom fields, incident workflows, workflow triggers and the workflow action catalog with your own REST API key
Read your PagerDuty status pages with their services, severities, statuses, impacts, incident and maintenance posts, post updates and postmortems using your own REST API key