Skip to main content
Glama
Sign In
Supabase Storage MCP Server

Supabase Storage MCP Server

by danizeap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get a shareable link (signed)

get_signed_url

Generate a time-limited signed URL to privately share a file from Supabase Storage. Anyone with the link can view the file until it expires, adjustable from 1 to 30 days.

Instructions

Create a temporary shareable link to a file. This works for PRIVATE buckets: anyone with the link can view the file until it expires. The default link lasts 7 days; you can ask for anywhere from 1 to 30 days. Use this to share media that shouldn't be public forever.

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_signed_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketYesThe bucket the file is in.
file_pathYesPath to the file inside the bucket, e.g. 'logo.png' or 'logos/logo.png'. Use 'list_files' to find it.
expires_in_daysNoHow many days the link stays valid. Default 7, maximum 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Discloses key behaviors: temporary link, expiry duration, default 7 days, range 1-30, and that anyone with the link can view. No annotations provided, so description carries full burden; still lacks details about revocability or link format, but sufficient.

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, no fluff, front-loaded with action verb. Efficient and well-organized.

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 purpose, usage context, parameter hints, and behavior. Lacks explicit mention of return value (signed URL), but for a simple tool this is minor. Could mention link expiry more prominently.

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?

All three parameters have schema descriptions; the tool description adds context (use list_files to find file_path, default expiry). Schema coverage is 100%, and description enhances understanding beyond raw 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?

Description clearly states the tool creates a temporary shareable link for files in private buckets, distinguishing it from siblings like get_public_url.

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?

Explicitly states it works for private buckets and hints at when not to use (public buckets), though does not name specific alternatives like get_public_url directly.

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