MCP Protocol: The Technology Making Real Estate AI Actually Useful

What is MCP and why does it matter for real estate agents?

Most AI assistants are great at generating text but have no connection to the systems where real estate agents actually work. They can draft a follow-up email in the abstract, but they cannot look up the lead's last conversation, check whether a task already exists, or log the note into your CRM. That gap — between what AI knows and what your CRM contains — is the problem MCP solves.

Model Context Protocol (MCP) is an open standard, originally developed by Anthropic, that defines how AI models communicate with external tools. An MCP server exposes a list of named actions — "tools" — that the AI can invoke with structured arguments. The AI chooses the right tool for the job, calls it, and gets back real data from your live system.

For real estate agents, this matters in a concrete way:

• Before MCP: You copy a contact's name from Follow Up Boss, paste it into ChatGPT, ask for a follow-up, copy the reply back, and manually log the note.
• With MCP: You tell Claude "draft a follow-up for Maria Chen and log it as a note." Claude fetches Maria's record from Follow Up Boss, generates the message in context, and writes the note — without you ever leaving the chat.

The MCP standard means that same approach works with any MCP-compatible AI client: Claude Desktop, Claude.ai (web), ChatGPT with Connectors enabled, or any third-party tool that speaks MCP.

How does Follow Up Ace implement MCP for Follow Up Boss?

Follow Up Ace runs a dedicated MCP server that authenticates against your Follow Up Boss account and exposes its full feature set as named tools. The server speaks two transports: Streamable HTTP (the modern standard, endpoint /mcp) and SSE (endpoint /api/mcp/sse/, required by some ChatGPT Connector flows). Both are live at followupace.com.

The tool set is organized across 20+ functional categories:

The MCP server is compatible with Claude.ai (web), ChatGPT's Connector system, Claude Desktop, and any other MCP-compatible client. The CORS allowlist is locked to claude.ai, chatgpt.com, and chat.openai.com, so your FUB data only flows through authenticated, whitelisted channels.

How do you connect Follow Up Ace MCP to Claude or ChatGPT?

Setup takes under three minutes and requires no code. The connector uses OAuth 2.1, so your Follow Up Boss credentials never leave Follow Up Ace's servers.

Connecting to Claude.ai (web)

1. Open Claude.ai and go to Settings → Integrations.
2. Click Add integration and paste the connector URL: https://followupace.com/mcp
3. Claude will trigger the OAuth flow. Log in with your Follow Up Ace account.
4. Grant the requested CRM permissions and return to Claude. Your Follow Up Boss data is now live in the conversation.

Connecting to ChatGPT

1. In ChatGPT, go to Settings → Connectors → Advanced → Developer mode.
2. Enter the SSE endpoint: https://followupace.com/api/mcp/sse/
3. Complete the OAuth handshake when prompted.
4. ChatGPT will confirm with the connector label "FollowUpAce CRM." The search and fetch tools activate automatically, and the full tool set is available on request.

After setup, every new conversation with Claude or ChatGPT has access to your live CRM. No re-authentication is needed between sessions — the OAuth token refreshes automatically.

What can an agent actually do with MCP connected?

The day-to-day workflow changes significantly once CRM tools are available inside the AI conversation. Here are concrete examples grounded in the actual tool set:

• Morning triage in one call: Ask Claude to run run_morning_triage and it synthesizes your slip alerts, high-intent contacts, and revenue risks into a ranked action list for the day — without you opening FUB.
• Compliance-safe messaging: Before sending any message, Claude can invoke scan_message_for_compliance, which runs your draft through the Fair Housing and licensing guardrails built into Follow Up Ace's compliance engine. The tool returns violation count, severity, the matched phrase, and a suggested rewrite. See the compliance feature page for how this works.
• Speed-to-lead on Zillow leads: zillow_speed_to_lead_check evaluates a new lead against timing thresholds and drafts a first-touch response. The AI never auto-sends — it prepares everything for the agent to review and send. Details on the Zillow playbook.
• Pipeline health at a glance: The pipeline-health-check tool analyzes your active deals and flags stalls, missing follow-ups, and stage gaps without you clicking through the FUB pipeline board.
• Lead nurture sequencing: lead-nurture-optimizer reviews a contact's history and recommends the next touch — channel, timing, and message angle — based on their engagement pattern.
• Bulk stage scoring: bulk_grade_pipeline scores an entire pipeline segment in a single call, which would otherwise require opening each deal individually in FUB.

The agentic workflow layer built on top of MCP takes this further, letting you chain multiple tools into goal-oriented sequences — for example, "find all buyers who haven't been contacted in 14 days and draft a re-engagement message for each."

Which plan is required for MCP access?

MCP access requires an Ace Pro subscription. Pro is $55 per user per month. The Regular plan ($25 per user per month) covers the embedded FUB chat interface and most AI features, but MCP connector access — and the voice feature — are Pro-only.

