Supabase Management MCP Server
by ubeydtalha
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port | 3200 |
| SUPABASE_URL | Yes | Supabase project URL (e.g. https://supabase.example.com) | |
| FUNCTIONS_PATH | No | Path to edge function files | /functions |
| STUDIO_MCP_URL | No | Enables Studio MCP proxy | |
| MIGRATIONS_PATH | No | Path to migration SQL files | /migrations |
| EDGE_CONTAINER_NAME | No | Edge runtime Docker container name | supabase-functions |
| SUPABASE_MGMT_API_KEY | Yes | API key to connect to the MCP server | |
| SUPABASE_MGMT_API_KEYS | No | Additional API keys (comma-separated) | |
| SUPABASE_SERVICE_ROLE_KEY | Yes | Service role key (for admin operations) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessNo issues