Getting started
Brella OS documentation
How Claude works inside a Brella agency workspace: what the connector is, what it may do, what it asks you before doing, and every tool it can call. Written for the person who has to decide whether to switch it on.
The connector, in one paragraph#
Brella OS is the software an insurance agency runs its book on. The connector is a remote MCP server at www.brellapartners.com/mcp that lets Claude work in that book — not by reading a copy of it, but by calling the workspace’s own handlers, the same ones its screens call, with the same authorisation.
You connect with your own Brella OS login and pick one agency workspace. Claude then acts as you: an Owner or Manager reaches the agency’s book, a User only the policies assigned to them, re-checked on every single request. Of the 102 tools it can call, 30 only look and change nothing, 38 change the agency’s own record, and 34 — anything a policyholder would see, anything a certificate will assert, anything that cannot be undone — stop and ask you first. Every change lands on the policy’s activity log as your name, via Claude.
What is documented here#
- The Claude connector — the address, the transport, what it exposes, and how a call is authorised.
- Connect Claude — setup for Claude on the web, desktop and mobile, for Claude Code, for the plugin, and for any other MCP client.
- Permissions and approval — the two scopes, the three kinds of tool, everything that asks first, and how a role scopes it.
- Tool reference — all 102 of them, grouped the way the workspace is.
- Attribution and the activity log — how work done through Claude is recorded.
- Authentication — OAuth 2.1, PKCE, scopes, token lifetimes, revocation.
- Data handling — what reaches Claude, what Brella keeps, and what it never stores.
- Prompts, skills and subagents and troubleshooting.
What you need#
- A Brella OS login at an agency — Owner, Manager or User. Brella OS is invitation-only: an agency is provisioned with its Owner, who invites everyone else. Brella’s own platform staff and policyholder portal accounts cannot connect.
- Claude, or another MCP client. Claude on the web, desktop and mobile through a custom connector; Claude Code with one command; anything else that speaks MCP over streamable HTTP with OAuth.
- Nothing installed. There is no extension, no agent on your machine and no export of your book.
What it will not do#
It records what people at the agency do. It does not bind coverage: marking a policy “bound” in Brella OS is a record, not a binder. It does not move money. And there is no carrier transport anywhere in Brella — a change request marked submitted records that a human sent it somewhere else, on the date they say they sent it.
The rule the whole product is built on
Claude drafts and does the legwork; a person at the agency reviews and sends. Nothing reaches a policyholder, a carrier or a regulator without somebody tapping.
What is documented elsewhere#
- Brella OS for Claude — the short version: what it is for, and what a morning with it looks like.
- Privacy policy, “Connecting Claude to Brella OS” — the binding statement of what is kept and for how long.
- System status — live availability of every service behind these pages.
These pages describe what the connector does today. Where something is not built, they say so rather than leaving you to find out.