MinIO

You are running a FastMCP-based MCP server that exposes a STDIO transport to your client applications and uploads content to MinIO. This setup lets you send text or base64 data to MinIO through an MCP interface, with automatic object naming and optional bucket handling for easy storage integration.

How to use

This server provides a standard STDIO MCP endpoint. To use it, configure your MCP client to launch the server process and point it to MinIO using the exposed environment variables. Your client can then call the available tools to upload text or base64 content to MinIO, and rely on automatic object naming to avoid collisions.

How to install

Prerequisites you need before starting are Python installed on your system and Git/Python packaging tools if you plan to install from source. You will also need network access to a MinIO server.

Step by step, set up the runtime environment and install dependencies, then start the server locally for debugging.

pip install -r requirements.txt

# Copy the example environment file and adjust values for your environment
cp .env.example .env

# On Windows
copy .env.example .env

# Start the local server (STDIO transport)
python server.py

Additional sections

Configuration, security considerations, and example client configurations are provided below. Follow these details to ensure the server runs correctly and securely in your environment.

Configuration details and environment variables are shown in concrete form in the following MCP client configurations. Use the same environment variable names when launching the STDIO server from your own tooling.

Security notes: Ensure MinIO access keys are kept secure, restrict network exposure of your MCP endpoints, and use secure transport (MINIO_SECURE=true) in production environments.

Configuration and usage notes

The server relies on these MinIO-related environment variables. You can provide them in the process environment or in a launcher script used by your MCP client.

• MINIO_ENDPOINT: Address and port of your MinIO server, for example 127.0.0.1:9000
• MINIO_ACCESS_KEY: MinIO access key
• MINIO_SECRET_KEY: MinIO secret key
• MINIO_SECURE: true or false to indicate if TLS is used
• MINIO_DEFAULT_BUCKET: Default bucket name when none is provided
• MINIO_AUTO_CREATE_BUCKET: true to auto-create the bucket if it does not exist
• MINIO_OBJECT_PREFIX: Path prefix for uploaded objects (default: uploads)
• MCP_HOST: Host the MCP server binds to (default: 0.0.0.0)
• MCP_PORT: Port the MCP server binds to (default: 8000)

MCP client configuration (stdio)

This is the JSON configuration you place in your MCP client to connect to the local STDIO server exposed by this project.

{
  "mcpServers": {
    "minio": {
      "type": "stdio",
      "command": "minio-mcp",
      "args": [],
      "env": {
        "MINIO_ENDPOINT": "127.0.0.1:9000",
        "MINIO_ACCESS_KEY": "your-access-key",
        "MINIO_SECRET_KEY": "your-secret-key",
        "MINIO_SECURE": "false",
        "MINIO_REGION": "us-east-1",
        "MINIO_DEFAULT_BUCKET": "your-bucket"
      },
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Alternative local start method

If you prefer starting the server by directly invoking Python, you can run the server with a local working directory configured.

{
  "mcpServers": {
    "minio": {
      "type": "stdio",
      "command": "python",
      "args": ["server.py"],
      "cwd": "d:/code/MCP/minio_mcp",
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Available tools

upload_text_to_minio

Uploads UTF-8 text content to MinIO, generating a unique object path if no object_name is provided.

upload_base64_to_minio

Uploads content provided as a base64 string to MinIO, generating a unique object path if no object_name is provided.