Add the Backblaze B2 MCP server to Gemini CLI

gemini mcp add -e B2_APPLICATION_KEY_ID=YOUR_VALUE -e B2_APPLICATION_KEY=YOUR_VALUE backblaze-b2 npx -y @backblaze-labs/b2-mcp

Scopes, env vars, OAuth and limits: Gemini CLI MCP config guide

Run /mcp auth <name> inside Gemini CLI to sign in to an OAuth server. Backblaze B2 runs locally and needs B2_APPLICATION_KEY_ID, B2_APPLICATION_KEY. Replace the placeholder values above with your own before starting Gemini CLI.

Ask Gemini CLI for something Backblaze B2 can do. Manage B2 buckets, files, application keys and Object Lock through the native B2 and S3 compatible APIs. Approve the first tool call and check the result before allowing write actions automatically.

• · In settings.json, streamable HTTP servers use httpUrl, SSE servers use url, local servers use command.
• · includeTools and excludeTools limit which tools the model sees.

How do I add the Backblaze B2 MCP server to Gemini CLI?

Run: gemini mcp add -e B2_APPLICATION_KEY_ID=YOUR_VALUE -e B2_APPLICATION_KEY=YOUR_VALUE backblaze-b2 npx -y @backblaze-labs/b2-mcp. Run /mcp auth <name> inside Gemini CLI to sign in to an OAuth server.

Is this the official Backblaze B2 MCP server?

Yes. It is published by Backblaze as io.github.backblaze-labs/b2-mcp in the official MCP registry.

Does the Backblaze B2 MCP server need an API key?

Yes. It runs locally and requires B2_APPLICATION_KEY_ID, B2_APPLICATION_KEY.