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

GitHub Repo Admin (BYOK) — connector documentation

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

What GitHub Repo Admin (BYOK) is for

GitHub Repo Admin (BYOK) lets an AI assistant read your own GitHub Repo Admin data through the GitHub Repo Admin API with a key you supply (GitHub personal access token (repo scope; most of these reads need admin access to the repository)). Read-only: 12 tools (list_collaborators, list_branches, get_branch_protection, list_rulesets, list_environments, list_deployments, list_deployment_statuses, list_repository_teams, list_repository_invitations, list_webhook_status, list_deploy_keys, list_autolinks). 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 Repo Admin. GitHub Repo Admin 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:

  • "Who has write access to octocat/Hello-World?"
  • "Which branches of octocat/Hello-World are protected?"
  • "What protection rules does the main branch of octocat/Hello-World have?"
  • "Which rulesets apply to octocat/Hello-World?"
  • "Which deployment environments does octocat/Hello-World have?"
  • "What was last deployed to production in octocat/Hello-World?"

What it does

  • list_collaborators: List the people with access to a repository and their permission level; filter by outside or direct collaborators.
  • list_branches: List a repository's branches with the head commit sha and whether branch protection is on.
  • get_branch_protection: Get the protection rules of one branch: required reviews, status checks, admin enforcement, force-push and deletion settings.
  • list_rulesets: List the repository rulesets (including inherited organization rulesets) with target, enforcement and update time.
  • list_environments: List a repository's deployment environments with creation and update times.
  • list_deployments: List a repository's deployments with ref, sha, environment and creator; filter by environment, ref or sha.
  • list_deployment_statuses: List the status history of one deployment (pending, in_progress, success, failure) with log link.
  • list_repository_teams: List the teams that have access to a repository with their permission.
  • list_repository_invitations: List pending invitations to collaborate on a repository with invitee, inviter and permission.
  • list_webhook_status: List a repository's webhooks with their events, active flag and the result of the last delivery. Target URLs and secrets are not returned.
  • list_deploy_keys: List a repository's deploy keys with title, read-only flag and last use. The key material is not returned.
  • list_autolinks: List the custom autolink references configured on a repository.

BYOK key

You bring your own GitHub Repo Admin GitHub personal access token (repo scope; most of these reads need admin access to the repository) (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 Repo Admin API (api.github.com) with a BYOK key; documentation: https://docs.github.com/en/rest/repos. 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 Repo Admin. GitHub Repo Admin 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 Repo Admin account.

Built for: Worldwide. Languages: English.