Skip to main content
Glama
backblaze-labs

Backblaze B2 MCP Server

Official

Related Servers

Alternatives to Backblaze B2 MCP Server

  • A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol (MCP) server for AWS S3 integration using FastMCP and boto3. This server provides access to S3 functionality through MCP-compatible tools.
    10
    1
    MIT
  • F
    license
    A
    quality
    D
    maintenance
    Enables file operations (upload, download, list, delete) on Cloudflare R2 (S3-compatible) storage, with dedicated APK upload tool.
    5
    -

Related Servers

  • F
    license
    A
    quality
    C
    maintenance
    An MCP server that exposes Backblaze B2 Cloud Storage as tools any MCP-compatible AI client can call. Manage B2 by talking to an assistant -- list buckets, upload, download, delete versions, and check usage against a budget.
    9
    1
    -
  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP clients to manage Backblaze B2 Cloud Storage through native B2 and S3-compatible tools, including bucket operations, file upload/download, key management, and presigned URLs.
    -
  • 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
    A
    maintenance
    Lightweight object storage with S3, HTTP, and MCP interfaces, enabling AI agents to store and retrieve files via structured tool definitions.
    4
    Do What The F*ck You Want To Public

TDQS

A3.9/5.0

Scored across 40 tools

Disambiguation4/5

The b2_/s3_ prefix split plus verb_noun naming makes most tools clearly distinct. The main overlap risk is b2_unfinished_uploads vs s3_list_multipart_uploads, which both enumerate in-progress multipart uploads, and the three analytics tools (largest files, egress leaders, usage growth) sit close together, though their descriptions and cross-references draw clear boundaries.

Naming Consistency4/5

Nearly all 40 tools follow a consistent family_verb_noun pattern in snake_case, with b2_* marking the native API and s3_* the S3-compatible surface. The one outlier, b2_reserve_trial_create_account, awkwardly stacks two verbs, and the analytics tools use descriptive noun phrases, but these are minor deviations from an otherwise highly predictable scheme.

Tool Count2/5

40 tools is well above the 25+ threshold for a heavy surface, and the dual native/S3 API families double up on several operations (bucket checking, lifecycle, multipart listing). The breadth is partly defensible given two API surfaces plus partner management and analytics, but an agent must sift through a very large tool set to select correctly.

Completeness4/5

Bucket, object, key, multipart, notification, retention, legal-hold, and analytics workflows are all well covered with no dead ends. Minor gaps include no S3 get-bucket-lifecycle reader (mitigated by b2_list_buckets returning lifecycle rules), no group-creation/update tool in the Partner API, and file retention/legal-hold state only being readable via S3 metadata headers.

Maintenance

ActivityActive
ResponsivenessUnresponsive