AI agents (MCP)

Last updated: November 9, 2026

BucketWorx has a built-in MCP server, so an AI assistant can list, read and download from your buckets. It can only read unless you allow more.

bucketworx-cli mcp runs an MCP server, so an AI assistant can work with your buckets. Point your MCP client at it, for example:

{ "mcpServers": { "bucketworx": { "command": "bucketworx-cli", "args": ["mcp"] } } }

It is read-only by default. These tools are always on:

• list_accounts, list_buckets and list_objects (a page of up to 1,000 at a time).
• object_info (size, ETag, type, modified time, storage class, encryption) and object_url.
• download into an absolute local folder. Existing files are skipped unless you allow writes.
• transfer_status for a transfer or batch.
• bucket_cors, a bucket's CORS rules (from beta 4; it only reads them).
• bucket_policy, a bucket's policy and whether it makes the bucket public (from beta 4; it only reads it).
• bucket_lifecycle, a bucket's lifecycle rules and what each one does (from beta 4; it only reads them).
• bucket_website, a bucket's website settings and address (from beta 4; it only reads them).

Start it with --allow-writes and these are added: sync_plan (a preview that changes nothing), sync_apply, upload, copy, move, create_folder and create_bucket. Deleting needs --allow-delete as well. So does edit_tags (from beta 5), which adds or removes tags on objects or whole folders, because a lifecycle rule can delete files by their tags. remove_public_grant (from beta 5), which takes a public grant off a bucket's ACL, needs both as well. For Object Lock (from beta 5), object_lock reads a version's lock, set_object_lock (writes) turns a legal hold on or sets or lengthens retention, and release_object_lock (writes and delete) takes a hold off or shortens or removes retention. Every write tool needs Pro.