Add the MinIO MCP server to Claude Desktop

Config last verified Jun 1, 2026

The exact config to run MinIO in Claude Desktop — paste it in, restart, and the tools load.

Prerequisites

Claude Desktop installed.
MINIO_ENDPOINT — Hostname:port of your MinIO or AIStor server.
MINIO_ACCESS_KEY — Access key used to authenticate to the object store.
MINIO_SECRET_KEY — Secret key paired with the access key.

Setup

1. Open `~/Library/Application Support/Claude/claude_desktop_config.json`

On Windows the file lives at %APPDATA%\Claude\claude_desktop_config.json.

2. Add this configuration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json

~/Library/Application Support/Claude/claude_desktop_config.json

json

{
  "mcpServers": {
    "minio": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MINIO_ENDPOINT",
        "-e",
        "MINIO_ACCESS_KEY",
        "-e",
        "MINIO_SECRET_KEY",
        "-e",
        "MINIO_USE_SSL",
        "-v",
        "/path/to/local/dir:/data",
        "quay.io/minio/aistor/mcp-server-aistor:latest",
        "--allowed-directories",
        "/data"
      ],
      "env": {
        "MINIO_ENDPOINT": "<MINIO_ENDPOINT>",
        "MINIO_ACCESS_KEY": "<MINIO_ACCESS_KEY>",
        "MINIO_SECRET_KEY": "<MINIO_SECRET_KEY>",
        "MINIO_USE_SSL": "<MINIO_USE_SSL>"
      }
    }
  }
}

3. Restart Claude Desktop and confirm the MinIO tools load.

Gotchas

Claude Desktop reads MCP servers from an "mcpServers" object, but the config file is stdio-only: it cannot dial a remote URL directly. To reach a remote server you bridge it locally by running "npx mcp-remote <url>" as the command. Native remote Connectors exist on paid plans, but not through this config file, so the bridge is the portable path.

← Back to the MinIO MCP server