Add the Backblaze B2 MCP server to Codex

# ~/.codex/config.toml
[mcp_servers.backblaze_b2]
command = "npx"
args = ["-y", "@backblaze-labs/b2-mcp"]

[mcp_servers.backblaze_b2.env]
B2_APPLICATION_KEY_ID = "<your B2_APPLICATION_KEY_ID>"
B2_APPLICATION_KEY = "<your B2_APPLICATION_KEY>"

Scopes, env vars, OAuth and limits: Codex MCP config guide

Run codex mcp login <name> to complete OAuth for a remote server. Backblaze B2 runs locally and needs B2_APPLICATION_KEY_ID, B2_APPLICATION_KEY. Replace the placeholder values above with your own before starting Codex.

Ask Codex 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.

• · Each server is a [mcp_servers.<name>] table in config.toml.
• · Use enabled_tools or disabled_tools to keep the tool list short.

How do I add the Backblaze B2 MCP server to Codex?

Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote 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.