Supabase Storage MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment mode | development |
| LOG_LEVEL | No | Logging verbosity | info |
| SUPABASE_URL | Yes | Your Supabase project URL | |
| SUPABASE_SERVICE_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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_bucketB | Create a new storage bucket with comprehensive security validation and audit logging |
| setup_bucketsC | Initialize standard storage buckets for organized file management workflows |
| upload_image_batchC | Upload multiple images to designated bucket and folder (supports both file paths and base64 data) |
| list_filesC | Enumerate files in bucket folder for processing or download |
| get_file_urlB | Generate signed download URL for secure file access |
| get_security_statusA | Get current security configuration and audit information |
| create_signed_urlsC | Generate multiple signed download URLs in a single request for batch operations |
| download_fileC | Download file content directly with optional image transformations |
| download_file_with_auto_triggerC | Download file with optional auto-download trigger and custom filename support |
| batch_downloadC | Download multiple files with optional auto-download triggers and batch processing |
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 10 tools
There is significant overlap between download-related tools (batch_download, download_file, download_file_with_auto_trigger, get_file_url, create_signed_urls) that could cause confusion about which to use for different download scenarios. However, the descriptions help clarify some distinctions like batch operations versus single file downloads. The upload and bucket management tools are more clearly differentiated.
Most tools follow a consistent verb_noun pattern (create_bucket, download_file, list_files, upload_image_batch) with clear action-oriented names. The main deviation is 'get_file_url' and 'get_security_status' which use 'get' instead of more specific verbs like 'generate' or 'retrieve', but overall the naming is quite readable and predictable.
With 10 tools, this is a reasonable number for a storage management server. The count feels slightly high due to the multiple overlapping download tools, but it covers core storage operations (upload, download, bucket management, security) without being overwhelming. A more consolidated download interface could reduce the count to be more optimal.
The toolset provides good coverage of storage operations including CRUD-like functionality (upload, download, list), bucket management (create, setup), and security features. Minor gaps include missing file deletion, bucket deletion, and file metadata updates, but agents can accomplish most storage workflows with the available tools.