Supabase MCP: your Postgres projects inside Claude and Cursor

Connect Supabase to Claude, ChatGPT or Cursor

1. 1Click Connect Supabase free and sign in with your Supabase account.
2. 2Your AI app gets every Supabase tool when you connect, and the full list appears then. Switch off the tools that delete API keys or remove third-party auth providers, and the SQL tool too if your AI app should read schemas rather than run queries.
3. 3Add ContextGate to your AI app as a connector or MCP server. The steps for each app are on the Works with page.
4. 4Ask your AI app for the columns and constraints of a table in one of your Supabase projects, then open Activity to see the call.

Supabase work you can do from your editor

• List your organizations and projects, with each project's region and status.
• Pull column types and constraints for several tables at once to debug a schema or write accurate SQL.
• Run a SQL query against a project's database when the standard endpoints aren't enough.
• Generate TypeScript types from your database for the schemas you name.
• Audit a project's third-party auth providers, SSL enforcement and API keys.

Protect your Supabase databases

• Removing a third-party auth provider stops people signing in that way straight away, so switch that tool off unless you need it.
• Policies check every call, so a secret key pasted into a SQL query can be blocked.
• Activity keeps a record of every query and project change your team's AI apps make through ContextGate.

What you get with Supabase and ContextGate

• Your AI apps can use SupabaseClaude, Cursor, ChatGPT and other AI apps reach Supabase through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any Supabase tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

Supabase tools

Examples of what your AI apps can do in Supabase. You'll see the exact list of tools after you connect it.

• Execute project database queryExecutes a given sql query against the project's database; use for advanced data operations or when standard api endpoints are insufficient, ensuring queries are valid postgresql and sanitized. use th
• Create an organizationCreates a new supabase organization, which serves as a top-level container for projects, billing, and team access.
• Create new projectCreates a new supabase project, requiring a unique name (no dots) within the organization; project creation is asynchronous.
• Generate TypeScript typesGenerates and retrieves typescript types from a supabase project's database; any schemas specified in `included schemas` must exist in the project.
• Get Table SchemasRetrieves column details, types, and constraints for multiple database tables to help debug schema issues and write accurate sql queries.
• List all organizationsLists all organizations (id and name only) associated with the supabase account, excluding project details within these organizations.
• List all projectsRetrieves a list of all supabase projects, including their id, name, region, and status, for the authenticated user.
• Create project api keyCreates a 'publishable' or 'secret' api key for an existing supabase project, optionally with a description; 'secret' keys can have customized jwt templates.
• Delete an API key from the projectPermanently deletes a specific api key (identified by `id`) from a supabase project (identified by `ref`), revoking its access.
• Get a third-party integrationRetrieves the detailed configuration for a specific third-party authentication (tpa) provider, identified by `tpa id`, within an existing supabase project specified by `ref`.
• List third-party auth integrations for projectLists all configured third-party authentication provider integrations for an existing supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings.
• Delete third party auth configRemoves a third-party authentication provider (e.g., google, github) from a supabase project's configuration; this immediately prevents users from logging in via that method.
• Update an API key for the projectUpdates an existing supabase project api key's `description` and/or `secret jwt template` (which defines its `role`); does not regenerate the key string.
• Beta activate custom hostname for projectActivates a previously configured custom hostname for a supabase project, assuming dns settings are verified externally.
• Activate vanity subdomain for projectActivates a vanity subdomain for the specified supabase project, requiring subsequent dns configuration for the subdomain to become operational.
• Authorize user through OAuthGenerates a supabase oauth 2.0 authorization url for user redirection, requiring a pre-registered `client id` and a `redirect uri` that matches one of its pre-registered uris.
• Check vanity subdomain availabilityChecks if a specific vanity subdomain is available for a supabase project; this action does not reserve or assign the subdomain.
• Enable project database webhooksEnables database webhooks for the supabase project `ref`, triggering real-time notifications for insert, update, or delete events.
• Get project SSL enforcement configurationRetrieves the ssl enforcement configuration for a specified supabase project, indicating if ssl connections are mandated for its database.
• Get current vanity subdomain configFetches the current vanity subdomain configuration, including its status and custom domain name, for a supabase project identified by its reference id.