Backblaze B2 MCP Server
OfficialRelated Servers
Alternatives to Backblaze B2 MCP Server
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for AWS S3 integration using FastMCP and boto3. This server provides access to S3 functionality through MCP-compatible tools.101MIT
- FlicenseAqualityDmaintenanceEnables file operations (upload, download, list, delete) on Cloudflare R2 (S3-compatible) storage, with dedicated APK upload tool.5-
Related Servers
- FlicenseAqualityCmaintenanceAn 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.91-
- FlicenseNot gradedqualityBmaintenanceEnables 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.1-
- AlicenseNot gradedqualityDmaintenanceMCP server for AWS S3 and compatible object stores, enabling LLM clients to browse buckets and fetch objects.MIT No Attribution
- FlicenseNot gradedqualityDmaintenanceA 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-
- AlicenseAqualityBmaintenanceAn MCP server exposing 72 tools across 26 homelab services, enabling LLMs to monitor and manage infrastructure, media, storage, and networking with a single endpoint.16MIT
- AlicenseNot gradedqualityAmaintenanceLightweight object storage with S3, HTTP, and MCP interfaces, enabling AI agents to store and retrieve files via structured tool definitions.4Do What The F*ck You Want To Public
TDQS
Scored across 40 tools
Most tools target distinct resource+action pairs, and descriptions clarify cases like small inline object I/O versus presigned URL transfers. There is some conceptual overlap between native b2_* and S3-compatible s3_* surfaces, especially around listing buckets, multipart uploads, and abandoned-upload analysis, but the tools remain mostly distinguishable.
Tool names use consistent snake_case with clear b2_* and s3_* prefixes, and most follow a predictable verb_noun pattern. Minor deviations such as b2_unfinished_uploads and b2_reserve_trial_create_account prevent a perfect score.
With 40 tools, the set is well above the typical 3-15 range and crosses the rubric's 25+ heavy threshold. The broad Backblaze B2 domain justifies many operations, but the combined native and S3-compatible surfaces make the count feel excessive.
Coverage is strong across buckets, objects, multipart uploads, keys, retention, legal holds, notifications, and usage analytics. Some lifecycle gaps remain, such as group creation/deletion and native hide/update-key operations, though several object gaps are covered through the S3-compatible tools.