Skip to main content
Glama
supabase-mcp-server

supabase-mcp-server

Supabase MCP Server

An MCP (Model Context Protocol) server that enables LLMs to interact with Supabase services including Database, Auth, Storage, and Edge Functions.

Setup

  1. Install dependencies:

    npm install
  2. Copy .env.example to .env and fill in your Supabase credentials:

    cp .env.example .env
  3. Build:

    npm run build
  4. Run:

    npm start

Related MCP server: Supabase MCP Server

Environment Variables

Variable

Required

Description

SUPABASE_URL

Yes

Your Supabase project URL

SUPABASE_SERVICE_ROLE_KEY

Yes

Service role key (found in Project Settings > API)

TRANSPORT

No

Transport mode: stdio (default) or http

MCP Client Configuration

Add to your MCP client config (e.g., Claude Desktop):

{
  "mcpServers": {
    "supabase": {
      "command": "node",
      "args": ["/path/to/supabase-mcp-server/dist/index.js"],
      "env": {
        "SUPABASE_URL": "https://your-project.supabase.co",
        "SUPABASE_SERVICE_ROLE_KEY": "your-service-role-key"
      }
    }
  }
}

Available Tools

Database (7 tools)

  • supabase_query - Select rows with filters, ordering, pagination

  • supabase_insert - Insert one or more rows

  • supabase_update - Update rows matching filters

  • supabase_delete - Delete rows matching filters

  • supabase_upsert - Insert or update on conflict

  • supabase_rpc - Call a Postgres function

  • supabase_list_tables - List tables in the database

Auth (5 tools)

  • supabase_auth_list_users - List users with pagination

  • supabase_auth_get_user - Get user by ID

  • supabase_auth_create_user - Create a new user

  • supabase_auth_update_user - Update user details

  • supabase_auth_delete_user - Delete a user

Storage (8 tools)

  • supabase_storage_list_buckets - List storage buckets

  • supabase_storage_create_bucket - Create a bucket

  • supabase_storage_list_files - List files in a bucket

  • supabase_storage_upload - Upload a file (base64)

  • supabase_storage_download - Download a file (base64)

  • supabase_storage_delete - Delete files

  • supabase_storage_get_public_url - Get public URL

  • supabase_storage_move - Move/rename a file

Edge Functions (1 tool)

  • supabase_functions_invoke - Invoke an Edge Function

Development

npm run dev    # Run with tsx (hot reload)
npm run build  # Compile TypeScript
npm start      # Run compiled output

Testing with MCP Inspector

npx @modelcontextprotocol/inspector node dist/index.js

Available Tools

21 tools
supabase_auth_create_userB
Destructive

Create a new user with email/password or phone

Inputs: email, phone, password, emailConfirm, +2 more.

supabase_auth_delete_userB
Destructive

Delete a user by their ID

Inputs: userId (required).

supabase_auth_get_userA
Read-onlyIdempotent

Get a single user by their ID

Inputs: userId (required).

supabase_auth_list_usersA
Read-only

List all users with pagination

Inputs: page, perPage.

supabase_auth_update_userA
Destructive

Update a user's email, password, phone, or metadata

Inputs: userId (required), email, phone, password, +2 more.

supabase_deleteA
Destructive

Delete rows from a Supabase table matching the given filters

Inputs: table (required), filters (required).

supabase_functions_invokeC

Invoke a Supabase Edge Function

Inputs: functionName (required), body, method, headers.

supabase_insertB
Destructive

Insert one or more rows into a Supabase table

Inputs: data (required), table (required), onConflict.

supabase_list_tablesB
Read-onlyIdempotent

List all tables in the database schema

Inputs: schema.

supabase_queryA
Read-onlyIdempotent

Select rows from a Supabase table with filters, ordering, and pagination

Inputs: table (required), limit, order, offset, +4 more.

supabase_rpcC

Call a Postgres function via RPC

Inputs: functionName (required), params.

supabase_storage_create_bucketB
Destructive

Create a new storage bucket

Inputs: name (required), public, fileSizeLimit, allowedMimeTypes.

supabase_storage_deleteA
Destructive

Delete files from a storage bucket

Inputs: paths (required), bucket (required).

supabase_storage_downloadA
Read-onlyIdempotent

Download a file from a storage bucket (returns base64)

Inputs: path (required), bucket (required).

supabase_storage_get_public_urlA
Read-onlyIdempotent

Get the public URL for a file in a storage bucket

Inputs: path (required), bucket (required).

supabase_storage_list_bucketsA
Read-onlyIdempotent

List all storage buckets

Inputs: no named parameters.

supabase_storage_list_filesA
Read-onlyIdempotent

List files in a storage bucket at a given path

Inputs: bucket (required), path, limit, offset, +1 more.

supabase_storage_moveA
Destructive

Move or rename a file within a storage bucket

Inputs: bucket (required), toPath (required), fromPath (required).

supabase_storage_uploadA
Destructive

Upload a file to a storage bucket (base64-encoded content)

Inputs: path (required), bucket (required), fileBody (required), upsert, +1 more.

supabase_updateA
Destructive

Update rows in a Supabase table matching the given filters

Inputs: data (required), table (required), filters (required).

supabase_upsertA
Destructive

Upsert (insert or update on conflict) rows in a Supabase table

Inputs: data (required), table (required), onConflict, ignoreDuplicates.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 21 tools

    Disambiguation5/5

    Tools are cleanly separated into database, auth, storage, and functions domains, each with distinct actions. There is no overlap; e.g., supabase_insert, supabase_update, and supabase_upsert are clearly differentiated by their descriptions.

    Naming Consistency4/5

    All tool names use snake_case and follow a consistent 'supabase_' prefix. The pattern is mostly verb_noun (e.g., supabase_storage_create_bucket), but database tools like supabase_query and supabase_insert lack a domain prefix, making them slightly less consistent with the auth/storage/functions groups.

    Tool Count4/5

    21 tools is on the heavier side, but the server covers four distinct Supabase subsystems (database, auth, storage, functions), each with a reasonable set of operations. The count is justified for the broad scope, though it approaches the upper boundary.

    Completeness4/5

    The tool set provides solid CRUD coverage for database rows and users, plus file operations and RPC/function invocation. Minor gaps exist, such as missing storage bucket update/delete and lack of detailed schema inspection beyond listing tables, but these are not critical for most workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      C
      maintenance
      Enables querying Supabase databases and generating TypeScript types through the Model Context Protocol interface, supporting features like schema selection, column filtering, and pagination.
      2
      14
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Implements the Model Context Protocol to provide LLMs with tools for interacting with Supabase databases, supporting operations like reading, creating, updating, and deleting records with filtering and pagination capabilities.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables minimal interaction with Supabase databases through 4 essential tools for data querying, mutations, file storage, and user authentication. Designed for 70% less context usage than standard implementations with auto-truncated results and simplified parameters.
      2
      MIT