# Connect Claude

Add BLU to Claude as a custom connector on claude.ai, Claude Desktop or your Team workspace, or to Claude Code — then ask about your agency.

You need a BLU API key without an IP restriction — see [Get a key](https://docs.blu.luxe/mcp/#get-a-key) — and a Claude plan that allows custom connectors. On the Free plan you can add one custom connector; Pro and Max allow more; on Team and Enterprise an owner adds BLU for the whole organisation first.

**Claude (web and desktop)**

1. **Open Connectors**

   In Claude, open **Customize**, then **Connectors**. Click **+ Add**, then **Add custom connector**.

2. **Add BLU**

   *Picture: An illustration of Claude's Add custom connector dialog, with the name BLU and the server URL https://mcp.blu.luxe/mcp filled in.* — Adding BLU as a custom connector in Claude. Illustration — your screen may look slightly different.

   Name it **BLU** and paste the server URL (Claude asks for the remote MCP server URL):

   Server URL: `https://mcp.blu.luxe/mcp`

   Click **Continue**, and **Continue** again once Claude has checked the server: it then shows the sign-in settings it found. (On some accounts the dialog shows **Advanced settings** instead of **Continue**: leave them empty, click **Add**, then click **Connect** on BLU in your list of connectors.)

3. **Choose how Claude signs in**

   *Picture: An illustration of Claude's connector settings with Sign in now and Use Claude's published identity selected, and no request headers.* — Claude's sign-in settings for BLU. Each number matches a step below. Illustration — your screen may look slightly different.

   1. **Authentication:** choose **Sign in now**. BLU shows its tools only to an assistant that has signed in, so it needs the sign-in up front.
   2. **OAuth client:** keep **Use Claude's published identity (Recommended)**.
   3. **Request headers** (not every account has them): leave them empty. Never put your API key here — it belongs on BLU's sign-in page only.

   Click **Add**. BLU's sign-in page opens.

4. **Sign in on BLU's page**

   Paste your BLU API key and click **Continue**, check what Claude will be able to read, and click **Allow**. You are back in Claude, and BLU shows as connected.

Once added on the web or in Claude Desktop, BLU is available in the Claude mobile apps too.

**Team and Enterprise**

1. **An owner adds BLU**

   A Claude workspace **Owner** (on Enterprise, also anyone allowed to manage access to libraries) opens **Organization settings**, then **Connectors**, clicks **Add**, points to **Custom** and selects **Web**. They enter the name **BLU** and the server URL, click **Continue** (twice, if asked), choose **Sign in now** and **Use Claude's published identity**, leave **Request headers** empty and click **Add**. (In the older one-screen dialog: leave **Advanced settings** empty and click **Add**.)

   Server URL: `https://mcp.blu.luxe/mcp`

2. **Each member connects**

   Adding BLU signs nobody in. Each person who wants to use it opens **Customize**, then **Connectors**, finds BLU (marked **Custom**) and clicks **Connect**, then signs in on BLU's page with a BLU API key.

Every person signs in with a key, so each one only sees what their key allows. Only the agency owner can create keys: share one through your password manager's sharing feature, never in a chat or an email ([Keep a key safe](https://docs.blu.luxe/security/#keep-safe)). One key can serve several people — but revoking or rotating it disconnects all of them.

**Claude Code**

1. **Add the server**

   Run this in a terminal:

   ```bash
   claude mcp add --transport http blu https://mcp.blu.luxe/mcp
   ```

2. **Sign in**

   In Claude Code, run `/mcp`, choose **blu** and sign in — or run `claude mcp login blu`. Your browser opens BLU's sign-in page: paste your key, click **Continue**, check what Claude Code will be able to read and click **Allow**.

On your own computer you can skip the sign-in page and pass the key directly:

```bash
claude mcp add --transport http blu https://mcp.blu.luxe/mcp \
  --header "Authorization: Bearer <your key>"
```

The key is then stored in Claude Code's settings on this computer. Don't add `--scope project` to this command: that writes the key into the project's `.mcp.json`, a file that is usually shared with everyone who has the project.

More options are on [Developer tools](https://docs.blu.luxe/mcp/developer-tools/).

## Use BLU in a chat

1. Start a chat and click **+**, then **Connectors**, and switch **BLU** on.
2. Ask a question — try *"What can this connection see?"* first.
3. The first time Claude wants to use a BLU tool it may ask for your approval. Every BLU tool only reads, so **Allow always** is a safe choice for BLU's tools. To keep Claude from using a tool, switch it off in the chat's **Search and tools** menu.

For ideas, see [Example prompts](https://docs.blu.luxe/mcp/example-prompts/).

## Disconnect

Remove BLU under **Customize** → **Connectors** to disconnect Claude. Revoking or rotating the key in BLU disconnects every app that uses it.

If something doesn't work, start with [Troubleshooting](https://docs.blu.luxe/troubleshooting/).