Teams can mix plans: some agents on Regular for the embedded chat, others on Pro for MCP and voice. The admin dashboard manages both. For team-wide analytics and contact scoring, the Ace Trove add-on starts at $49 per month for accounts up to 5,000 contacts.

How is MCP different from a typical API integration or Zapier workflow?

API integrations and Zapier automations are powerful but rigid. You define a trigger and an action at setup time, and the workflow runs exactly as configured — no more, no less. If the situation changes (a lead replies unexpectedly, a deal stalls mid-sequence), the automation cannot adapt.

MCP-based AI is different in a meaningful way:

• Intent-driven, not trigger-driven. The AI interprets what you ask and selects the right combination of tools. One request — "what should I do with my pipeline today?" — might invoke four different tools in sequence.
• Context-aware. The AI can read a contact's full note history before drafting a message, then write the note back after sending. Static automations cannot reason about content.
• Auditable. Every tool call is visible in the conversation. You see exactly what the AI fetched and what it wrote to FUB before anything is committed.
• No auto-send guarantee. The Follow Up Ace MCP server never sends messages autonomously. Speed-to-lead tools draft for review; message tools prepare but require agent confirmation.

The practical result: MCP handles the judgment layer that Zapier cannot. Zapier reliably sends a task after a new lead arrives. MCP can decide which task to create, whether the lead's stage should change, whether the draft message is compliant, and what follow-up cadence matches the lead's engagement history.

Does the MCP connector work with Claude Desktop?

Yes. Claude Desktop supports MCP via a local configuration file. Follow Up Ace also ships a pre-packaged DXT (Desktop Extension) that sets up the MCP server configuration automatically — you install the extension file and authenticate, and no manual JSON editing is required.

Claude Desktop connects via the DXT extension, which uses the Streamable HTTP transport at https://followupace.com/mcp by default — no manual URL configuration needed when installing via the extension file. The tool set available through Claude Desktop is identical to the web connector surface — all 200+ tools, including the differentiator tools for AI intelligence, compliance, and speed-to-lead that go beyond basic CRM CRUD.

Is Follow Up Ace the only MCP integration for Follow Up Boss?

As of June 2026, Follow Up Ace is the only Follow Up Boss integration that implements MCP. Follow Up Boss itself does not expose an MCP server. Other FUB add-ons (ISA services, dialer integrations, market report tools) do not implement the protocol.

This matters because MCP is rapidly becoming the way that AI assistants connect to business software. Salesforce, HubSpot, Linear, and others are adding MCP servers to their platforms. Agents who learn to work with MCP-connected AI today are building a workflow advantage that will compound as AI assistants become more capable. See how Follow Up Ace compares with other AI approaches on the competitor comparison page.

What data stays in Follow Up Boss and what does the AI see?

The MCP server is a read/write bridge, not a data warehouse. When the AI calls a tool like fetch_person_by_id, it retrieves the contact's data from Follow Up Boss at that moment and returns it to the AI's context window for that conversation. Follow Up Ace does not maintain a separate copy of your FUB contacts.

Write operations — creating a note, editing a contact, creating a task — go directly to FUB via its API. The result: your FUB database remains the single source of truth. If you disconnect the MCP connector, everything the AI has done is in FUB, exactly as you'd expect from manual data entry.

Authentication uses JWT tokens issued by Follow Up Ace's server. Each token is scoped to one user's FUB account and expires on a short rotation. The CORS policy on the MCP server restricts origins to known AI client domains, blocking unauthorized cross-origin requests.

Common questions about MCP for real estate

Can the AI send emails or texts automatically through MCP?

No. The Follow Up Ace MCP server prepares and drafts communications but does not auto-send. The merge_email_template and merge_text_message_template tools populate a template with contact data and return the filled draft for the agent to review. Sending still requires a deliberate action in FUB or the agent's email client.

Does MCP require a Follow Up Boss API key?

Follow Up Ace handles the Follow Up Boss API connection. When you connect your FUB account to Follow Up Ace during signup, your FUB credentials are stored server-side. The MCP connector authenticates against Follow Up Ace (via OAuth), and Follow Up Ace proxies the CRM calls. You do not need to copy/paste FUB API keys into Claude or ChatGPT.

How many tools are actually available?

The connector exposes 200+ tools spanning contact management, notes, tasks, appointments, deals, email templates, SMS templates, action plans, automations, smart lists, team management, webhooks, and the AI intelligence layer (compliance scanning, pipeline health, lead scoring, speed-to-lead, and more). The full tool manifest is served at https://followupace.com/mcp and is readable by any MCP-compatible client during the tools/list handshake.

What if I already use the Follow Up Ace embedded chat in FUB?

The embedded chat (the AI panel inside Follow Up Boss's interface) and the MCP connector are separate surfaces that share the same underlying tools. The embedded chat is available on Regular and Pro plans. The MCP connector — which lets Claude or ChatGPT access FUB from outside the FUB interface — requires Pro. Upgrading to Pro adds MCP and voice to an existing Regular account without losing any embedded chat history or settings.