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

Checkly Alerting (BYOK) — connector documentation

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

What Checkly Alerting (BYOK) is for

Checkly Alerting (BYOK) lets an AI assistant read your own Checkly Alerting data through the Checkly Alerting API with a key you supply (Checkly user API key). Read-only: 5 tools (list_alert_channels, get_alert_channel, list_alert_notifications, list_dashboards, get_dashboard). 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.checklyhq.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkly Alerting. Checkly Alerting 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 alert channels are set up in Checkly?"
  • "Which checks use this Checkly alert channel?"
  • "Did any Checkly alert notifications fail to send recently?"
  • "Which Checkly dashboards exist?"
  • "Show one Checkly dashboard"

What it does

  • list_alert_channels: List alert channels with type (email, Slack, webhook, SMS, PagerDuty, Opsgenie, call) and which events they send. Destination settings such as addresses and URLs are not returned.
  • get_alert_channel: Get one alert channel by id: type, which events it sends and which checks and groups are subscribed to it. Destination settings are not returned.
  • list_alert_notifications: List alert notifications that were sent (default: the last 6 hours) with channel, check, status and time; optionally only failed sends or one channel.
  • list_dashboards: List the public status dashboards with header, description, custom URL or domain, privacy flag, refresh rate and tags. Access keys are not returned.
  • get_dashboard: Get one dashboard by its dashboard id: header, description, custom URL or domain, privacy flag, refresh rate and tags.

BYOK key

You bring your own Checkly Alerting Checkly user API key (https://app.checklyhq.com/settings/user/api-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.checklyhq.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 Checkly Alerting API (api.checklyhq.com) with a BYOK key; documentation: https://www.checklyhq.com/docs/api-reference/openapi.json. 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 Checkly Alerting. Checkly Alerting 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 Checkly Alerting account.

Built for: Worldwide. Languages: English.