GitHub Webhooks (BYOK) — connector documentation
- MCP endpoint:
https://byok-github-webhooks.connectorbay.com/mcp - REST API:
POST https://byok-github-webhooks.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-github-webhooks.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own GitHub Webhooks GitHub personal access token (admin:org_hook scope for organizations, admin:repo_hook or repo for repositories), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-github-webhooks.connectorbay.com/health· Tool schemas:https://byok-github-webhooks.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-github-webhooks · agent@connectorbay.com
What GitHub Webhooks (BYOK) is for
GitHub Webhooks (BYOK) lets an AI assistant read your own GitHub Webhooks data through the GitHub Webhooks API with a key you supply (GitHub personal access token (admin:org_hook scope for organizations, admin:repo_hook or repo for repositories)). Read-only: 5 tools (list_org_webhooks, get_org_webhook, list_org_webhook_deliveries, get_repo_webhook, list_repo_webhook_deliveries). 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.github.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitHub Webhooks. GitHub Webhooks 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 webhooks does octo-org have and which events do they send?"
- "Describe webhook 12345678 of octo-org"
- "Did the latest deliveries of org webhook 12345678 in octo-org succeed?"
- "Is webhook 12345678 of octocat/Hello-World healthy?"
- "Which deliveries of webhook 12345678 on octocat/Hello-World failed?"
What it does
list_org_webhooks: List an organization's webhooks with subscribed events, active flag and content type; the target URL and secret are left out.get_org_webhook: Get one organization webhook's events, active flag and content type; the target URL and secret are left out.list_org_webhook_deliveries: List recent deliveries of an organization webhook with event, action, HTTP status code, duration and time; payloads are not included.get_repo_webhook: Get one repository webhook's events, active flag, content type and the result of its last delivery; the target URL and secret are left out.list_repo_webhook_deliveries: List recent deliveries of a repository webhook with event, action, HTTP status code, duration and time; payloads are not included.
BYOK key
You bring your own GitHub Webhooks GitHub personal access token (admin:org_hook scope for organizations, admin:repo_hook or repo for repositories) (https://github.com/settings/tokens). 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.github.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
- https://docs.github.com/en/rest/webhooks (the API this connector calls, with a BYOK key)
Live from the GitHub Webhooks API (api.github.com) with a BYOK key; documentation: https://docs.github.com/en/rest/webhooks. 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 GitHub Webhooks. GitHub Webhooks 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 GitHub Webhooks account.
Built for: Worldwide. Languages: English.