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

# Setup

> Connect Claude, Claude Code, ChatGPT, Cursor or another AI client to Redbark Advisor.

## Connect your client

**1. Copy the server URL**

Copy the address from **Settings > API and MCP** in Advisor, under **MCP server URL**:

```text theme={null}
https://advisor.redbark.com/api/mcp
```

**2. Add it to your AI client**

Follow the instructions for your client below. The client opens Advisor in your browser.

**3. Sign in and allow**

Sign in to Advisor as yourself. Choose the firm and the access, then click **Allow**. See [the consent page](#the-consent-page).

**4. Ask a question**

Try "Which clients haven't finished their checklist?"

## Client configuration

> [tab] Claude
>
> Custom connectors work in claude.ai, Claude Desktop and the Claude mobile apps.
>
> 1. Open **Customize > Connectors**.
> 2. Click **+ > Add custom connector**.
> 3. Name it `Redbark Advisor` and paste `https://advisor.redbark.com/api/mcp`.
> 4. Click **Add**, then **Connect** to sign in to Advisor.
>
> On a Team or Enterprise plan, an owner adds the connector for the organisation first. Each person then connects it as themselves.
>
> Leave the OAuth client ID and secret blank. Advisor registers Claude automatically. See [Anthropic's custom connectors guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

> [tab] Claude Code
>
> Run:
>
> ```bash theme={null}
> claude mcp add --transport http redbark-advisor https://advisor.redbark.com/api/mcp
> ```
>
> Then run `/mcp` in Claude Code and choose **redbark-advisor** to sign in.
>
> Or add it to your project's `.mcp.json`:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "redbark-advisor": {
>       "type": "http",
>       "url": "https://advisor.redbark.com/api/mcp"
>     }
>   }
> }
> ```
>
> Use the `http` type. The server does not support `sse`.

> [tab] ChatGPT
>
> Custom connectors need **Developer Mode** in ChatGPT. Which plans have it, and where the switch is, depends on your ChatGPT plan and workspace.
>
> 1. Turn on **Developer Mode** in ChatGPT's settings.
> 2. Create a new connector.
> 3. Name it `Redbark Advisor`, set the URL to `https://advisor.redbark.com/api/mcp` and set authentication to **OAuth**.
> 4. Confirm you trust the app, create it, then connect and sign in to Advisor.
>
> See [OpenAI's connector guide](https://developers.openai.com/apps-sdk/deploy/connect-chatgpt).

> [tab] Cursor
>
> Add this to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (one project):
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "redbark-advisor": {
>       "url": "https://advisor.redbark.com/api/mcp"
>     }
>   }
> }
> ```
>
> Cursor opens the Advisor sign-in the first time it connects. See [Cursor's MCP docs](https://cursor.com/docs/mcp).

> [tab] Other clients
>
> Any client that supports remote MCP servers over Streamable HTTP with OAuth can connect. Give it the server URL. It should find the sign-in details by itself.
>
> * Clients that run on your own computer and sign in through a `localhost` address work.
> * Hosted clients work only when Advisor knows their sign-in return address. Today that is Claude, ChatGPT, Cursor and VS Code.
> * If a hosted client is refused, contact [support](mailto:support@redbark.com) to have it added, or use an [API key](#use-an-api-key).

## The consent page

After you sign in, Advisor asks whether the app may act as you.

* **The app's name.** The app supplies its own name. Advisor shows it but has not checked it. The page also shows the site you will be sent back to.
* **Firm.** If you belong to one firm, it is shown. If you belong to several, choose one. The app is connected to that firm only.
* **Access.** Choose **Read only** or **Read and change**. Read only is the default. If the app asks for change access, **Read and change** is selected to start.
* **Allow** connects the app. **Cancel** sends you back to the app without connecting.

What you can do still follows your role. With **Read and change**, a member still cannot use tools only an admin can use. See [access and security](https://redbark.com/docs/advisor/mcp/security.md).

To change the access later, connect the app again and choose the new access. The new choice replaces the old one.

## Use an API key

An admin can make an API key in **Settings > API and MCP** for tools that cannot sign in with OAuth. The MCP server accepts the key as a bearer token:

```text theme={null}
Authorization: Bearer rbk_org_live_...
```

For example, in Claude Code:

```bash theme={null}
claude mcp add --transport http redbark-advisor https://advisor.redbark.com/api/mcp \
  --header "Authorization: Bearer rbk_org_live_..."
```

* A key acts as the admin who made it, so admin-only tools are available.
* A key's access is set when it is made: All, Read only, or Restricted to chosen areas.
* Advisor shows the key once. Store it in a password manager.
* Treat a key like a password. Anyone with it can act as that admin within its access.

Prefer OAuth when the client supports it. Each person then acts as themselves. See [authentication](https://redbark.com/docs/advisor/api-reference/authentication.md) for more on keys.

## Technical details

* The server uses Streamable HTTP and is stateless. Send JSON-RPC messages with `POST`. `GET` answers 405.
* A request may hold one message or a batch of up to 10.
* A request body may be up to 64 KB.
* The OAuth sign-in uses dynamic client registration and PKCE. Clients find the details at `https://advisor.redbark.com/.well-known/oauth-protected-resource/api/mcp`.

If connecting fails, see [troubleshooting](https://redbark.com/docs/advisor/mcp/troubleshooting.md).


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