Connect Claude

Before you start#

You need a Brella OS login at an agency — Owner, Manager or User. Brella OS is invitation-only, so if you do not have one, the person who set up your agency’s workspace can invite you. Brella’s own platform staff accounts and policyholder portal accounts cannot connect, and the consent page will say so rather than connecting you to nothing.

Claude on the web, desktop and mobile#

Add it once in Claude and it works in the desktop and mobile apps under the same account.

1. In Claude, open Settings → Connectors (Customize → Connectors on some plans) and choose Add custom connector.
2. Name it Brella OS and paste the address below.
3. Choose Add, then Connect. Brella OS opens in your browser for you to sign in.
4. On the consent page, pick your agency workspace and decide whether Claude may only read your book or also get work done. Choose Allow access, and you are back in Claude.

Claude Code#

One line adds the server. It is added but not yet authorised — the second step is what signs you in.

Then, in Claude Code, run /mcp, choose brella-os and sign in. Your browser opens Brella OS and hands you back to the terminal. If no tools appear, it is almost always this second step that has not been done.

The Brella OS plugin#

The plugin is the connector plus the broker workflows: twenty skills, four subagents, two commands and a set of guardrail hooks that make Claude Code ask before anything outward. It is for Claude Code and Cowork. Add the marketplace, then install:

Then run /mcp and sign in, or /brella-os:connect to be walked through it. What the plugin brings is set out in prompts, skills and subagents.

Plugin listing — coming soon. The commands above work today; the directory entry is still to come.

Other MCP clients#

Any MCP client that connects to a remote server over streamable HTTP and can run an OAuth 2.1 authorization code flow with PKCE. Point it at the same address. There is no client ID to ask us for:

• —A client that publishes a client ID metadata document uses its own URL as the client id, and we fetch it.
• —Anything else registers itself at /oauth/register (RFC 7591 dynamic client registration).

The details — discovery documents, redirect URI rules, what a loopback client needs — are on authentication.

Check that it worked#

In a new conversation, ask this. It reads one tool, changes nothing, and answers with your own name:

A good answer names you, your role, and the agency workspace this connection acts in. If it names a workspace you did not expect, connect again and pick the right one — a connection holds exactly one.

Team and Enterprise#

On Claude Team and Enterprise an Owner adds the connector once for the organization — Organization settings → Connectors → Add → Custom — and each member then chooses Connect beside Brella OS in their own Connectors. Adding it for the organization authorises nobody: every member still signs in as themselves and gets their own permissions.

Disconnecting#

In Brella OS, open Settings → Claude and revoke the connection. An agency Owner can revoke any connection into the workspace, not only their own. Revoking takes effect on the next request. Resetting your Brella OS password disconnects every connection you hold — see authentication.