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

GitHub Code Security Configs (BYOK) — connector documentation

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

What GitHub Code Security Configs (BYOK) is for

GitHub Code Security Configs (BYOK) lets an AI assistant read your own GitHub Code Security Configs data through the GitHub Code Security Configs API with a key you supply (personal access token). Read-only: 9 tools (list_org_configurations, get_org_configuration, list_org_default_configurations, list_org_configuration_repositories, list_enterprise_configurations, get_enterprise_configuration, list_enterprise_default_configurations, list_enterprise_configuration_repositories, list_org_private_registries). 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 Code Security Configs. GitHub Code Security Configs 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 code security configurations does octo-org have?"
  • "What does the Strict baseline security configuration of octo-org enable?"
  • "Which security configuration do new octo-org repositories get by default?"
  • "Which octo-org repositories use the Strict baseline security configuration?"
  • "Which code security configurations does octo-enterprise have?"
  • "What does enterprise security configuration 17 of octo-enterprise enable?"

What it does

  • list_org_configurations: List an organization's code security configurations with the state of Dependabot, code scanning and secret scanning settings.
  • get_org_configuration: Get one organization code security configuration with all its feature settings.
  • list_org_default_configurations: Show which configuration is applied by default to new repositories of an organization.
  • list_org_configuration_repositories: List repositories attached to an organization code security configuration with their attachment status.
  • list_enterprise_configurations: List an enterprise's code security configurations with feature settings.
  • get_enterprise_configuration: Get one enterprise code security configuration with its feature settings.
  • list_enterprise_default_configurations: Show which configuration is applied by default to new repositories of an enterprise.
  • list_enterprise_configuration_repositories: List repositories attached to an enterprise code security configuration with their attachment status.
  • list_org_private_registries: List the private package registries configured for Dependabot and code scanning in an organization (registry type, URL and visibility; credentials are never returned).

BYOK key

You bring your own GitHub Code Security Configs personal access token (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 Code Security Configs API (api.github.com) with a BYOK key; documentation: https://docs.github.com/en/rest/code-security/configurations. 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 Code Security Configs. GitHub Code Security Configs 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 Code Security Configs account.

Built for: Worldwide. Languages: English.