Connect Claude
Copy the server URL from Brixit → User profile → AI connections. Read the connection overview before authorising access.
Add a custom connector
- In Claude, open Customize → Connectors. Some versions show this under Settings.
- Choose Add → Add custom connector.
- Name it Brixit — your company and enter the URL from your CRM.
- Review the detected OAuth settings. Choose Register automatically for the OAuth client and sign in when prompted. This uses Brixit’s dynamic client registration.
- Check that the sign-in page belongs to your company’s CRM domain. Sign in with your own Brixit account and approve read access. Select optional write access only if you want notes and follow-ups.
- Finish setup and enable Brixit from the conversation’s connector menu.
For a managed team, an authorised owner first adds the remote web connector in the organisation’s connector settings. Members then connect with their own Brixit accounts. Feature access and connector limits depend on the Claude account.
These steps follow Anthropic’s remote connector guide, checked on 14 October 2026. Claude’s cloud service must be able to reach your CRM endpoint; being able to open it on your own computer is not enough.
Verify it works
Ask:
Use Brixit to identify my connected account and company, then find one contact I can access. Make no changes.
Compare the result with your CRM. A read-only connection exposes ten tools; a connection with write access exposes twelve. If you enable write access later, reconnect and refresh the tools if Claude still shows the old list.
Keep Claude’s action approval prompts enabled and check the selected record before allowing a write. Try the reports and action examples once reading works.
If setup succeeds but chat does not
Account or billing restrictions in Claude can prevent a chat from running even after OAuth and tool discovery succeed. Resolve these through your Claude account; reconnecting Brixit does not change your subscription. For server errors, use the troubleshooting guide.