Skip to main content
Get data flowing through OneBucket — as S3, as MCP, or both.

Prerequisites

OneBucket is deployed per cluster, so your endpoints look like https://s3.<your-cluster>.onebucket.io. Copy the exact values from your console.

Use it as S3

OneBucket speaks the S3 API with AWS SigV4 auth, so any S3 client or SDK works — just change the endpoint.
# Credentials
aws configure set aws_access_key_id <ACCESS_KEY>
aws configure set aws_secret_access_key <SECRET_KEY>
export OB=https://s3.<your-cluster>.onebucket.io   # copy from your console

# Create a bucket, upload, list, and read back
aws --endpoint-url $OB s3 mb s3://my-first-bucket
echo "hello from onebucket" > hello.txt
aws --endpoint-url $OB s3 cp hello.txt s3://my-first-bucket/hello.txt
aws --endpoint-url $OB s3 ls s3://my-first-bucket/
aws --endpoint-url $OB s3 cp s3://my-first-bucket/hello.txt -
Because it’s standard S3, the same endpoint and keys work with SDKs in any language, s3cmd, rclone, and most S3-compatible tools.

Connect Claude

Prefer to work in natural language? Add OneBucket as an MCP connector and let Claude list, read, and manage your objects for you.

OneBucket Connector for Claude

Add your mcp-core.<your-cluster>.onebucket.io endpoint as a custom connector, sign in, and ask Claude to work with your buckets.

Manage keys and tokens (CLI)

The onebucket CLI handles authentication and tokens — your data operations go through the S3 client above.
onebucket login      # OAuth browser sign-in; exports ONEBUCKET_TOKEN
onebucket keys       # list your access keys
onebucket token      # mint an MCP JWT for a client
onebucket sessions   # list or revoke active sessions
onebucket logout     # clear the stored login

Next steps

  • Automate with AIconnect Claude for natural-language access to your storage.
  • Span backends — copy, migrate, and locate objects across clouds, on-prem, and edge from the same client.
  • Cut egress — prefetch hot objects into the edge cache so repeat reads are served locally.