Skip to main content
Glama
Sign In
Supabase Storage MCP Server

Supabase Storage MCP Server

by danizeap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get a public web link

get_public_url

Retrieve the permanent public web link for a file stored in a public Supabase Storage bucket. Use this for openly shared assets like logos and campaign images.

Instructions

Get the permanent public web link for a file. This only works for PUBLIC buckets — files anyone can view. If the bucket is private, this explains that and points you to 'get_signed_url' for a temporary link instead. Use this for logos, campaign images, and other openly shared assets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bucket": "<bucket>",
      "file_path": "<file_path>"
    },
    "name": "get_public_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketYesThe bucket the file is in (must be a public bucket).
file_pathYesPath to the file inside the bucket, e.g. 'logo.png' or 'logos/logo.png'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, description carries full burden. It discloses behavior for both public and private buckets, but doesn't specify exact return format (e.g., URL string). Still highly transparent.

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?

Three sentences, each serving a purpose: statement, conditional, use case. No fluff.

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

Completeness5/5

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

Complete for the tool's purpose: explains behavior, parameter constraints, and offers guidance for edge case (private bucket). No output schema needed.

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

Parameters3/5

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

Schema coverage is 100%, baseline 3. Description adds extra context (e.g., example paths) but doesn't significantly enhance beyond 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 the action ('get the permanent public web link for a file') and distinguishes from sibling 'get_signed_url' by specifying it works only for public buckets.

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

Usage Guidelines5/5

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

Explicitly says when to use (public buckets, logos, campaign images) and when not to (private buckets), and points to the alternative 'get_signed_url'.

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

Deploy Server

Other Tools