Skip to main content
Glama
ClearMind1

minio_mcp

by ClearMind1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to minio_mcp

No user-submitted related servers found.

    Related Servers

    • saveformedearai

      bramato
      A
      license
      A
      quality
      D
      maintenance
      MCP server for uploading, listing, and retrieving files on S3-compatible storage (AWS S3, DigitalOcean Spaces) with public/private access and temporary URLs.
      4
      5 npm
      MIT

    • @zhigang1992/uploadfile-mcp

      zhigang1992
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables users to upload local files to S3-compatible storage and retrieve shareable public URLs. Files are automatically organized into unique UUID-based folders to prevent naming conflicts while preserving original filenames.
      13 npm
      MIT

    • MinIO MCP Server

      Rafitis
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides a bridge between MCP-compatible clients and MinIO object storage. It exposes MinIO operations as MCP tools for seamless bucket management and object operations.
      4
      -

    • MinIO PUT MCP Server

      zymeli
      A
      license
      A
      quality
      A
      maintenance
      A PUT-only MCP server for MinIO that enables file, batch, and streaming uploads with automatic date/machine/file path organization and metadata generation for data archiving.
      3
      4 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.6/5.0

    Scored across 2 tools

    Disambiguation2/5

    The two tools have overlapping purposes—both upload files to MinIO—with only minor distinctions in input format (base64 vs. local file). An agent could easily misselect between them if the input format isn't clearly specified, as the core action is identical. The descriptions help differentiate, but the fundamental overlap in functionality creates ambiguity.

    Naming Consistency5/5

    The tool names follow a perfectly consistent verb_noun pattern: both start with 'upload', followed by a descriptor ('base64' or 'file'), and end with 'to_minio'. This predictable naming scheme makes it easy for agents to understand and select tools without confusion.

    Tool Count2/5

    With only 2 tools, the server feels severely under-scoped for a MinIO integration, which typically involves operations like listing, downloading, deleting, or managing buckets. The count is too low to cover the basic CRUD/lifecycle needs of file storage, limiting agent functionality.

    Completeness1/5

    The tool surface is extremely incomplete for a MinIO server, covering only upload operations with no ability to retrieve, list, delete, or manage files or buckets. This creates significant gaps that will cause agent failures in most file storage workflows, as agents cannot perform basic operations beyond uploading.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources