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

Supabase Database Config (BYOK) — connector documentation

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

What Supabase Database Config (BYOK) is for

Supabase Database Config (BYOK) lets an AI assistant read your own Supabase Database Config data through the Supabase Database Config API with a key you supply (personal access token). Read-only: 12 tools (get_pooler_config, get_pgbouncer_config, get_postgres_config, get_disk_config, get_disk_utilization, get_disk_autoscale_config, list_backups, get_backup_schedule, get_upgrade_eligibility, get_readonly_mode, get_ssl_enforcement, get_network_restrictions). 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 Database Config. Supabase Database 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:

  • "How is the connection pooler of my Supabase project configured?"
  • "What are the PgBouncer pool settings of my Supabase project?"
  • "What are max_connections and statement_timeout on my Supabase database?"
  • "How big is the database disk of my Supabase project?"
  • "How full is the disk of my Supabase database?"
  • "Is disk autoscaling set up for my Supabase project and how far can it grow?"

What it does

  • get_pooler_config: List the connection pooler (Supavisor) entries of a project, one per primary or read replica, with pool mode, pool size and client connection limit. Connection strings are not picked.
  • get_pgbouncer_config: Show the PgBouncer settings of a project: pool mode, default pool size, client connection limit and timeouts.
  • get_postgres_config: Show tuned Postgres parameters of a project, such as max_connections, shared_buffers, work_mem, statement_timeout and WAL limits.
  • get_disk_config: Show the database disk attributes of a project: volume type, size in GB, IOPS and throughput, and when it was last changed.
  • get_disk_utilization: Show how much of the database disk is used: total, used and available bytes with the measurement time.
  • get_disk_autoscale_config: Show the disk autoscaling settings of a project: growth percent, minimum increment and maximum size.
  • list_backups: List the database backups of a project with status and creation time, and whether point-in-time recovery and WAL-G backups are on.
  • get_backup_schedule: Show the daily backup schedule of a project (the time of day backups run) and when it was last updated.
  • get_upgrade_eligibility: Show whether a project can upgrade Postgres: current and latest version, target versions, estimated duration, warnings and validation errors.
  • get_readonly_mode: Show whether a project database is in read-only mode, and any temporary override.
  • get_ssl_enforcement: Show whether SSL is enforced on database connections for a project.
  • get_network_restrictions: Show the database network restrictions of a project: whether the plan allows them, the allowed IPv4 and IPv6 CIDR ranges and whether they are applied.

BYOK key

You bring your own Supabase Database 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 Database 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 Database Config. Supabase Database 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 Database Config account.

Built for: Worldwide. Languages: English.