Add the MinIO MCP server to Cursor
Config last verified Jun 1, 2026
The exact config to run MinIO in Cursor — paste it in, restart, and the tools load.
Prerequisites
- Cursor 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 ~/.cursor/mcp.json
2. Add this configuration
Add to ~/.cursor/mcp.json
~/.cursor/mcp.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 Cursor and confirm the MinIO tools load.
Gotchas
Cursor keeps MCP servers under an "mcpServers" object in ~/.cursor/mcp.json for global use, and also reads a project-scoped .cursor/mcp.json so a repository can ship its own servers. Remote servers are configured with a bare "url" field and connect natively, with OAuth handled in-app when a server requires it.