Add the Backblaze B2 MCP server to Cursor

{
  "mcpServers": {
    "backblaze-b2": {
      "command": "npx",
      "args": [
        "-y",
        "@backblaze-labs/b2-mcp"
      ],
      "env": {
        "B2_APPLICATION_KEY_ID": "<your B2_APPLICATION_KEY_ID>",
        "B2_APPLICATION_KEY": "<your B2_APPLICATION_KEY>"
      }
    }
  }
}

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

Cursor prompts you to sign in the first time a remote OAuth server is used. Backblaze B2 runs locally and needs B2_APPLICATION_KEY_ID, B2_APPLICATION_KEY. Replace the placeholder values above with your own before starting Cursor.

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

• · Remote servers take a url; local servers take command and args.
• · Values can reference ${env:NAME} so secrets stay out of the file.

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

Run: { …. Cursor prompts you to sign in the first time a remote OAuth server is used.

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.