Supabase MCP Server
by ALPA-Const
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| features | No | Used to specify which tool groups to enable. Available groups are: account, docs, database, debugging, development, functions, storage, and branching. Defaults to all except storage. | |
| read_only | No | Used to restrict the server to read-only queries and tools. Recommended by default. This prevents write operations on any of your databases by executing SQL as a read-only Postgres user. | |
| project_ref | No | Used to scope the server to a specific project. If omitted, the server will have access to all projects in your Supabase account. You can find this under Project ID in your Supabase project settings. |
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