OneBucket Connector for Muse

Connect Muse to your OneBucket account so Muse can list buckets and objects, read objects and, only with your approval, write or move data. The connection uses OAuth 2.1 with PKCE and Dynamic Client Registration: you do not create an application in advance, and you never paste a token or secret. Endpoints, sign-in details and the full tool list are on the shared MCP overview.

Before you start

A OneBucket account that can access at least one bucket. Request an account.
Access to Muse chat, where you can approve a connector connection.

Setting	Value
MCP endpoint	`https://data.onebucket.io`
Authorization server	`https://oauth.onebucket.io`
Scope	`mcp`
Resource	`https://data.onebucket.io`

Use the root URL exactly as shown. Do not use https://data.onebucket.io/mcp.

Connect Muse to OneBucket

Ask Muse to connect

In Muse, ask to connect to https://data.onebucket.io, then click Connect on the OneBucket connector card.

Continue past consent

On the consent screen, click Continue. If Muse asks for a Client ID, follow If Muse asks for a Client ID, then come back. If no Client ID field appears, carry on. Both behaviors are normal.

Wait for confirmation

Keep the window open until Muse confirms the connection.

If Muse asks for a Client ID

Sometimes the Add custom connector dialog asks for a Client ID instead of registering a client itself. Ask Muse to register one first:

Please register a client for me and give me the Client ID.

Muse registers a public client and returns a Client ID. Paste it into the Client ID field, click Add, and finish the sign-in steps above.

Do not invent a Client ID or copy one from a screenshot, another person’s setup or an old registration. Only a Client ID registered for Muse will complete the flow.

Register the client manually

If Muse cannot register the client, register a public client yourself, with no secret:

curl -X POST https://oauth.onebucket.io/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "Muse",
    "redirect_uris": ["https://agent.meta.ai/api/hatch/oauth/callback"],
    "grant_types": ["authorization_code", "refresh_token"],
    "response_types": ["code"],
    "token_endpoint_auth_method": "none",
    "scope": "mcp"
  }'

A successful registration returns HTTP 201 with a client_id. Paste only that value into the Client ID field, click Add, and finish the sign-in steps. Registering a client does not connect Muse by itself; the authorization and token exchange happen after you enter the Client ID and approve consent. Register a new client only if the Client ID you entered is rejected, and never a second one for a connection that already works.

Verify the connection

Ask Muse:

List buckets

Muse should return the buckets your account can reach, with the storage locations for each. After that you can list objects, read an object, check where an object is stored, or check recent events if you also connect the events endpoint.

Connect events

Storage events are a separate, read-only connection. Repeat the same flow with:

Setting	Value
MCP endpoint	`https://synapse.onebucket.io`
Resource	`https://synapse.onebucket.io`

The authorization server and scope are the same.

Troubleshooting

Problem	Fix
The connection fails, or Muse cannot reach the endpoint	Check the URL is exactly `https://data.onebucket.io`, with no `/mcp` and no trailing path, and start again.
Muse asks for a Client ID	Ask Muse to register the client, or register one manually. Enter only the `client_id` from the `201` response.
The Client ID is rejected	Register a new public client with the values above and enter the new `client_id`. Do not reuse one from an old or unrelated registration.
Authorization fails with a resource or audience error	The resource must be exactly `https://data.onebucket.io` (or `https://synapse.onebucket.io` for events). The client must request that exact value.
Muse asks for a token, secret or password	Stop. Do not paste credentials into chat or a connector dialog. The flow uses OAuth consent and Muse stores the credential itself.
A working connection now fails	Reconnect from Muse. If a Client ID field appears, try the Client ID from your working registration first, and register a new one only if it is rejected.

Disconnect

Disconnect Muse at any time in Muse Settings. This removes Muse’s access; it does not delete any bucket or object.

Support

Email support@attimis.co or call +1-650-382-3274; we typically respond the same business day.
Support and regions: onebucket.io/support
Live status: status.onebucket.io
Privacy policy: onebucket.io/privacy

Getting Started

Concepts

MCP

Guides

Scenarios

Reference

OneBucket Connector for Muse

Before you start

Connect Muse to OneBucket

If Muse asks for a Client ID

Register the client manually

Verify the connection

Connect events

Troubleshooting

Disconnect

Support

​Before you start

​Connect Muse to OneBucket

​If Muse asks for a Client ID

​Register the client manually

​Verify the connection

​Connect events

​Troubleshooting

​Disconnect

​Support

Before you start

Connect Muse to OneBucket

If Muse asks for a Client ID

Register the client manually

Verify the connection

Connect events

Troubleshooting

Disconnect

Support