Skip to main content
Glama
ethersphere

Swarm MCP

Official
by ethersphere
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Swarm MCP

No user-submitted related servers found.

    Related Servers

    • mcp-ipfs

      alexbakers
      A
      license
      C
      quality
      F
      maintenance
      🪐 MCP IPFS Server This server empowers language models 🤖 and other MCP clients to manage storacha.network spaces, upload/download data, manage delegations, and perform various other tasks by seamlessly wrapping w3 commands.
      35
      40 npm
      21
      MIT

    • 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
      7 npm
      MIT

    • shelby-mcp

      Jasekeee
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Shelby Protocol that enables AI agents to read, write, and manage files on decentralized storage (Aptos) through tools like upload, download, list, delete, and account info.
      5
      1
      MIT

    • Universal MCP Gateway

      Samuel-Mencke
      F
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP gateway that aggregates all your MCP servers behind a single Streamable HTTP endpoint, with automatic registry discovery (19,000+ servers), on-demand Docker provisioning, multi-device support via SSH, OAuth2 PKCE authentication, and a workflow engine for saving and replaying multi-step tool sequences.
      -
    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

    A3.8/5.0

    Scored across 7 tools

    Disambiguation3/5

    The upload family is mostly well-separated, but `upload_file` accepts raw text content in addition to paths, making it overlap with `upload_data` for text uploads. The download pair is better distinguished by explicit routing rules, though it still relies on subtle user phrasing.

    Naming Consistency4/5

    All tools follow a readable `verb_noun` snake_case pattern (`upload_folder`, `read_feed`, etc.). Minor inconsistency: `upload_file` is singular while `download_files` is plural, and `upload_data`/`upload_file` are semantically close despite different nouns.

    Tool Count5/5

    Seven tools is a reasonable scope for a storage-plus-feed MCP server. Each tool has a clear responsibility in the workflow, even if `upload_data` partially overlaps with `upload_file`.

    Completeness2/5

    The set covers upload/download and feed read/update, but both upload tools reference `query_upload_progress` for deferred uploads, and that tool is absent from the server. Large uploads therefore dead-end with only a tagId, which is a significant functional gap.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources