Claude MCP and Connectors for Real Estate: The Complete Guide

This is the deep dive on connections specifically. New to Claude overall? Start with our broader guide to using Claude for real estate, then come back here.

Here's what we'll cover:

• What MCP and connectors are and how they work under the hood
• The connectors worth setting up by role
• How to connect a tool, prebuilt or custom
• Reaching your MLS or CRM when there's no ready-made option
• Troubleshooting the issues you'll actually hit
• Staying safe and compliant with client data

One caveat before we start: connectors let Claude run your back office, but they can't capture the buyers already on your website.

A real estate chatbot does that, qualifying visitors around the clock so no lead slips away.

Let's get started.

The two terms get used interchangeably, but they're not the same thing.

MCP (Model Context Protocol) is an open standard for linking AI to outside tools.

A connector is a single one of those links: the connection between Claude and one specific app, like Gmail or your CRM.

You don't need to be technical to use connectors, but knowing the moving parts helps you troubleshoot and explain it to your team.

MCP runs on a simple client-server model with three roles.

• The host is the app you're using, in this case Claude.
• The client lives inside the host and speaks the MCP standard.
• The server sits on the other side, exposing one tool's data and actions, like your CRM or MLS.

When you ask Claude to pull a lead, the client sends the request to the server, the server fetches it from the underlying tool, and the answer flows back.

There are two kinds of server worth knowing.

• A remote MCP server runs in the cloud and connects over a URL, which is how nearly all directory connectors and vendor integrations work.
• A local MCP server runs on your own machine and is used mainly by developers working with files or software on that computer.

In 99% of cases you will be using a remote MCP server.

Once a tool is connected, Claude can read and act on your live data as part of a task, not just repeat what you paste in.

• Read: pull a lead's history from your CRM, open an email thread, or find a file in Drive.
• Act: draft a reply, update a record, add a calendar event, or create a document.
• Combine: use several connected tools in one task, like reading new inbox leads and logging them to your CRM.

Claude's directory has hundreds of prebuilt connectors. These are the ones that earn their place in an agent or brokerage workflow.

Start with the two or three you touch every day.

• Email
• Calendar
• Your CRM.

Your stack depends on how you work, so match it to your role rather than connecting everything at once.

Add each tool only when a specific workflow needs it. That keeps your setup simple and gives every connection a clear reason to exist.

Setting up a directory connector takes a couple of minutes and no code.

• Open Settings, then Connectors in the Claude desktop app, web app, or Cowork.

• Browse or search the directory for the app you want, like Gmail, Google Drive, Slack, or Notion.

• Click Connect and review the permissions. Claude will show you exactly what read and write access it's requesting.

• Complete the sign-in (OAuth) prompt for that app.
• Toggle the connector on in a conversation and start asking Claude to use it.

That's it. The tool stays connected for future chats until you turn it off.

Plenty of real estate software, your MLS, IDX provider, or a niche CRM, won't have a prebuilt connector. You have three routes.

Custom remote MCP connector. If your vendor offers an MCP server, add it directly:

• Open Settings, then Connectors, and click Add custom connector.
• Give it a name and paste the MCP server URL your vendor or developer provides.
• Configure any OAuth settings, click Add, and authenticate.

Build your own MCP server. For a proprietary system like your MLS feed or an in-house tool, a developer can wrap it in a small MCP server so Claude can reach it.

This is the most flexible route, and its a task that Claude Code can help you get started on.

Most teams live on prebuilt connectors and only build custom when they need to reach the MLS or a system unique to their business.

Reaching your MLS is the most common reason a real estate team goes custom, so it's worth knowing what's involved. A developer builds a small MCP server that wraps your MLS or IDX feed and exposes a few defined actions to Claude.

At a high level, the build covers four things:

• Access: credentials or an API key for your feed, commonly the RESO Web API standard.
• Actions: the specific things Claude can do, like search active listings or pull a property by address.
• Auth: an OAuth or token setup so only your account can use it.
• Hosting: a URL where the server runs so Claude can reach it.

