Skip to main content
Glama
stufently

yandex-s3-mcp-ai-cli

by stufently
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to yandex-s3-mcp-ai-cli

No user-submitted related servers found.

    Related Servers

    • vkcloud-s3-mcp-ai-cli

      stufently
      A
      license
      C
      quality
      A
      maintenance
      VK Cloud S3 MCP server and Go CLI: browse, preview and restore files in a bucket. Read-only by default; write, delete and admin tools only behind switches, destructive calls confirmed by a person.
      14
      MIT

    • selectel-s3-mcp-ai-cli

      stufently
      A
      license
      C
      quality
      A
      maintenance
      Selectel S3 MCP server and Go CLI: browse, preview and restore files in a bucket. Read-only by default; write, delete and admin tools only behind switches, destructive calls confirmed by a person.
      13
      MIT

    • beget-s3-mcp-ai-cli

      stufently
      A
      license
      C
      quality
      A
      maintenance
      Beget S3 MCP server and Go CLI: browse, preview and restore files in a bucket. Read-only by default; write, delete and admin tools only behind switches, destructive calls confirmed by a person.
      10
      1
      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.8/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target a distinct resource+read operation (buckets, objects, versions, tags, parts, usage). The main ambiguity is s3_list_multipart_uploads vs s3_unfinished_uploads, which both surface unfinished multipart uploads (one filtered by age); get/head/preview also overlap slightly on reading object data, but descriptions differentiate the intent.

    Naming Consistency4/5

    Everything shares the s3_ prefix and snake_case, which is predictable. Minor deviations exist: largest_objects, prefix_usage, and unfinished_uploads drop the leading verb, and presign_get inverts the verb/noun order, so the verb_noun pattern isn't perfectly uniform.

    Tool Count5/5

    14 tools sit squarely in the well-scoped 3-15 range and each maps to a plausible inspection task (list, get, head, tags, versions, multipart, presign, usage, preview). No filler or redundant tools beyond the minor upload overlap.

    Completeness4/5

    The surface reads as a read-only S3 inspection/analysis domain and covers buckets, objects, versions, tags, multipart uploads, presigning, and usage aggregation well. Gaps are minor for that scope (no object ACL read, no abort of unfinished uploads, and full-object download only via presign), which agents can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources