supabase-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DB_ROLE | No | The Supabase API role to use: anon or authenticated. | anon |
| MCP_SCHEMAS | No | Comma-separated allowlist of schemas the server may access. | public |
| MCP_USER_ID | No | UUID returned by auth.uid(); required when MCP_DB_ROLE=authenticated and rejected when MCP_DB_ROLE=anon. | |
| DATABASE_URL | Yes | Postgres connection string for a role that can SET ROLE anon and SET ROLE authenticated (the local postgres user can). Required. | |
| MCP_MAX_ROWS | No | Maximum number of rows returned by a tool call. Must be between 1 and 1000. | 100 |
| MCP_ALLOW_SQL | No | Set to true to register the run_select_sql tool. | false |
| MCP_ALLOW_WRITES | No | Set to true to register the insert_row tool. | false |
| MCP_STATEMENT_TIMEOUT_MS | No | Statement timeout in milliseconds. Must be between 100 and 60000. | 5000 |
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 | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Shows which Supabase role and user id the server queries as, which schemas are exposed, the row cap and whether SQL and writes are enabled. Never returns credentials. |
| list_tablesA | Lists tables and views in the exposed schemas that the current role can see, with whether row-level security is enabled. |
| describe_tableC | Columns (name, type, nullability, default), the RLS flag and the names and commands of RLS policies for one table. |
| select_rowsA | Reads rows from one table with structured filters (eq, neq, gt, gte, lt, lte, like, ilike, in, is_null), ordering and a limit of at most 100. Rows are filtered by RLS for role anon. No raw SQL. |
| count_rowsA | Counts rows visible to the current role, with the same structured filters as select_rows. |
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 5 tools
Each tool has a distinct scope: list_tables enumerates objects, describe_table returns schema details for one table, select_rows fetches rows, count_rows aggregates, and whoami reports session/role context. The only near-neighbours, select_rows and count_rows, are clearly separated by 'read rows' vs 'count rows' and both share the same filter vocabulary.
Four of five tools follow a clean verb_noun snake_case pattern (list_tables, describe_table, select_rows, count_rows). whoami deviates from that convention, though it is a widely understood idiomatic name rather than an arbitrary break.
Five tools is a tight, well-scoped set for read-only introspection and querying of a Postgres/Supabase schema, with no redundant entries. It sits on the lean side, especially since whoami advertises SQL and write capabilities that no tool here exposes.
The read path is coherent (list → describe → select/count) and RLS awareness is covered, but describe_table omits foreign keys, indexes and constraints, and there is no way to list schemas or run arbitrary SQL despite whoami reporting those flags. Write operations are also absent, so anything beyond inspection is a dead end.