← Explore all mcp servers

OBJECT STORAGE / MinIO

MinIO AIStor MCP Server

MinIO's MCP server for AIStor object stores lists buckets and objects, reads metadata and tags, issues presigned URLs and answers questions about object contents. It runs as a container image from MinIO's Quay registry, starts read-only, and needs --allow-write, --allow-delete or --allow-admin for the rest. The repository is archived and holds no source or licence file.

“This is a Model Context Protocol (MCP) server for interacting with AIStor object stores.”

01 / THE REASONING

Why this made the selection.

  • The README splits its operations into read, AI, write, delete and admin groups, and says that without any --allow-* flag the server runs read-only; write, delete and admin each need their own flag.
  • The README lists all 26 tools by name; its configurations pass --allowed-directories, and list_allowed_directories reports the directories permitted for operations with the server.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md at def0b4e2b7fa691016f75e7b51ee8880dcf1b2ed: read, AI, write, delete and admin operations; the Claude for Desktop container configuration; the StreamableHTTP container command; the tool list; the 2025-05-28 update.
  • Repository contents at the same revision: .gitignore, README.md and glama.json only; no LICENSE file, manifest or source.
  • GitHub API repository metadata on 2026-10-13: archived true, no licence detected, last push 2025-05-28.
  • Quay tag API for quay.io/minio/aistor/mcp-server-aistor on 2026-10-13: tag latest and RELEASE.2025-05-28T17-22-30Z share one digest, last modified 2025-05-28.
  • MinIO blog post "Introducing MCP server for AIStor" (blog.min.io now redirects to www.min.io/blog): works with AIStor and the community edition; ask-object is AIStor-specific.

Our findings

  • Without any --allow flag the server runs read-only, which the README states explicitly.
  • The default listing cap is 1000 objects, raised with --max-keys for wider context windows.
  • ARCHIVED: the GitHub API reports archived: true for https://github.com/minio/mcp-server-aistor (checked 2026-10-13). The record is kept; whether it stays listed is the controller's decision.
  • The README lists 26 tools, including copy_object, move_object, delete_bucket, delete_object, set_bucket_versioning, get_admin_info, download_object and upload_object. text_to_object was added on 2025-05-28.
  • configExample is the README's Claude for Desktop block at this commit. The previous configExample used docker and omitted the volume, MINIO_USE_SSL, --allowed-directories and --allow-* arguments, so it was not the README's block.
  • The server acts with the access and secret keys passed in the container environment; no other authentication is documented. In --http mode it listens on the published port at /mcp.

Not established by this review

  • The container image was not pulled or run; no object store was connected.
  • The 2025-05-28 image was not inspected for a licence file.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Install Docker or Podman and obtain the object store's endpoint and credentials (the README points to the MinIO Playground for testing).
  2. Add the README's container configuration to the MCP client, replacing the endpoint, credential and YOUR_USERNAME placeholders.
  3. Remove --allow-write, --allow-delete and --allow-admin unless those surfaces are needed; without them the server is read-only.

Before you start

  • Docker or Podman installed.
  • An AIStor or MinIO object store endpoint with access keys.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "aistor": {
      "command": "podman",
      "args": [
        "run",
        "-i",
        "--rm",
        "-v",
        "/Users/YOUR_USERNAME/Downloads:/Downloads",
        "-e",
        "MINIO_ENDPOINT=REPLACE_WITH_ENDPOINT",
        "-e",
        "MINIO_ACCESS_KEY=REPLACE_WITH_ACCESS_KEY",
        "-e",
        "MINIO_SECRET_KEY=REPLACE_WITH_SECRET_KEY",
        "-e",
        "MINIO_USE_SSL=true",
        "quay.io/minio/aistor/mcp-server-aistor:latest",
        "--allowed-directories",
        "/Downloads",
        "--allow-write",
        "--allow-delete",
        "--allow-admin"
      ]
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/minio/mcp-server-aistor/blob/def0b4e2b7fa691016f75e7b51ee8880dcf1b2ed/README.md

    Supports: summary, upstreamDescription, install, configExample, compatibility, limitations, access, transports, whySelected, tools

  2. Repository (archived) ↗Checked

    https://github.com/minio/mcp-server-aistor

    Supports: archived status, no licence file

  3. https://quay.io/repository/minio/aistor/mcp-server-aistor?tab=tags

    Supports: latest tag last modified 2025-05-28

  4. https://www.min.io/blog/mcp-server-for-aistor

    Supports: bestFor, limitations, community edition and ask-object

Evidence & Ask