Your workspace, native in Claude.
Workspace ships a Model Context Protocol server, so the AI tools you already use can work against your own CRM directly. Ask about your pipeline where you are already working, instead of switching tabs to go and look.
Free on every plan, including Workspace Free. Plus a public REST API and signed webhooks.
Connect it in one line.
Generate a workspace API key in Settings → Integrations, then point any MCP client at the endpoint. Streamable HTTP, stateless, no SDK to install.
claude mcp add --transport http brokeragent \
https://mcp.brokerandagent.com/mcp \
--header "Authorization: Bearer bak_your_workspace_key"Claude Desktop takes the same URL and header as a custom connector. When our OAuth 2.1 server ships, this becomes sign in and approve, with no key to copy or rotate.
Fifteen tools.
Generous on reading, deliberately narrow on writing. The in-app assistant does the heavy work; MCP is the open door, not a replacement for it.
Reading your workspace
get_workspace_info |
Which workspace the key belongs to, and what plan it is on. |
|---|---|
search_contacts |
Find people by name, email, phone or free text. |
get_contact |
One contact in full. |
get_contact_timeline |
Everything that has happened with a person, in order. |
get_pipeline_summary |
What is in the pipeline and what stage it sits at. |
list_tasks |
Open and completed tasks. |
list_appointments |
Showings, closings and meetings. |
get_todays_schedule |
The day, assembled. |
list_transactions |
Deals, milestones and close dates. Pro plans. |
list_automations |
The follow-up plans available to enrol someone in. |
Capturing into it
send_lead |
The Follow Up Boss-compatible arrival path. Routing, tagging and follow-up all run. |
|---|---|
add_note |
Log something onto a contact. |
create_task |
Add a to-do, with a due date and an owner. |
create_appointment |
Put a showing or a meeting on the calendar. |
enroll_in_automation |
Start someone on a follow-up plan. |
What it deliberately cannot do.
The absent tools are a design decision, not a backlog. An AI client working on your behalf should not be able to do things you would want to look at first.
Every tool calls the same public API your own session uses, with your key. Authentication, rate limits, visibility rules and plan gates apply identically, and there is no privileged path around them.
Why this matters more than another REST API
Plenty of real estate platforms have an API. An API is a promise that someone could build an integration, if they had the time and a reason. MCP is different in kind: the AI client reads what the tools do and picks the right one for what you asked. Nobody writes the integration, because there is nothing to write.
In practice that means you can be in the middle of drafting something, ask what is on today or who has gone quiet this month, and get an answer from your own records without leaving what you were doing. Then log the note or create the task from the same place.
The REST API and webhooks
Under the MCP server is a conventional public API covering identity, contacts, leads, tasks, appointments, pipeline, automations and transactions, with the status codes you would expect and a clear upgrade-required response where a plan gate applies. Webhooks deliver signed, retried events for new leads, stage changes, replies, completed tasks, new appointments and transaction status changes.
Lead intake accepts the same shape Follow Up Boss uses. That is deliberate: it means the lead sources already pointed at a Follow Up Boss account can be repointed at Workspace without being rebuilt, and everything downstream, the routing, the tagging and the follow-up, runs on arrival exactly as it would for any other lead.
Zapier, for everything else
Six instant triggers ride the outbound webhooks and six actions plus a contact search ride the API, which connects Workspace to several thousand other applications without anyone writing code. The integrations page lists what connects and what state each connection is in.
Common questions
What is the Broker & Agent MCP server?
It is a Model Context Protocol server that lets AI clients work directly against your Broker & Agent workspace. MCP is an open standard for connecting AI assistants to external systems. Point Claude Desktop, Claude Code or any other MCP client at https://mcp.brokerandagent.com/mcp with a workspace API key, and you can ask about your pipeline, search your contacts, check today's schedule, and capture leads and tasks from inside the tool you are already working in.
How do I connect Claude to my CRM?
Generate an API key in Settings → Integrations, then add the connector. In Claude Code that is a single command: claude mcp add --transport http brokeragent https://mcp.brokerandagent.com/mcp --header "Authorization: Bearer YOUR_KEY". In Claude Desktop, add it as a custom connector with the same URL and header. Any MCP client that speaks streamable HTTP works the same way. When our OAuth 2.1 server ships, connecting becomes sign in and approve, with no key to copy.
Is this safe? What can the AI actually do?
It runs as you, and never more than you. Every tool calls the same public API your own session uses, so authentication, rate limits, visibility rules and plan gates apply identically. There is no privileged path. The write tools are deliberately limited to light capture: notes, tasks, leads, appointments and automation enrolment. Sending messages to your clients, deleting records, moving deal stages, and anything touching settings, billing or your team are all deliberately absent.
Does it cost extra?
No. MCP and the public API are available on every plan, including Workspace Free. Pro-only surfaces such as transactions return a clear upgrade-required response on a free workspace rather than failing oddly, which is the same behaviour as the rest of the API.
Do you have a REST API and webhooks too?
Yes. The public REST API covers identity, contacts, leads, tasks, appointments, pipeline, automations and transactions, with conventional status codes. Webhooks deliver signed, retried events for lead.created, contact.stage_changed, contact.replied, task.completed, appointment.created and transaction.status_changed. Lead intake is Follow Up Boss-compatible on purpose, so sources already pointed at that shape can be repointed rather than rebuilt.
Do other real estate platforms have MCP servers?
We have not found another real estate CRM or platform shipping a native MCP server as of September 2026. Several have REST APIs, which is not the same thing: an API needs someone to write an integration, while MCP lets an AI client use the system directly, choosing the right call for what you asked. If that changes we will happily update this page.
Get early access.
Workspace opens soon and the MCP server comes with it, on every plan including the free one. Tell us what you would want to build.
Or email hello@brokerandagent.com.