Skip to content
Backblaze logo

Backblaze MCP server

Scalable storage in the cloud

Backblaze is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
2
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
August 2026

About the Backblaze MCP server

Connect Backblaze once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Backblaze and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Backblaze tools your AI can run

Once connected, your assistant can call any of these Backblaze actions by asking in plain language.

  • Upload File

    Upload an File to bucket.

    4 fields

  • Read File

    Read a file from Backblaze bucket to use it in other steps.

    1 field

Triggers

Backblaze events your agent can watch

These start a run the moment something happens in Backblaze, so work gets picked up on its own.

  • New File

    Trigger when a new file is uploaded.

    1 field

Give your assistant Backblaze

Connect Backblaze once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Backblaze MCP, answered.

No. That is the point of it. One Activepieces server exposes Backblaze alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Backblaze in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 2 tools, including Upload File, Read File, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.