AI connections (MCP)
Connect an AI assistant to your Brixit CRM to search contacts, review inquiries and listings, prepare reports, add notes and schedule follow-ups. MCP (Model Context Protocol) is the standard that lets the assistant use these Brixit tools.
Starting with Brixit 2.2.36, the assistant can also review a contact workspace, match properties to inquiries, create contacts and inquiries, and edit supported CRM records with separate management permission. Reports include explicit coverage and continuation instructions so the assistant can retrieve the detail pages it needs.
The connection runs inside your existing Brixit installation. You do not need to upload your database, share Brixit’s source code or build a separate service.
Find your personal connections
Click your avatar or name in the top-right corner of Brixit to open the User profile menu. Choose AI connections to open that tab in the profile settings dialog. You can also choose Profile settings and switch to the AI connections tab there.
Profile details and AI connections belong to your account. Company settings remain under Settings. Each person connects and manages their own AI apps.
Start with your own CRM address
- Sign in to your company’s Brixit installation.
- Open User profile → AI connections and copy the server URL.
- Follow the guide for ChatGPT, Claude or Gemini.
- Sign in on your CRM domain when prompted and review the access request.
- Ask the assistant to check your connected Brixit profile before using CRM data.
For example, a company running Brixit at https://crm.asdf.com connects with:
https://crm.asdf.com/api/mcp
Use the address shown by your installation. The demo address crm.brixit.io only connects to the demo CRM; it does not find or route to your company’s installation.
AI connections is included and enabled by default starting with Brixit 2.2.33. Install the release through your normal Brixit update process, then connect from your user profile menu. No server configuration or Brixit access to your server is needed. See Connection help if the option is missing.
How your data moves
Your AI provider connects directly to your CRM over HTTPS. Brixit does not run an MCP relay or a central store of customer connection credentials. Each customer can use its own domain and hosting provider, provided the AI service can reach the endpoint.
The CRM remains on your infrastructure. Records returned by a tool are shared with the connected AI provider so it can answer your request. That provider’s data handling and retention settings apply to those results. Follow your company’s policy before connecting.
Choose the access you need
| Access | What the assistant can do |
|---|---|
| Read only, the default | Read your permitted contacts, inquiries, listings, notes, follow-ups and reports |
| Read and write, optional | Also add notes and schedule follow-ups on permitted contacts or listings |
| CRM management, optional in 2.2.36 | Create contacts and inquiries, edit supported contact fields, move inquiries within their pipeline, and edit notes and follow-ups |
Every request uses the connected user’s company and CRM permissions. Connecting an administrator account can expose more records than connecting an agent account. Each team member should authorise their own account.
Upgrading Brixit does not expand an existing connection’s permissions. Disconnect and reconnect to request management access, then select it explicitly on the consent screen.
Write access does not give the assistant general control over the CRM. The current tools do not delete records, send email, run SQL or change arbitrary settings. Follow-ups may sync to a connected calendar. See Reports, actions and permissions.
Active accounts are required
Your Brixit account must be active, have login enabled and have completed its first login. Brixit checks account access on every MCP request, when refreshing a connection and when approving or completing a new connection.
If an administrator disables, deactivates or removes your account, existing AI connections cannot make further MCP requests, even if they connected before the account was disabled. They cannot refresh access or authorise a new connection while the account is disabled. This blocks future access; it does not erase data already returned to the AI provider.
Availability and costs
These guides describe custom connections to your installation. As of 14 October 2026, Brixit’s public directory listings are not published. A directory listing is separate from connecting your own endpoint, and a demo listing would not connect other customer domains.
AI app access depends on the provider’s account, region and workspace settings. Gemini has additional eligibility limits described in its guide. Compatibility checks are still in progress; successful sign-in or tool discovery alone does not prove every workflow works.
The Brixit MCP endpoint needs no model API key or separate AI server. Your existing Brixit hosting and licensing still apply, and the AI provider’s subscription or usage charges may apply. Check your provider account before enabling a paid feature; this guide does not require purchasing API credits.
Disconnect an assistant
Open User profile → AI connections, find the connection and select Disconnect to revoke its future access. You can also remove it in the AI app. Revoking access does not erase data already included in previous AI conversations. To change from write access to read only, disconnect and reconnect without selecting the optional write permission.