Sauce Labs (BYOK)
Read your Sauce Labs real-device and virtual-device test cloud: devices, device status, jobs, builds, concurrency and platform status, with your own username and access key
Discover
OpenAPIRead your data8 tools
PagerDuty Incident Config (BYOK)
Read your PagerDuty incident types, incident custom fields, incident workflows, workflow triggers and the workflow action catalog with your own REST API key
Unify Dynamics LLC
Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderPagerDuty Incident Configunofficial, not affiliated
Works withMCP · RESTany agent
Try asking
Real questions, and the tools your agent calls to answer them.
Which incident types are defined in PagerDuty?
Tools called
list_incident_typesDescribe the PagerDuty incident type major_incident
Tools called
get_incident_typeWhich custom fields does the PagerDuty incident type major_incident have?
Tools called
list_incident_type_custom_fieldsWhich incident workflows are set up in PagerDuty?
Tools called
list_incident_workflowsShow the steps of PagerDuty incident workflow PWF1
Tools called
get_incident_workflowWhich PagerDuty workflows start automatically on incidents?
Tools called
list_workflow_triggersAbout
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.
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.
Privacy
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
Data not collectedNo account, no profile, no stored prompts or results.
What it can do
8 tools, grouped by job. Every one is read-only or compute-only.
- List incident typesList incident types (categories such as major or security incident) with name, display name, description, enabled flag and parent type.
- Get incident typeGet one incident type by id or name with description, enabled flag, parent and dates.
- List incident type custom fieldsList the custom fields of an incident type: name, display name, data type, field type, enabled flag and (optionally) allowed options.
- List incident workflowsList incident workflows with name, description, enabled flag, owning team and URL.
- Get incident workflowGet one incident workflow with its steps (action, description and configuration), enabled flag and owning team.
- List workflow triggersList incident workflow triggers (what starts a workflow): trigger type, condition, workflow, services covered and disabled flag.
- List workflow actionsList the catalog of workflow actions that can be used in incident workflows: name, description, action type, tier, tags and creation time.
- Get workflow actionGet one workflow action by id with its description, tier, inputs and outputs.
Information
PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpoint
https://byok-pagerduty-incident-config.connectorbay.com/mcpREST APIopenapi.json
CountryWorldwide
FunctionOther
LayerDeep connectors
More like this
More in OtherReflag (BYOK)
Read your Reflag feature flags, apps, environments and per-user or per-company flag status with your own management API key
Back4app (BYOK)
Read objects, counts and remote config from your Back4app (Parse Server) backend-as-a-service app with your own application id and REST API key
Apphud (BYOK)
Read your Apphud subscription analytics: chart catalog, time series, column reports and dashboard widgets, with your own S2S key
Userpilot (BYOK)
Read the catalog of your Userpilot product-growth content (flows, banners, spotlights, surveys, checklists, segments, tracked events and properties) with your own API key
Airbridge (BYOK)
Read your Airbridge mobile attribution reports (actuals and active users) and their metric and group-by catalogs with your own API token