MinIO / AIStor MCP server

What is MinIO / AIStor MCP server?

It is a Model Context Protocol (MCP) server for interacting with MinIO servers. It provides functions for listing buckets and objects, uploading and downloading files, getting and setting object tags, and retrieving server status and admin information.

How to use MinIO / AIStor MCP server?

Download the executable from the Releases page, set the MINIO_ENDPOINT, MINIO_ACCESS_KEY, and MINIO_SECRET_KEY environment variables, then configure your MCP client (e.g., Claude Desktop) with the server command. Optionally add --allow-write, --allow-delete, or --allow-admin flags to extend permissions.

Key features of MinIO / AIStor MCP server

• List buckets and objects on a MinIO server.
• Upload and download files to/from buckets.
• Get and set object tags.
• Retrieve admin information (nodes, drives, usage).
• Read-only by default; write and delete controlled by flags.

Use cases of MinIO / AIStor MCP server

• Ask an AI assistant to list all buckets on your MinIO server.
• Have the AI download a file from a bucket to your local desktop.
• Request a summary of server health and storage usage.
• Upload documents from your computer to a specific bucket via chat.
• Create new buckets or delete objects with proper permissions.

FAQ from MinIO / AIStor MCP server

How do I protect my MinIO server when using this MCP?

Create a separate MinIO user with read-only access and attach the readonly policy. For diagnostics, also attach the diagnostics policy. Never use admin credentials.

What happens in read-only mode?

By default the server starts in read-only mode, allowing only listing, reading, and getting object tags. Write, delete, and admin operations require explicit flags.

How do I enable write or delete operations?

Add --allow-write and/or --allow-delete flags to the server arguments in your client configuration file. Enable them only when needed and remove them afterward.

Can I run the server as a container instead of a binary?

Yes. The README provides a configuration example using Podman (or Docker) with environment variables for the MinIO endpoint and credentials, and mounted host directories.

What are the runtime requirements?

A running MinIO server (or the playground at play.min.io), MinIO credentials, and a macOS or Linux host. No additional runtime or dependencies are needed beyond the single executable.