← Index

Backblaze B2 MCP Server

io.github.backblaze-labs/b2-mcpv0.2.0AWS

Operate Backblaze B2 buckets, files, keys, Object Lock, and S3-compatible storage.

The current version, v0.2.0, was published to the official MCP registry on 2026-09-01. It is distributed as @backblaze-labs/b2-mcp on npm, filed under AWS by this index, and declares 5 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Backblaze B2 MCP Server in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-02).

Contracts can change after screening, with no version bump. The gate pins Backblaze B2 MCP Server’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
B2_APPLICATION_KEY_ID
requiredsecret

Backblaze B2 application key ID for native B2 and S3-compatible tools.

B2_APPLICATION_KEY
requiredsecret

Backblaze B2 application key secret.

B2_REGION

Optional fallback S3-compatible region used before authorization.

B2_MASTER_KEY_ID
secret

Optional master key ID for Partner/Groups API tools.

B2_MASTER_KEY
secret

Optional master key secret for Partner/Groups API tools.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in AWS