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

Supabase Service Config (BYOK) — connector documentation

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

What Supabase Service Config (BYOK) is for

Supabase Service Config (BYOK) lets an AI assistant read your own Supabase Service Config data through the Supabase Service Config API with a key you supply (personal access token). Read-only: 12 tools (get_auth_providers, get_auth_security_settings, get_rest_api_config, get_realtime_config, get_storage_config, get_custom_hostname_config, get_vanity_subdomain_config, list_third_party_auth_integrations, list_sso_providers, list_signing_keys, get_services_health, get_api_request_counts). 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.supabase.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Supabase Service Config. Supabase Service Config 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 login providers are enabled in my Supabase project?"
  • "What are the password rules and JWT expiry in my Supabase project?"
  • "Which schemas does my Supabase REST API expose and what is the max rows limit?"
  • "What are the Realtime limits of my Supabase project?"
  • "What is the maximum upload size of my Supabase storage and is image transformation on?"
  • "Is the custom domain of my Supabase project verified?"

What it does

  • get_auth_providers: Show which sign-in methods are enabled for a project's Auth service: email, phone, anonymous, SAML and common social providers. Client secrets are not picked.
  • get_auth_security_settings: Show a project's Auth security and session settings: site URL, sign-up switch, JWT expiry, password rules, MFA limit, CAPTCHA and email rate limit.
  • get_rest_api_config: Show the REST (PostgREST) API settings of a project: exposed schemas, maximum rows, extra search path and connection pool size. The JWT secret is not picked.
  • get_realtime_config: Show the Realtime limits of a project: concurrent users, events and bytes per second, channels per client, payload size and whether it is private-only or suspended.
  • get_storage_config: Show the Storage settings of a project: maximum file size and which features (image transformation, S3 protocol, cache purge, vector buckets) are enabled.
  • get_custom_hostname_config: Show the custom domain setup of a project: the hostname and the verification stage it has reached.
  • get_vanity_subdomain_config: Show whether a project uses a vanity subdomain, and the custom domain recorded for it.
  • list_third_party_auth_integrations: List third-party auth integrations of a project (for example Clerk, Auth0, Firebase) with type, issuer URL and JWKS URL.
  • list_sso_providers: List SAML SSO providers of a project with the email domains routed to each and creation time. Metadata XML is not picked.
  • list_signing_keys: List the JWT signing keys of a project with algorithm, status (in use, standby, previously used, revoked) and dates. Public JWKs are not picked.
  • get_services_health: Check the health of chosen services of a project (auth, db, pooler, realtime, rest, storage) and return the status of each.
  • get_api_request_counts: Show request counts per time bucket for a project's Auth, REST, Realtime and Storage APIs over a chosen interval.

BYOK key

You bring your own Supabase Service Config personal access token (https://supabase.com/dashboard/account/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.supabase.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 Supabase Service Config API (api.supabase.com) with a BYOK key; documentation: https://supabase.com/docs/reference/api/introduction. 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 Supabase Service Config. Supabase Service Config 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 Supabase Service Config account.

Built for: Worldwide. Languages: English.