A GUI for MinIO buckets.
Stream Vessel lets you browse and manage MinIO through a file-manager-style interface. Point a connection at your MinIO endpoint, turn on path-style URLs if your server needs them, and work in your buckets with a folder tree, search, an editor and uploads.
What Stream Vessel adds to MinIO
MinIO is often self-hosted, and people reach for the command line or a separate console to look inside buckets. Stream Vessel gives MinIO the same explorer as AWS and the other providers, next to them in the same window, so you can compare or copy between a MinIO bucket and a cloud bucket.
Stream Vessel is an S3 browser and file manager for AWS S3 and every S3-compatible provider. MinIO is a preset in the connection dialog.
Connection details
| Endpoint | Your MinIO API URL, for example https://minio.example.com |
|---|---|
| Region | Your server's configured region; MinIO defaults to us-east-1 |
| Credentials | A MinIO access key and secret key, ideally a service account with a limited policy |
Connect MinIO to Stream Vessel
- In MinIO, create an access key (service account) with a policy that covers the buckets Stream Vessel should reach.
- In Stream Vessel, add a connection, pick MinIO and enter your server's API URL and keys.
- Under Advanced, turn on path-style URLs unless your server is set up for virtual-host-style bucket names.
- Test the connection, save, and your buckets appear in the explorer.
What you can do with MinIO in Stream Vessel
The same features work on every provider. The editions differ: sharing and AI access need a Stream Vessel Cloud account. All S3 browser features.
| Feature | Stream Vessel Cloud | Chrome extension |
|---|---|---|
| Browse buckets and folders: tree, file list, s3:// breadcrumbs | ✓ Available | ✓ Available |
| Several panes side by side, each on its own connection | ✓ Available | ✓ Available |
| Upload files and folders, multipart for large files | ✓ Available | ✓ Available |
| Copy between connections and providers | ✓ Available | ✓ Available |
| Rename objects and folders | Soon | Soon |
| Edit text and code in place | ✓ Available | ✓ Available |
| Read and edit object metadata | ✓ Available | ✓ Available |
| Search a folder or a whole bucket | ✓ Available | ✓ Available |
| Presigned links with an expiry, single and bulk | ✓ Available | ✓ Available |
| Share a connection, bucket or folder with people | ✓ Available | – Not available |
| AI access over MCP | ✓ Available | – Not available |
| Send to and import from Google Drive | ✓ Available | ✓ Available |
Sharing, AI access and transfers with MinIO
- Share MinIO access without sharing keys. On Stream Vessel Cloud, share a MinIO connection, bucket or folder by email at READ, WRITE or FULL, and revoke it in one click. How secure S3 sharing works.
- Give AI agents access to MinIO. An MCP token with a tier and an expiry lets Claude Code, Cursor or another MCP client work in your MinIO buckets, with every call logged. S3 access for AI agents.
- Copy between MinIO and other storage. Open MinIO next to any other connection and drag or paste to copy across providers, or send files to Google Drive. Cloud storage transfers.
- Keys stay yours. In the Chrome extension your MinIO keys never leave your browser. On Cloud they are encrypted with AES-256 and never shown to the people or agents you give access. Where keys are stored.
Good to know about MinIO
-
Path-style URLs. Most MinIO deployments address buckets as
https://host/bucket, nothttps://bucket.host. Turn on path-style URLs in the connection's advanced options. - A MinIO on your laptop or network: use the Chrome extension. The extension calls your endpoint directly from your browser, so it can reach a MinIO that is only on your machine or local network. Keys stay in your browser profile.
-
Stream Vessel Cloud and AI access need a public HTTPS endpoint. Cloud is served over HTTPS, so browsers will not let it talk to an
http://endpoint. AI access over MCP runs on Stream Vessel's servers, so the endpoint must also be reachable from the internet. -
CORS is set server-wide. MinIO handles CORS for the whole server rather than per bucket, so Cloud may show the bucket CORS status as "Invalid or N/A". If your server restricts allowed origins, allow
https://app.streamvessel.com. The extension does not need CORS.