minio_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host address for the MCP server | 0.0.0.0 |
| MCP_PORT | No | Port for the MCP server | 8000 |
| MINIO_SECURE | No | Whether to use a secure (HTTPS) connection (true/false) | |
| MINIO_ENDPOINT | Yes | MinIO server endpoint (e.g., 127.0.0.1:9000) | |
| MINIO_ACCESS_KEY | Yes | Access key for MinIO authentication | |
| MINIO_SECRET_KEY | Yes | Secret key for MinIO authentication | |
| MINIO_OBJECT_PREFIX | No | Prefix for the object path | uploads |
| MINIO_DEFAULT_BUCKET | Yes | Default bucket for uploading files | |
| MINIO_AUTO_CREATE_BUCKET | No | Whether to automatically create the bucket if it does not exist |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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 2 tools
The two tools have overlapping purposes—both upload files to MinIO—with only minor distinctions in input format (base64 vs. local file). An agent could easily misselect between them if the input format isn't clearly specified, as the core action is identical. The descriptions help differentiate, but the fundamental overlap in functionality creates ambiguity.
The tool names follow a perfectly consistent verb_noun pattern: both start with 'upload', followed by a descriptor ('base64' or 'file'), and end with 'to_minio'. This predictable naming scheme makes it easy for agents to understand and select tools without confusion.
With only 2 tools, the server feels severely under-scoped for a MinIO integration, which typically involves operations like listing, downloading, deleting, or managing buckets. The count is too low to cover the basic CRUD/lifecycle needs of file storage, limiting agent functionality.
The tool surface is extremely incomplete for a MinIO server, covering only upload operations with no ability to retrieve, list, delete, or manage files or buckets. This creates significant gaps that will cause agent failures in most file storage workflows, as agents cannot perform basic operations beyond uploading.