> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onebucket.io/llms.txt
> Use this file to discover all available pages before exploring further.

# OneBucket Connector for Muse

> Connect Muse to OneBucket so it can list, read and, with your approval, write or move your data.

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](https://docs.onebucket.io/mcp/overview.md).

## Before you start

* A OneBucket account that can access at least one bucket. [Request an account](https://app.onebucket.io/sign-up).
* 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` |

> [!WARNING]
>
> Use the root URL exactly as shown. Do not use `https://data.onebucket.io/mcp`.

## Connect Muse to OneBucket

**1. Ask Muse to connect**

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

**2. Continue past consent**

On the consent screen, click **Continue**. If Muse asks for a **Client ID**, follow [If Muse asks for a Client ID](#if-muse-asks-for-a-client-id), then come back. If no Client ID field appears, carry on. Both behaviors are normal.

**3. Sign in**

Sign in at `oauth.onebucket.io` with your OneBucket account and approve access for scope `mcp`.

**4. 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:

```text theme={null}
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.

> [!WARNING]
>
> 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:

```bash theme={null}
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:

```text theme={null}
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](#register-the-client-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](mailto:support@attimis.co) or call +1-650-382-3274; we typically respond the same business day.
* Support and regions: [onebucket.io/support](https://www.onebucket.io/support)
* Live status: [status.onebucket.io](https://status.onebucket.io)
* Privacy policy: [onebucket.io/privacy](https://www.onebucket.io/privacy)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.