PagerDuty (BYOK) — connector documentation
- MCP endpoint:
https://byok-pagerduty.connectorbay.com/mcp - REST API:
POST https://byok-pagerduty.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-pagerduty.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own PagerDuty REST API key, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-pagerduty.connectorbay.com/health· Tool schemas:https://byok-pagerduty.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-pagerduty · agent@connectorbay.com
What PagerDuty (BYOK) is for
PagerDuty (BYOK) lets an AI assistant read your own PagerDuty data through the PagerDuty API with a key you supply (REST API key). Read-only: 9 tools (list_incidents, get_incident, list_services, get_service, list_oncalls, list_schedules, get_schedule, list_escalation_policies, list_users). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.pagerduty.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PagerDuty. PagerDuty and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which PagerDuty incidents are triggered right now?"
- "What is the state of PagerDuty incident Q1ABC23?"
- "What services are configured in PagerDuty?"
- "Show the PagerDuty service PABC123"
- "Who is on call in PagerDuty right now?"
- "What on-call schedules exist in PagerDuty?"
What it does
list_incidents: List PagerDuty incidents (newest first unless sorted otherwise) filtered by status, urgency, service and time range, with service, assignees and priority.get_incident: Get one PagerDuty incident by ID or incident number: status, urgency, times, service, escalation policy, assignees and alert counts.list_services: List PagerDuty services with status, escalation policy and timeouts, optionally filtered by name.get_service: Get one PagerDuty service: status, escalation policy, timeouts, alert creation mode, urgency rule and support hours.list_oncalls: List who is on call now (or in a time range), with user, schedule, escalation policy, escalation level and shift start and end.list_schedules: List PagerDuty on-call schedules with name, time zone, description, users and escalation policies.get_schedule: Get one PagerDuty schedule, with its layers and rendered shifts for a time range when since and until are given.list_escalation_policies: List PagerDuty escalation policies with their rules, delays, targets and loop count.list_users: List PagerDuty users with name, email, role, job title and time zone, optionally filtered by name.
BYOK key
You bring your own PagerDuty REST API key (https://support.pagerduty.com/main/docs/api-access-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.pagerduty.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://docs.pagerduty.com/developer/api/reference/rest/incidents/list-incidents (the API this connector calls, with a BYOK key)
Live from the PagerDuty API (api.pagerduty.com) with a BYOK key; documentation: https://docs.pagerduty.com/developer/api/reference/rest/incidents/list-incidents. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PagerDuty. PagerDuty and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your PagerDuty account.
Built for: Worldwide. Languages: English.