Skip to directory

About Supabase MCP

Supabase's hosted MCP server connects AI coding clients to Supabase projects for database, documentation, debugging, development, Edge Functions, Storage, branching, and account operations.

What you can use it for

  • Inspect and query Supabase project databases
  • Search Supabase documentation
  • Inspect project URL, types, logs, advisors, and Edge Functions
  • Manage Supabase projects/branches and deploy or manage functions when enabled and authorized
Connection and setup
Hosting
Remote hosted; local endpoint via Supabase CLI
Transport
Streamable HTTP
Endpoint
https://mcp.supabase.com/mcp
Authentication
OAuth with dynamic client registration and interactive Supabase sign-in by default. Scoped PAT header or manually registered OAuth app are documented for special clients/CI.

Requirements

  • Supabase account and organization/project access
  • MCP client that supports remote HTTP OAuth
  • Choose a specific project, read-only mode, and feature groups to limit access

Setup steps

  1. Configure https://mcp.supabase.com/mcp with an appropriate project_ref and optional feature groups/read_only=true.
  2. Start OAuth in the MCP client and sign in to Supabase; choose the organization containing the target project. No PAT is normally needed.
  3. Confirm the intended project, scope, read-only setting, and enabled feature groups before allowing writes.
  4. Verify with a harmless read-only request such as listing tables; do not use production without necessity.
Tools 33+

Stored rows include the documented database, debugging, development, Edge Function, account and docs groups plus names of optional branching and Storage tools. Actual exposure varies by selected feature groups, project-scoping, read-only mode and plan; branching requires a paid plan and Storage is disabled by default.

  • list_tables
    01
  • list_extensions
    02
  • list_migrations
    03
  • apply_migration
    04
  • execute_sql
    05
  • query_logs
    06
  • get_advisors
    07
  • get_project_url
    08
  • get_publishable_keys
    09
  • generate_typescript_types
    10
  • list_edge_functions
    11
  • get_edge_function
    12
  • deploy_edge_function
    13
  • create_edge_function_secret
    14
  • list_projects
    15
  • get_project
    16
  • create_project
    17
  • pause_project
    18
  • restore_project
    19
  • list_organizations
    20
  • get_organization
    21
  • get_cost
    22
  • confirm_cost
    23
  • search_docs
    24
  • create_branch

    Create a database branch.

    25
  • list_branches

    List database branches.

    26
  • delete_branch

    Delete a database branch.

    27
  • merge_branch

    Merge a database branch.

    28
  • reset_branch

    Reset a database branch.

    29
  • rebase_branch

    Rebase a database branch.

    30
  • list_storage_buckets

    List storage buckets.

    31
  • get_storage_config

    Read storage configuration.

    32
  • update_storage_config

    Update storage configuration.

    33

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Powerful write/deployment tools can modify production resources; enable least privilege, project scope, read-only mode, and narrow features.
  • Tools execute under the authenticated developer's permissions; user data may contain prompt-injection attempts.
  • create_edge_function_secret requires supported elicitation and secret values must be entered in the Supabase Dashboard, never chat/tool args.
  • Project-scoped mode disables account-management tools. Storage group is off by default.
  • Manual PAT auth is for CI or clients without dynamic registration; custom headers may not be supported by every client.
Source discrepancies
  • The discovery listing labels the publisher as supabase-community, while Supabase's official documentation identifies this as its hosted MCP server. Community wrappers are separate implementations.
Original sources
  • official tool reference

    Official docs list tools by feature group. Storage is disabled by default, branching requires a paid plan, account tools are hidden in project-scoped mode, and selected features determine the exposed catalog.

  • official documentation

    Official docs list tools by feature group. Storage is disabled by default, branching requires a paid plan, account tools are hidden in project-scoped mode, and selected features determine the exposed catalog.

Documentation checked 2026-10-28T12:48:00.000Z. Connection has not been runtime tested.