Integration

Wasabi integration

Wasabi Hot Cloud Storage API providing S3-compatible object storage with no egress fees. Store and retrieve unlimited data, manage buckets and objects, configure versioning and lifecycle policies, and enable multi-region replication. Perfect for backup, archive, media storage, and data lakes with predictable pricing and high performance.

Connect Wasabi How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Wasabi.Built from the 21 Wasabi tools below, on the connection you add once.

Common Wasabi use cases

compliance checks
storage cost management
renaming objects
emptying a bucket
browsing stored files
auto-deleting old logs
uploading backup files
removing obsolete files
retrieving stored files
auditing access policies

What you can do with Wasabi

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Object, 7 operations

copy_objectCopy objectPUTCopies an object within Wasabi, optionally across buckets or regions. Supports metadata modification during copy.
delete_objectDelete objectDELETEDeletes an object from Wasabi storage. Versioned buckets create delete markers; specify versionId for permanent deletion.
delete_objectsDelete objectsPOSTDeletes up to 1000 objects in a single Wasabi API call.
get_objectGet objectGETDownloads an object from Wasabi storage. Supports partial downloads, versioning, and conditional requests for efficient data transfer.
head_objectHead objectHEADRetrieves metadata headers for a Wasabi object without downloading content.
list_objects_v2List objects v2GETLists objects in a Wasabi bucket with pagination. Supports prefix filtering and delimiter for folder-like navigation.
put_objectPut objectPUTUploads an object to Wasabi storage. Supports encryption, custom metadata, tags, and integrity verification.

Bucket, 3 operations

create_bucketCreate bucketPUTCreates a new storage bucket in Wasabi. Configure region, Object Lock for compliance, and other bucket-level settings.
delete_bucketDelete bucketDELETEDeletes an empty bucket from Wasabi. The bucket must contain no objects or object versions before deletion.
list_bucketsList bucketsGETLists all buckets in the Wasabi account. Returns bucket names and creation timestamps for all storage containers owned by the user.

Multipart upload, 3 operations

abort_multipart_uploadAbort multipart uploadDELETEAborts a multipart upload and deletes all uploaded parts to avoid storage charges.
complete_multipart_uploadComplete multipart uploadPOSTAssembles uploaded parts into a final object and completes the multipart upload.
initiate_multipart_uploadInitiate multipart uploadPOSTInitiates a multipart upload and returns an UploadId for large object uploads.

Bucket policy, 2 operations

get_bucket_policyGet bucket policyGETReturns the bucket policy for a Wasabi bucket.
put_bucket_policyPut bucket policyPUTSets an IAM-style JSON bucket policy on a Wasabi bucket.

Cors, 2 operations

get_bucket_corsGet bucket corsGETReturns the CORS configuration for a Wasabi bucket.
put_bucket_corsPut bucket corsPUTConfigures CORS rules on a Wasabi bucket for browser-based cross-origin access.

Lifecycle, 2 operations

get_bucket_lifecycle_configurationGet bucket lifecycle configurationGETReturns the lifecycle rules configured on a Wasabi bucket.
put_bucket_lifecycle_configurationPut bucket lifecycle configurationPUTSets lifecycle rules on a Wasabi bucket to automatically expire or transition objects.

Versioning, 2 operations

get_bucket_versioningGet bucket versioningGETReturns the versioning state of a Wasabi bucket.
put_bucket_versioningPut bucket versioningPUTEnables or suspends versioning on a Wasabi bucket. Versioning preserves all object versions for protection and recovery.

Use Wasabi from Claude Code, Cursor or Codex

Connect Wasabi in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Wasabi operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Wasabi

Create your workspace
Sign up free. Nothing to install.
Connect Wasabi once
Add your Wasabi connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Wasabi integration FAQ

What can you do with the Wasabi integration?

LiveContext exposes 21 operations on Wasabi, covering object, bucket, multipart upload and bucket policy. Common uses include compliance checks, storage cost management and renaming objects.