Skip to main content
Glama
atengk

@atengk/mcp-server-s3

by atengk

Related Servers

Alternatives to @atengk/mcp-server-s3

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to interact with MinIO/S3 object storage, supporting bucket and object operations like listing, reading, writing, and generating presigned URLs.
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to interact with any S3-compatible storage (AWS S3, LocalStack, MinIO) via MCP, providing tools like list, read, write, delete objects and buckets.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to explore and manage S3-compatible object storage (AWS S3, RustFS, MinIO, Cloudflare R2) by listing buckets and objects, inspecting metadata, and reading object contents with capped range requests. Write operations such as upload and delete are available but disabled unless explicitly enabled, with optional bucket allow-listing and custom TLS trust.
      6
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      Enables AI models to interact with Akave's S3-compatible storage by providing tools for managing storage buckets and objects through standardized Model Context Protocol (MCP).
      13
      32 npm
      3
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with S3-compatible storage services like AWS S3 and Cloudflare R2, supporting bucket management, object listing, reading, uploading, and deletion operations.
      5
      121 npm
      ISC
    • F
      license
      A
      quality
      D
      maintenance
      Provides tools for interacting with MinIO and S3-compatible object storage through MCP clients like Claude. It enables comprehensive bucket and object management, including listing, creating, uploading, and generating presigned URLs.
      13
      2
      -

    TDQS

    C2.9/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: copy vs move, single/batch/prefix delete, text vs range read, file vs text upload. Minor overlap exists between list_objects and search_objects (both can return object keys by prefix) and between read_object_text and read_object_range, but the descriptions clarify their intended scopes.

    Naming Consistency4/5

    Nearly all tools follow a predictable snake_case verb_noun pattern (list_buckets, create_bucket, delete_object, get_object_tags). Minor deviations include s3_ping (service prefix instead of a verb) and delete_objects_batch/by_prefix (extra qualifiers), but the overall convention is consistent.

    Tool Count3/5

    21 tools is on the heavy side for the rubric's 16-25 range. While S3 is a broad domain and most tools serve distinct needs, there are three deletion tools, two read tools, and two write tools that could arguably be consolidated, making the surface feel somewhat fragmented.

    Completeness4/5

    Core lifecycle coverage is strong: bucket create/list/delete/location, object CRUD, copy/move, tags get/set, presigned URLs, and diagnostics. Gaps remain for advanced S3 features such as multipart upload, versioning, ACLs/policies, and metadata updates beyond tags, but agents can work around these for common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive