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

GitHub Org Admin (BYOK) — connector documentation

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

What GitHub Org Admin (BYOK) is for

GitHub Org Admin (BYOK) lets an AI assistant read your own GitHub Org Admin data through the GitHub Org Admin API with a key you supply (GitHub personal access token of an organization owner (read:org scope; admin:org for roles and apps)). Read-only: 12 tools (get_organization, list_org_members, list_outside_collaborators, list_pending_invitations, list_teams, get_team, list_team_members, list_team_repositories, list_organization_roles, list_custom_properties, list_installed_apps, list_issue_types). 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 Admin. GitHub Org 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:

  • "How many private repositories and seats does octo-org have, and is two-factor required?"
  • "Which octo-org members have two-factor authentication disabled?"
  • "Who are the outside collaborators of octo-org?"
  • "Which people have pending invitations to octo-org?"
  • "What teams does octo-org have?"
  • "How many members does the platform team of octo-org have?"

What it does

  • get_organization: Get an organization's profile and settings: name, plan seats, repository counts, default repository permission and two-factor requirement.
  • list_org_members: List members of an organization, optionally only admins or only members without two-factor authentication.
  • list_outside_collaborators: List outside collaborators of an organization (people with repository access who are not members).
  • list_pending_invitations: List pending organization invitations with invited login or email, role, inviter and age.
  • list_teams: List the teams of an organization with privacy, permission and parent team.
  • get_team: Get one team by slug with member and repository counts.
  • list_team_members: List the members of a team, optionally only maintainers.
  • list_team_repositories: List the repositories a team can access with visibility and default branch.
  • list_organization_roles: List the custom and predefined organization roles with their base role and permissions.
  • list_custom_properties: List the custom repository properties defined for an organization with type, required flag and allowed values.
  • list_installed_apps: List the GitHub Apps installed on an organization with repository selection and permissions.
  • list_issue_types: List the issue types configured for an organization.

BYOK key

You bring your own GitHub Org Admin GitHub personal access token of an organization owner (read:org scope; admin:org for roles and apps) (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 Admin API (api.github.com) with a BYOK key; documentation: https://docs.github.com/en/rest/orgs. 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 Admin. GitHub Org 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 Org Admin account.

Built for: Worldwide. Languages: English.