scopedb-mcp
by xieweicong
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | Yes | Supabase project URL (e.g., https://xxx.supabase.co) | |
| SCOPEDB_SCOPE | Yes | Name of the scope to use (e.g., support, analytics, admin) | |
| SCOPEDB_CONFIG | Yes | Path to the ScopeDB YAML configuration file | |
| SCOPEDB_CONTEXT | No | Optional JSON string for context parameters (e.g., {"current_user_id":"user-uuid"}) | |
| SUPABASE_SERVICE_KEY | Yes | Supabase service role key (for full database access) |
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