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

PagerDuty Incident Config (BYOK) — connector documentation

  • MCP endpoint: https://byok-pagerduty-incident-config.connectorbay.com/mcp
  • REST API: POST https://byok-pagerduty-incident-config.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-pagerduty-incident-config.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own PagerDuty Incident 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-incident-config.connectorbay.com/health · Tool schemas: https://byok-pagerduty-incident-config.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-pagerduty-incident-config · agent@connectorbay.com

What PagerDuty Incident Config (BYOK) is for

PagerDuty Incident Config (BYOK) lets an AI assistant read your own PagerDuty Incident Config data through the PagerDuty Incident Config API with a key you supply (REST API key (read-only is enough)). Read-only: 8 tools (list_incident_types, get_incident_type, list_incident_type_custom_fields, list_incident_workflows, get_incident_workflow, list_workflow_triggers, list_workflow_actions, get_workflow_action). 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 Incident Config. PagerDuty Incident 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 incident types are defined in PagerDuty?"
  • "Describe the PagerDuty incident type major_incident"
  • "Which custom fields does the PagerDuty incident type major_incident have?"
  • "Which incident workflows are set up in PagerDuty?"
  • "Show the steps of PagerDuty incident workflow PWF1"
  • "Which PagerDuty workflows start automatically on incidents?"

What it does

  • list_incident_types: List incident types (categories such as major or security incident) with name, display name, description, enabled flag and parent type.
  • get_incident_type: Get one incident type by id or name with description, enabled flag, parent and dates.
  • list_incident_type_custom_fields: List the custom fields of an incident type: name, display name, data type, field type, enabled flag and (optionally) allowed options.
  • list_incident_workflows: List incident workflows with name, description, enabled flag, owning team and URL. Filter by name text; page with limit and offset.
  • get_incident_workflow: Get one incident workflow with its steps (action, description and configuration), enabled flag and owning team.
  • list_workflow_triggers: List incident workflow triggers (what starts a workflow): trigger type, condition, workflow, services covered and disabled flag. Filter by workflow, service or type.
  • list_workflow_actions: List the catalog of workflow actions that can be used in incident workflows: name, description, action type, tier, tags and creation time. Filter by keyword.
  • get_workflow_action: Get one workflow action by id with its description, tier, inputs and outputs.

BYOK key

You bring your own PagerDuty Incident 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 Incident 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 Incident Config. PagerDuty Incident 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 Incident Config account.

Built for: Worldwide. Languages: English.