Add the MinIO MCP server to VS Code
Config last verified Jun 1, 2026
The exact config to run MinIO in VS Code — paste it in, restart, and the tools load.
Prerequisites
- VS Code 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 .vscode/mcp.json
2. Add this configuration
Add to .vscode/mcp.json
.vscode/mcp.json
json
{
"servers": {
"minio": {
"type": "stdio",
"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>"
}
}
}
}Heads up
- VS Code uses the `servers` key (not `mcpServers`) and requires `type`.
3. Restart VS Code and confirm the MinIO tools load.
Gotchas
- VS Code uses the `servers` key (not `mcpServers`) and requires `type`.
VS Code is the exception to every other client: its top-level key is "servers", not "mcpServers", and each entry needs an explicit "type" (for example "http" or "stdio"). Secrets are not inlined; instead you declare an "inputs" array and reference each value as ${input:id}, so VS Code prompts for it once and never writes it to disk. Remote servers connect natively with OAuth.