The top-level container in object storage. Files (objects) live inside buckets, the way files live inside folders, but a bucket is the account-level grouping with its own access rules. An agent lists buckets to pick the right one, then works with the objects inside it.

How does this pair with uploading a file?

Listing buckets finds the container; uploading puts an object in it. An agent lists buckets to choose the destination, holds that bucket, then uploads or reads objects there. The bucket is the where; the object operations are the what.

MCP servers that can list storage buckets

3 verified servers expose a tool that can list storage buckets

Object storage organizes everything into buckets, and an agent that uploads a file, reads one back, or audits what is stored first has to know which buckets exist. Listing buckets returns them, so the agent picks the right container before it reads or writes.

These verified servers let an agent list the storage buckets in an account or project.

Top pick

Cloudflare

Official

Cloudflare's remote MCP servers: build and manage Workers, KV, R2, D1, and Hyperdrive from an agent.

cloud-infra3,806

Tool:

r2_buckets_list

Cloudflare's r2_buckets_list returns the R2 buckets on your account, the containers an agent picks from before reading or writing objects.

Pick 2

Supabase

Supabase (community)

Community

Connects agents to a Supabase project: run SQL, inspect schema, read logs, and manage edge functions.

databases2,710

Tool:

list_storage_buckets

On Supabase, list_storage_buckets returns a project's storage buckets, the read behind working with files in Supabase Storage.

Pick 3

MinIO

Official

MinIO's official MCP server lets agents browse buckets, read and write objects, manage tags and versioning, and ask AI questions about stored objects.

file-storage41

Tool:

list_buckets

For an S3-compatible object store, list_buckets returns the buckets and their basic info, the inventory an agent manages storage from.

What to know

A bucket is the top-level container in object storage, and listing them is the first step into a store an agent does not already know. The three servers return the buckets the connection can see: Cloudflare the R2 buckets on the account, Supabase the storage buckets in a project, MinIO the buckets in the object store. From the list the agent picks the bucket it means to work in, then lists or uploads objects within it. It is also how an agent confirms it is pointed at the right account and which buckets that connection exposes.

The set of buckets is stable, so an agent that learns the layout once can hold it rather than re-list every session. Remembering which bucket holds which kind of object, uploads here, backups there, lets it go straight to the right container instead of re-enumerating the store each time.

Questions

What is a bucket?: The top-level container in object storage. Files (objects) live inside buckets, the way files live inside folders, but a bucket is the account-level grouping with its own access rules. An agent lists buckets to pick the right one, then works with the objects inside it.
How does this pair with uploading a file?: Listing buckets finds the container; uploading puts an object in it. An agent lists buckets to choose the destination, holds that bucket, then uploads or reads objects there. The bucket is the where; the object operations are the what.