Skip to main content
Glama
ffumero2003

b2-mcp-server

by ffumero2003

Related Servers

Alternatives to b2-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP server for Backblaze B2 Cloud Storage: a focused, safe 40-tool surface (17 native B2 SDK, 19 S3 data-plane, 4 analytics) for any MCP-compatible AI client, currently incubating in Backblaze-Labs
      4
      40
      92 npm
      36
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      MCP server for the Rclone RC API. Gives AI assistants the ability to manage cloud storage remotes, copy/sync files, list directories, and more — all through natural language.
      56
      43 npm
      11
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AWS S3 and compatible object stores, enabling LLM clients to browse buckets and fetch objects.
      MIT No Attribution
    • 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
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables seamless integration with Backblaze B2 cloud storage for managing buckets, uploading/downloading files, handling large multipart uploads, and managing application keys through natural language interactions.
      14 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for the Rclone RC API that enables AI assistants to manage cloud storage remotes, copy/sync files, and list directories through natural language.
      12
      19 npm
      MIT

    TDQS

    A4.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: files (list/upload/download/hide/unhide/delete), buckets (list usage), and keys (list). The hide/delete pair is explicitly contrasted, preventing confusion. No two tools overlap in purpose.

    Naming Consistency4/5

    Almost all tools follow a consistent b2_verb_noun pattern (e.g., b2_list_files, b2_upload_file, b2_hide_file). The sole exception is b2_bucket_usage, which uses a noun phrase rather than a verb, but it remains clear and does not disrupt overall readability.

    Tool Count5/5

    Nine tools is well-scoped for a Backblaze B2 server. Each tool serves a distinct, necessary function, and there is no redundancy or bloat. The count feels appropriate for the domain.

    Completeness3/5

    The tool set covers file operations (list, upload, download, hide, delete) and includes bucket/key listing and usage, but misses bucket lifecycle (create/delete) and key management (create/delete). Hiding and unhiding work well, but no direct file metadata retrieval or bucket configuration exists. Core workflows are present, yet notable gaps remain.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive