Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

PagerDuty Account Config (BYOK) — connector documentation

  • MCP endpoint: https://byok-pagerduty-account-config.connectorbay.com/mcp
  • REST API: POST https://byok-pagerduty-account-config.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-pagerduty-account-config.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own PagerDuty Account Config REST API key (read-only is enough), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-pagerduty-account-config.connectorbay.com/health · Tool schemas: https://byok-pagerduty-account-config.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-pagerduty-account-config · agent@connectorbay.com

What PagerDuty Account Config (BYOK) is for

PagerDuty Account Config (BYOK) lets an AI assistant read your own PagerDuty Account Config data through the PagerDuty Account Config API with a key you supply (REST API key (read-only is enough)). Read-only: 9 tools (list_teams, get_team, list_maintenance_windows, list_tags, list_vendors, list_alert_grouping_settings, list_change_events, list_standards, list_abilities). 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 Account Config. PagerDuty Account Config 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 teams exist in PagerDuty?"
  • "Describe PagerDuty team PT1"
  • "Which PagerDuty maintenance windows are ongoing or coming up?"
  • "Which tags are used in PagerDuty?"
  • "Does PagerDuty have an integration for Honeycomb?"
  • "How does PagerDuty group alerts for our services?"

What it does

  • list_teams: List PagerDuty teams with name, description and default role. Filter by name text.
  • get_team: Get one PagerDuty team by id: name, description, default role and URL (no member list).
  • list_maintenance_windows: List maintenance windows (periods when services do not alert) with start, end, description, the services and the teams affected. Filter by state, team or service.
  • list_tags: List the tags in the account (labels applied to teams, users and escalation policies). Filter by label text.
  • list_vendors: List the integration vendors PagerDuty supports (for example monitoring tools) with description, website and integration guide URL.
  • list_alert_grouping_settings: List alert grouping settings (how alerts are merged into incidents): name, type, services, configuration and dates. Cursor paging with after.
  • list_change_events: List change events (deploys, config changes) sent to PagerDuty with summary, source, time, affected services and links. Filter by time range.
  • list_standards: List service standards (rules that technical services should meet) with name, description, active flag, resource type and inclusion and exclusion lists.
  • list_abilities: List the feature abilities enabled for the account by name, for example teams or sso, which tells what the plan supports.

BYOK key

You bring your own PagerDuty Account Config REST API key (read-only is enough) (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

Live from the PagerDuty Account Config API (api.pagerduty.com) with a BYOK key; documentation: https://developer.pagerduty.com/api-reference/. 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 Account Config. PagerDuty Account Config 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 Config account.

Built for: Worldwide. Languages: English.