Skip to main content
Glama
danizeap

Supabase Storage MCP Server

by danizeap

Create a storage bucket

create_bucket

Create a Supabase Storage bucket with required naming prefix (e.g., marketing, brand). Set access to private or public, and optionally specify allowed MIME types and file size limit.

Instructions

Create a new Supabase Storage bucket. Bucket names must start with one of: marketing, brand, campaigns, media, assets, then use lowercase letters, numbers, and dashes (for example: "marketing-q3-launch" or "brand-logos"). By default the bucket is PRIVATE (files need a signed link to view), accepts common media (images, video, audio, PDF), and limits files to 50MB. Set public=true only for assets meant to be shared openly on the web. If the name breaks the convention or already exists, creation fails with a clear explanation — nothing is overwritten.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesBucket name. Must match the convention, e.g. "marketing-q3-launch" or "brand-logos".
publicNotrue = anyone with the URL can view files (for openly shared assets). false (default) = private; files need a signed link.
allowed_mime_typesNoOptional list of allowed file types, e.g. ["image/*", "application/pdf"]. Defaults to common media types.
file_size_limit_mbNoOptional maximum file size in megabytes. Defaults to 50.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully discloses behavior: default privacy, allowed MIME types, file size limit, naming rules, and failure handling (clear error, no overwrite). This gives the agent a complete behavioral model.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loaded with the action, and every sentence adds useful information. No redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers creation behavior well but does not describe the return value (e.g., bucket ID) or any side effects beyond failure. Still, given no output schema and the context of sibling tools, it is sufficiently complete for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but description adds value beyond schema by explaining naming pattern, defaults, and appropriate use of public flag. It enriches understanding without repeating the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it creates a new storage bucket. It distinguishes itself from siblings like upload_file or list_buckets by using specific verb 'create' and resource 'bucket'. No ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides guidance on when to set public=true and naming conventions. However, it does not explicitly contrast with sibling tools or state when not to use it, which would make it stronger.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danizeap/Supabase-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server