MinIO MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MINIO_SECURE | No | Set to 'true' for HTTPS connection, or 'false' for HTTP. | false |
| MINIO_ENDPOINT | Yes | The MinIO server endpoint (e.g., localhost:9000). | |
| MINIO_ACCESS_KEY | Yes | The access key for MinIO/S3 storage. | |
| MINIO_SECRET_KEY | Yes | The secret key for MinIO/S3 storage. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| minio_list_bucketsB | List all buckets in MinIO storage |
| minio_make_bucketC | Create a new bucket in MinIO |
| minio_remove_bucketB | Remove an empty bucket from MinIO |
| minio_bucket_existsB | Check if a bucket exists in MinIO |
| minio_list_objectsC | List objects in a MinIO bucket |
| minio_get_objectC | Get object content from MinIO bucket |
| minio_put_objectC | Upload content as an object to MinIO bucket |
| minio_upload_fileC | Upload a local file to MinIO bucket |
| minio_download_fileB | Download an object from MinIO to a local file |
| minio_remove_objectC | Remove an object from a MinIO bucket |
| minio_stat_objectA | Get object metadata without downloading content |
| minio_presigned_urlC | Generate a presigned URL for object download |
| minio_copy_objectC | Copy an object to another location in MinIO |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Every tool has a clearly distinct purpose with no ambiguity. Each targets a specific action on a specific resource (buckets or objects), such as minio_bucket_exists for checking existence versus minio_make_bucket for creation, and minio_get_object for content retrieval versus minio_stat_object for metadata. The descriptions reinforce these distinctions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with the prefix 'minio_' and snake_case throughout. The verbs are clear and descriptive (e.g., list, get, make, remove), and the nouns specify the target (e.g., buckets, objects, bucket, object). This predictability aids agent understanding and tool selection.
With 13 tools, the count is well-scoped for a MinIO storage server, covering essential operations for bucket and object management. Each tool earns its place by addressing a specific need, such as existence checks, CRUD operations, listing, and utilities like presigned URLs, without being overly sparse or bloated.
The tool set provides complete CRUD/lifecycle coverage for the MinIO domain, including bucket operations (create, list, check, remove) and object operations (upload, download, copy, get, remove, stat, presigned URLs). There are no obvious gaps, enabling agents to handle full workflows without dead ends.