Skip to main content
The OneBucket connector is a Model Context Protocol (MCP) server that lets Claude browse, read, and manage the objects in your buckets — and query your OneBucket activity — using your own credentials, with your explicit consent.

​
What you can do

Ask Claude things like:
  • “List my buckets, then show what’s in reports/ in the analytics bucket.”
  • “Download notes/meeting.md from team-docs and summarize it.”
  • “Upload this text as drafts/summary.md in team-docs.”
  • “Copy logo.png to archive/logo.png, then delete the original.”
  • “Give me a presigned download link for builds/app.zip.”
  • “What happened in my OneBucket in the last 24 hours?”

​
Tools

Read tools run without per-call confirmation. Write tools prompt for confirmation before running.

​
Reading

​
Writing

​
Events

Served by a separate events endpoint (see Connect):

​
Requirements

The global MCP hostnames below work for every account — geoproximity DNS routes you to the nearest cluster. To pin a specific cluster, use the per-cluster forms from your OneBucket console, e.g. core.<cluster>.onebucket.io.

​
Connect it to Claude

1

Add the connector

In Claude, go to Settings → Connectors → Add custom connector (or find “OneBucket” in the directory once listed).
2

Enter the server URL

Provide the OneBucket core MCP URL — https://core.onebucket.io. To also query events, add the events endpoint https://synapse.onebucket.io as a second connector.
3

Sign in

Claude discovers the authorization server automatically (RFC 9728 / RFC 8414) and opens the OneBucket sign-in page. Sign in and approve the requested access — Claude completes an OAuth 2.1 authorization-code flow with PKCE, and your secret key never leaves OneBucket.
4

Try it

Ask: “List my OneBucket buckets.”

​
How authentication works

The connector uses standard MCP OAuth: Claude discovers the OneBucket authorization server automatically and signs you in with OAuth 2.1 + PKCE — your secret key never leaves OneBucket. Every tool call is scoped to your organization and access key, and you can revoke access at any time from your OneBucket console.

​
Limits & behavior

Inline reads/writes are capped at 700 KB; larger transfers use presigned URLs (valid ~1 hour) so big files bypass the model.
  • copy, move, migrate, and prefetch are asynchronous — they return once queued, so a destination may not be readable immediately.
  • Small PDFs/binaries (≤10 KB) are returned inline as blobs; larger ones return a presigned URL.

​
Support