Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
PagerDuty Account Config (BYOK) icon

PagerDuty Account Config (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

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderPagerDuty Account Configunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which teams exist in PagerDuty?
Tools called
list_teams
Describe PagerDuty team PT1
Tools called
get_team
Which PagerDuty maintenance windows are ongoing or coming up?
Tools called
list_maintenance_windows
Which tags are used in PagerDuty?
Tools called
list_tags
Does PagerDuty have an integration for Honeycomb?
Tools called
list_vendors
How does PagerDuty group alerts for our services?
Tools called
list_alert_grouping_settings

About

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.

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.

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

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • List teamsList PagerDuty teams with name, description and default role.
  • Get teamGet one PagerDuty team by id: name, description, default role and URL (no member list).
  • List maintenance windowsList maintenance windows (periods when services do not alert) with start, end, description, the services and the teams affected.
  • List tagsList the tags in the account (labels applied to teams, users and escalation policies).
  • List vendorsList the integration vendors PagerDuty supports (for example monitoring tools) with description, website and integration guide URL.
  • List alert grouping settingsList alert grouping settings (how alerts are merged into incidents): name, type, services, configuration and dates.
  • List change eventsList change events (deploys, config changes) sent to PagerDuty with summary, source, time, affected services and links.
  • List standardsList service standards (rules that technical services should meet) with name, description, active flag, resource type and inclusion and exclusion…
  • List abilitiesList the feature abilities enabled for the account by name, for example teams or sso, which tells what the plan supports.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-pagerduty-account-config.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

More like this

More in Other

OnlineOrNot (BYOK)

Read your OnlineOrNot uptime checks, incidents, heartbeats, maintenance windows and status pages with your own API token

Live · MCP + REST12 tools

Roadie (BYOK)

Read your Roadie software catalog entities, locations, and Tech Insights scorecards, checks and results with your own API token

Live · MCP + REST11 tools

elmah.io (BYOK)

Read your elmah.io logs, logged errors and messages, and deployments with your own API key

Live · MCP + REST7 tools

Tolgee (BYOK)

Read your Tolgee localization projects, languages, translation keys, translations, tasks and statistics with your own API key

Live · MCP + REST11 tools

NodePing (BYOK)

Read your NodePing monitoring checks, results, uptime, outage events, maintenance schedules, accounts and probe locations with your own account token

Live · MCP + REST10 tools

DIDWW (BYOK)

Read your DIDWW phone numbers, orders, trunks, capacity pools, balance and number coverage with your own API key

Live · MCP + REST9 tools

Get PagerDuty Account Config (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own PagerDuty Account Config REST API key (read-only is enough). Create one at https://support.pagerduty.com/main/docs/api-access-keys, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to PagerDuty Account Config. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with PagerDuty Account Config.