Once it's live, you add it as a custom connector with that URL, and Claude queries listings the same way it reads your inbox. Expect a small, one-time developer project rather than an ongoing build.

Most connector problems trace back to a handful of causes, and each has a quick fix.

• Won't authenticate: sign out and reconnect, and confirm you're using the account that owns the data.
• Claude isn't using a connected tool: make sure it's toggled on in that conversation and name the tool directly in your prompt.
• Missing data or actions: check the permissions you granted, since read-only access can't write and some connectors expose only part of a tool.
• Custom connector fails: re-check the server URL and OAuth settings, and confirm the MCP server is actually running.

Connecting a tool gives Claude real access to real records, so treat it the way you'd treat handing someone a key.

• Connect only what you need. Don't wire up every tool at once. Add connectors as specific workflows call for them.
• Review permissions before you approve. Read-only is safer than read-write when that's all a task requires.

• Mind client PII. Be cautious feeding confidential financial or identity data into any AI, and check your brokerage's policy first.
• Turn off what you're not using. Removing a connector revokes that access cleanly.

Handled this way, connectors give you the upside, live data in your workflows, without the exposure.

When Claude can act on leads, compliance matters as much as security.

Anything a connector lets Claude write, like a follow-up email or a CRM note, falls under the same fair housing rules you follow yourself.

Two guardrails keep you safe:

• Don't let AI make protected-class decisions. Never prompt Claude to prioritize, screen, or filter leads by race, religion, familial status, or other protected characteristics.
• Keep a human in the loop for outreach. Review AI-drafted messages before they send, especially early on, so nothing goes out that you wouldn't have written yourself.

Connectors are the plumbing; the payoff comes when Claude uses them to finish real work, not just answer questions.

Once your email, calendar, and CRM are wired in, Claude Cowork can run a multi-step job that reads new leads, drafts the follow-ups, and logs everything back to the right record.

The first time you run a connected workflow you write it from scratch; the tenth time, you shouldn't have to.

When a task is repeated enough a Claude skill lets you package the whole routine, connectors included, so it runs the same way every time from one prompt.

This reduces the amount of copy and paste you will need to do.

Through its connector directory, Claude connects to hundreds of apps, including Gmail, Google Calendar, Drive, Slack, and Notion.

With a custom MCP connector or an automation bridge (such as Zapier), it can also reach real estate systems like Follow Up Boss, kvCore / BoldTrail, your MLS, or your IDX provider.

In short, MCP is the technology and a connector is the individual integration.

MCP is the open standard that connections run on, and a connector is a single link between Claude and one specific app built on that standard.

Most real estate CRMs, like Follow Up Boss or kvCore / BoldTrail, aren't in the prebuilt directory yet, so you'll connect them with a custom MCP connector using a URL from your vendor, or bridge them through an automation tool like Zapier.

If you run a general CRM that is in the directory, open Settings then Connectors, search for it, click Connect, and approve the sign-in.

Not with a prebuilt connector today. You can reach the MLS through a custom MCP server built for your feed, and connect Zillow or portal leads through an automation bridge like Zapier.

It's reasonably safe if you're deliberate about it: connect only what a task needs, review the read and write permissions before approving, avoid feeding sensitive client data without checking your brokerage's policy, and remove connectors you no longer use.

For most agents, the highest-value connectors are Gmail or Outlook, Google Calendar, and your CRM, since they cover lead response, scheduling, and pipeline. Brokerages usually add Drive, Slack, and a custom MLS connector on top.

The connectors are part of Claude, but you need a paid Claude plan to use them, and some third-party tools charge for their own MCP server or API access. Building a custom connector also carries a one-time development cost.

A remote MCP server runs in the cloud and connects over a URL, which is how nearly all directory and vendor connectors work. A local MCP server runs on your own computer and is mainly for developers working with files or software on that machine.

MCP is the standard and connectors are the individual links, and together they turn Claude into an assistant that works inside your real tools instead of alongside them. Start with email, calendar, and your CRM, add a custom connector when you need the MLS, and keep client data on a need-to-connect basis.

Ready to see AI put to work capturing the leads on your own website? Book a demo of Realty AI.