supabase-secure
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MODE | No | Scope control mode for the MCP server. Defaults to READ_ONLY, blocking state-modifying operations unless an explicit admin token is provided. | READ_ONLY |
| ADMIN_TOKEN | No | Explicit admin token required to authorize state-modifying operations when using scope control. | |
| SUPABASE_URL | Yes | Your Supabase project URL. | |
| SUPABASE_SERVICE_ROLE_KEY | Yes | Your Supabase service role 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 |
|---|---|
| get_customer_metricsC | Retrieves aggregated customer metrics. Read-only execution. |
| update_customer_statusB | Updates account status for a customer UUID. Mutation (Requires Admin Scope). |
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 2 tools
The two tools have clearly distinct purposes: one read-only metrics retrieval and one admin-scoped customer status mutation. An agent can easily tell them apart by action and resource.
Both tools follow a consistent snake_case verb_noun pattern: get_customer_metrics and update_customer_status. The naming is predictable and readable.
Two tools is thin for a server named supabase-secure, even if each tool is meaningful. It feels like a narrow slice of a broader secure customer-management surface.
The surface covers customer metrics retrieval and status updates but lacks obvious related operations such as listing customers, getting a customer, reading current status, or creating/deleting customer records. These gaps could force agents into dead ends.