supabase-mcp-server
Allows interaction with Supabase services including Database (query, insert, update, delete, upsert, RPC, list tables), Auth (list, get, create, update, delete users), Storage (list buckets, create bucket, list files, upload, download, delete, get public URL, move), and Edge Functions (invoke).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@supabase-mcp-server list all tables in the database"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Install dependencies:
npm installCopy
.env.exampleto.envand fill in your Supabase credentials:cp .env.example .envBuild:
npm run buildRun:
npm start
Related MCP server: Supabase MCP Server
Environment Variables
Variable | Required | Description |
| Yes | Your Supabase project URL |
| Yes | Service role key (found in Project Settings > API) |
| No | Transport mode: |
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 outputTesting with MCP Inspector
npx @modelcontextprotocol/inspector node dist/index.jsAvailable Tools
21 toolssupabase_auth_create_userBDestructive
Create a new user with email/password or phone
Inputs: email, phone, password, emailConfirm, +2 more.
supabase_auth_delete_userBDestructive
Delete a user by their ID
Inputs: userId (required).
supabase_auth_get_userARead-onlyIdempotent
Get a single user by their ID
Inputs: userId (required).
supabase_auth_list_usersARead-only
List all users with pagination
Inputs: page, perPage.
supabase_auth_update_userADestructive
Update a user's email, password, phone, or metadata
Inputs: userId (required), email, phone, password, +2 more.
supabase_deleteADestructive
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_insertBDestructive
Insert one or more rows into a Supabase table
Inputs: data (required), table (required), onConflict.
supabase_list_tablesBRead-onlyIdempotent
List all tables in the database schema
Inputs: schema.
supabase_queryARead-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_bucketBDestructive
Create a new storage bucket
Inputs: name (required), public, fileSizeLimit, allowedMimeTypes.
supabase_storage_deleteADestructive
Delete files from a storage bucket
Inputs: paths (required), bucket (required).
supabase_storage_downloadARead-onlyIdempotent
Download a file from a storage bucket (returns base64)
Inputs: path (required), bucket (required).
supabase_storage_get_public_urlARead-onlyIdempotent
Get the public URL for a file in a storage bucket
Inputs: path (required), bucket (required).
supabase_storage_list_bucketsARead-onlyIdempotent
List all storage buckets
Inputs: no named parameters.
supabase_storage_list_filesARead-onlyIdempotent
List files in a storage bucket at a given path
Inputs: bucket (required), path, limit, offset, +1 more.
supabase_storage_moveADestructive
Move or rename a file within a storage bucket
Inputs: bucket (required), toPath (required), fromPath (required).
supabase_storage_uploadADestructive
Upload a file to a storage bucket (base64-encoded content)
Inputs: path (required), bucket (required), fileBody (required), upsert, +1 more.
supabase_updateADestructive
Update rows in a Supabase table matching the given filters
Inputs: data (required), table (required), filters (required).
supabase_upsertADestructive
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
Scored across 21 tools
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.
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.
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.
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
Related MCP Connectors
Your Supabase account in natural language: run SQL, apply migrations, manage tables, storage, edge f
Supabase-compatible Postgres for agents: projects, branches, SQL, auth, storage, email.
Manage Supabase projects end to end across database, auth, storage, realtime, and migrations. Moni…
MCP server for interacting with the Supabase platform
Related MCP Servers
- FlicenseBqualityCmaintenanceEnables querying Supabase databases and generating TypeScript types through the Model Context Protocol interface, supporting features like schema selection, column filtering, and pagination.214-
- FlicenseNot gradedqualityDmaintenanceImplements 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.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI tools to interact with Supabase databases, providing tools for reading, creating, updating, and deleting records in Supabase tables.MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.2MIT