Supabase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_API_KEY | Yes | Your Supabase API key |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsC | List all Supabase projects |
| get_projectB | Get details of a specific Supabase project |
| create_projectC | Create a new Supabase project |
| delete_projectC | Delete a Supabase project |
| list_organizationsB | List all organizations |
| get_organizationC | Get details of a specific organization |
| create_organizationC | Create a new organization |
| get_project_api_keysC | Get API keys for a specific Supabase project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are organized around two main resources (organizations and projects) with specific CRUD operations, making it easy for an agent to select the right tool without confusion.
All tools follow a consistent verb_noun pattern throughout (e.g., create_organization, list_projects, get_project). The naming is predictable and readable, with no deviations in style or convention.
With 8 tools, the server is well-scoped for managing Supabase organizations and projects. Each tool earns its place by covering essential CRUD operations, and the count is appropriate for the domain without being overwhelming or insufficient.
The tool set provides strong coverage for organizations and projects, including create, get, list, and delete operations. A minor gap exists in missing update operations (e.g., update_organization or update_project), but agents can work around this with delete and recreate if needed.