Creates a scoped B2 application key with least-privilege capabilities and routes its one-time secret through a configured secret sink. Use for issuing auditable, limited-duration credentials.
Replace the complete B2 event-notification webhook rule set for a bucket. Submit the full desired rule set after retrieving existing rules, as this operation overwrites all current rules.
Delete a single Backblaze B2 object via S3 API. Provide versionId to permanently remove a specific version; omit it to apply standard S3 delete semantics (may create a delete marker).
Create a new B2 bucket with optional CORS, lifecycle, encryption, and Object Lock settings. Use for initial provisioning; duplicate names are rejected.
MCP server for Backblaze B2 Cloud Storage: a focused, safe 40-tool surface (17 native B2 SDK, 19 S3 data-plane, 4 analytics) for any MCP-compatible AI client, currently incubating in Backblaze-Labs
Enables seamless integration with Backblaze B2 cloud storage for managing buckets, uploading/downloading files, handling large multipart uploads, and managing application keys through natural language interactions.
Permanently delete a B2 application key to revoke access immediately. Verify the key ID with b2_list_keys first; deletion is irreversible and anything using the key loses access.
Create a B2 Reserve trial account using the Partner API and return its application key. Requires a partner master key and confirmation for this irreversible action.
Finalize an S3-compatible multipart upload in B2 by assembling uploaded parts into a single object. Provide the ordered part manifest with ETags to complete the upload.
Generate short-lived presigned URLs for individual parts of an S3-compatible multipart upload, enabling clients to upload each part directly to Backblaze B2.
Copies a byte range from an existing B2 object into a part of an in-progress multipart upload, avoiding download and re-upload. Assembles large objects from data already in B2.
Generate a short-lived presigned URL to download or upload a single B2 object, with expiry control, so data flows directly between the client and B2 rather than through the MCP server.
Check whether a B2 bucket exists and is reachable on the S3-compatible endpoint with current credentials. Validates S3-surface access that native bucket listing doesn't confirm.