Skip to main content
Glama
stufently

beget-s3-mcp-ai-cli

by stufently
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to beget-s3-mcp-ai-cli

No user-submitted related servers found.

    Related Servers

    • 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

    • yandex-s3-mcp-ai-cli

      stufently
      A
      license
      C
      quality
      A
      maintenance
      Yandex 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

    • 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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct resources/actions (get, head, list, prefix usage, largest objects). However s3_list_multipart_uploads and s3_unfinished_uploads overlap heavily—both surface incomplete uploads—and s3_get_object vs s3_preview_object have some boundary fuzziness, though the descriptions help differentiate.

    Naming Consistency5/5

    Every tool uses a uniform s3_ prefix with consistent snake_case verb_noun structure (s3_get_object, s3_list_buckets, s3_prefix_usage). The pattern is entirely predictable.

    Tool Count4/5

    Ten tools is well-scoped for an S3 inspection/analytics surface, with each tool earning a place. A couple of the analytics tools (largest_objects, prefix_usage) could arguably be merged, but nothing feels bloated.

    Completeness3/5

    The surface is read-only and covers listing, metadata, content retrieval, and analytics well, but lacks any write/lifecycle operations (put, delete, copy, presign). Notably s3_get_object instructs users to 'use presign for larger objects' yet no presign tool exists—a dead end for large-object retrieval.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources