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

GitHub Org Tokens (BYOK) — connector documentation

  • MCP endpoint: https://byok-github-org-tokens.connectorbay.com/mcp
  • REST API: POST https://byok-github-org-tokens.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-github-org-tokens.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own GitHub Org Tokens personal access token (organization owner), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-github-org-tokens.connectorbay.com/health · Tool schemas: https://byok-github-org-tokens.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-github-org-tokens · agent@connectorbay.com

What GitHub Org Tokens (BYOK) is for

GitHub Org Tokens (BYOK) lets an AI assistant read your own GitHub Org Tokens data through the GitHub Org Tokens API with a key you supply (personal access token (organization owner)). Read-only: 5 tools (list_pat_grants, list_pat_grant_repositories, list_pat_grant_requests, list_pat_request_repositories, list_org_role_users). 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 Org Tokens. GitHub Org Tokens 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 fine-grained tokens can access octo-org and which are unused for months?"
  • "Which octo-org repositories can token 25381 reach?"
  • "Which fine-grained token requests are waiting for approval in octo-org?"
  • "Which repositories does token request 25381 ask for in octo-org?"
  • "Who holds organization role 8132 in octo-org?"

What it does

  • list_pat_grants: List fine-grained personal access tokens approved for an organization with owner login, permissions, repository selection, expiry and last use (token values are never returned).
  • list_pat_grant_repositories: List the repositories one approved fine-grained token can access in an organization.
  • list_pat_grant_requests: List pending requests for fine-grained personal access tokens to access an organization, with the stated reason, permissions and expiry.
  • list_pat_request_repositories: List the repositories a pending fine-grained token request asks to access.
  • list_org_role_users: List the users assigned an organization role, directly or through a team, by login.

BYOK key

You bring your own GitHub Org Tokens personal access token (organization owner) (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

Live from the GitHub Org Tokens API (api.github.com) with a BYOK key; documentation: https://docs.github.com/en/rest/orgs/personal-access-tokens. 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 Org Tokens. GitHub Org Tokens 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 Org Tokens account.

Built for: Worldwide. Languages: English.