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

# Connect Claude

> Connect Claude to your Allocait account by signing in through the connector

Add Allocait to Claude, sign in, and choose what Claude may do. There's no key to copy. To use an API key instead, see [Use an API key](https://docs.allocait.app/claude/connect-with-api-key.md).

Both ways reach the same MCP server and offer the same two levels of access: **Read only** or **Read and change**. Your plan decides which of the two you can choose. See [Access levels](https://docs.allocait.app/concepts/access-levels.md).

## Before you start

You need an account with an active plan or trial. What Claude may do depends on your plan and on the access you choose.

If you're new to Allocait, create your account and choose a plan first. Then start the connection from Claude. If the sign-in request has expired, start the connection again from Claude.

## Connect by signing in

### In Claude

If Allocait appears in Claude's connectors directory, you can add it from there and sign in. Otherwise add it as a custom connector.

**1. Add a custom connector**

Claude's menus change, so follow [Claude's guide to adding a connector](https://claude.com/docs/connectors/custom/add-unlisted) for the current steps. On a Team or Enterprise plan, an organization Owner may need to add the connector before members can connect.

**2. Enter the URL**

```text theme={null}
https://api.allocait.app/functions/v1/mcp
```

If Claude asks how it identifies itself to the server, choose **Register automatically**. Leave any client ID and secret blank.

**3. Sign in**

When Claude opens Allocait, sign in.

**4. Check the consent screen**

Check that **Signed in as** shows your account and that **Returns you to** names the app you started from.

**5. Choose access and allow**

Under **Access**, choose **Read only** or **Read and change**, then select **Allow**.

### In Claude Code

**1. Add the server**

```bash theme={null}
claude mcp add --transport http allocait https://api.allocait.app/functions/v1/mcp
```

**2. Sign in**

In a Claude Code session, run `/mcp` and follow the sign-in steps in your browser.

**3. Allow**

On the consent screen, choose the access, then select **Allow**.

The [Allocait plugin](https://docs.allocait.app/claude/install-plugin.md) adds this same server to Claude Code. After you install it, run `/mcp` and sign in. You don't need to add the server a second time.

### What you allow

The consent screen offers one choice:

* **Read only** is the default. Claude can see everything in your account, including portfolios, rules, watchlists, inputs and actions, and can call the read tools.
* **Read and change** lets Claude also add, change and delete your data, including whole portfolios. It needs a plan that includes it.

The screen starts at **Read only** every time it appears, even for an app you allowed changes before. See [Access levels](https://docs.allocait.app/concepts/access-levels.md) for the full comparison.

Allocait refuses some requests before it shows **Allow**, for example an app that asks for your sign-in details, which Allocait does not share with connected apps. See [Connector sign-in errors](https://docs.allocait.app/claude/errors/access-and-limits.md#connector-sign-in) for each message.

## Change or remove access

Open **Settings > Apps**. Your connected apps are listed there.

* To change what an app may do, select **Edit access**, choose **Read only** or **Read and change**, then select **Save access**.
* To remove an app, select **Remove**, then select **Remove** again to confirm.

Allocait applies a change from the app's next request. Your client may keep its earlier tool list until you start a new chat. Removing an app doesn't delete anything it already changed or created.

An app or key that hasn't been used for 30 days shows **Inactive**. The label doesn't change its access.

If Claude shows an authorization error after you remove the app, remove the Allocait connector in Claude and add it again.

## When your plan changes

* If you move from Advanced to Core, a key or app with **Read and change** keeps working, read-only. A write returns "This account's agent access is read-only." See [Read-only access](https://docs.allocait.app/claude/errors/access-and-limits.md#read-only-access).
* If your plan or trial lapses, the sign-in screen offers no **Allow**, and requests from an app already connected fail with HTTP `403` until you choose a plan. Reconnecting doesn't help. See [API errors](https://docs.allocait.app/api/errors.md) for the exact text.

## Next steps

> [card] [Access levels](https://docs.allocait.app/concepts/access-levels.md)
>
> What Read only and Read and change allow.

> [card] [Overview](https://docs.allocait.app/claude/overview.md)
>
> What the connector can and can't do.

> [card] [Read prompts](https://docs.allocait.app/claude/example-prompts.md)
>
> Realistic prompts and the tools they use.

> [card] [All tools](https://docs.allocait.app/claude/tools.md)
>
> Every MCP tool, grouped by feature.


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