Connect the Follow Up Ace MCP Server to Claude

Updated July 24, 2026

Follow Up Ace publishes a remote MCP server — an implementation of the open Model Context Protocol that connects Claude directly to a real estate team's Follow Up Boss CRM, plus the Ace AI layer built on top of it (contact scoring, memory, revenue analytics, compliance scanning, and property/seller intelligence).

This page is the complete setup and administrator reference for the Claude integration. It covers connecting on claude.ai, Claude Desktop, and Claude Code; what the connector can do; and how authentication and permissions work.

What this connector is

Detail	Value
Connector name	Follow Up Ace (you can name it `Ace` when adding it)
Server URL	`https://followupace.com/mcp`
Transport	Remote / hosted (HTTP). Anthropic brokers the connection from its cloud — there is no local config file, no proxy, and nothing to install on a user's machine.
Authentication	Per-user sign-in with the user's Follow Up Boss email plus a 6-digit verification code emailed to that inbox. No API key, no shared secret, no developer setup.
Who can use it	Users with an active Ace Pro seat. The connector will not authorize a user without one.
Where the data lives	The connector reads and writes the team's own Follow Up Boss account. Follow Up Ace does not create a separate copy of the CRM for Claude to browse.

Follow Up Ace is an independent product. It is not built, operated, or endorsed by Follow Up Boss.

Before you start

Each person who wants to use the connector needs:

A Follow Up Boss login (the email address they sign into FUB with).
An active Ace Pro seat. The connector flow is a Pro capability — if a Pro seat is not assigned, the sign-in step will not complete. Team admins assign Pro seats from the Ace admin dashboard under Billing.
Access to that email inbox, to receive the one-time verification code.

Nothing else is required. There is no VPN, IP allowlist, firewall rule, or client-side install.

Connect on claude.ai (web)

This is the recommended path and takes under a minute.

Sign in to claude.ai on any device. Click your profile, open Settings, and choose the Connectors tab.
Click Add, then choose Add custom connector.
Enter a name — Ace works well — and paste the server URL into the URL field:
https://followupace.com/mcp
Leave the optional OAuth Client ID and Client Secret fields blank. Follow Up Ace handles sign-in itself; supplying values here is not required and is not expected. Click Add.
Claude opens the Follow Up Ace sign-in screen — "Claude wants to connect." Enter the same email address you use to log into Follow Up Boss and request a code.
A 6-digit verification code arrives in that inbox. Paste it back into the sign-in screen. Claude is now connected to your CRM.

Turning the connector on inside a conversation

Adding a connector makes it available; it is not forced on in every chat. In a conversation, open the + (tools) menu and enable Ace under Connectors. Claude will then use Follow Up Ace's tools when the request calls for them.

Team and Enterprise workspaces

On Claude Team and Enterprise plans, an Owner can add Follow Up Ace once for the whole workspace under Organization settings → Connectors. That publishes the connector to members — it does not grant anyone CRM access on its own. Each member still authenticates individually with their own Follow Up Boss email, and each member's access is scoped to their own FUB permissions. This is the recommended pattern for teams: one administrator approves and publishes the connector; access remains per user.

Connect in Claude Desktop

Claude Desktop uses the same remote connector as the web app. Open Settings → Connectors → Add custom connector, paste https://followupace.com/mcp, and complete the same email + verification-code sign-in described above. Because the server is remote, no local configuration file is edited and no dependency is installed on the desktop machine.

There is also an advanced local install for power users who prefer a desktop extension rather than the hosted connector — see Install Claude Desktop (advanced). For most teams, and for anything an IT administrator is standardizing on, the remote connector above is the right choice.

Connect in Claude Code

Add Follow Up Ace as an HTTP MCP server from the terminal:

claude mcp add --transport http follow-up-ace https://followupace.com/mcp

Then run /mcp inside Claude Code and complete the browser authentication prompt — your email address plus a 6-digit verification code. This second step is required: claude mcp add only registers the server, and until you authenticate it the server stays listed as Needs authentication and no code is ever sent. Once authenticated, the Follow Up Ace tools are available in your session.

Enter the address on your Ace seat — the address your Follow Up Boss admin assigned the seat to. The code is emailed to whichever address you type, and an address with no Ace seat behind it is answered with "Email not found in system" instead. If your seat address is a mail alias, type the alias, not the underlying mailbox: alias delivery lands the code in the same inbox.

What Claude can do once connected

The connector exposes 189 tools. The table below lists representative tools by category using their exact exposed names, so an administrator can see the actual shape of the surface — including which tools write and which only read.

Category	Representative tools	Access
Find & brief	`fetch_people`, `search_crm_globally`, `get_contact_360`	Read
CRM records	`create_task`, `create_note`, `create_appointment`, `create_deal`, `edit_person`	Write
Outreach	`merge_email_template`, `merge_text_message_template`	Read — renders the message body from a template; the agent copies it into Follow Up Boss and sends it themselves. Follow Up Boss does not permit programmatic send on this path, so there is no direct-send tool here.
Daily workflow	`run_morning_triage`, `daily_brief_get`, `get_now_view`	Read
Revenue analytics	`get_at_risk_deals`, `get_source_roi`, `get_pipeline_value_by_stage`, `get_conversion_funnel`	Read
AI scoring	`predict_close_probability`, `bulk_grade_pipeline`, `recommend_next_action`	Read
Compliance	`scan_message_for_compliance`	Read — checks a draft message before it is sent
Memory	`ace_memory_recall`, `record_contact_memory_fact`	Read and write, scoped to the signed-in user
Property & seller intent	`ace_lookup_property`, `ace_contact_seller_intent`	Read
Market data	`fetchMortgageRates`, `fetchHousingMarketData`	Read — public economic data, no CRM access
Lead response	`lead_speed_to_lead_check`, `lead_qualify`, `enroll_speed_to_lead`	Read, plus enrollment into a follow-up sequence
Team visibility	`get_team_cockpit`, `get_production_by_agent`, `get_response_time_per_agent`	Read — scoped to what the user's FUB role can already see
Knowledge	`search_knowledge_base`, `search_support_kb`	Read

Tool names shown here are the exact identifiers Claude sees. Market and economic data tools use camelCase (fetchMortgageRates); CRM and AI-layer tools use snake_case.

Examples of what a user would ask

"Find every Zillow lead I haven't called in three days, build a triage list, and schedule a call task for the top five."
"Show me my pipeline at risk this week with GCI estimates."
"Draft a follow-up to Sarah Carter referencing her last three emails."
"Run my morning triage."
"Scan this draft text for Fair Housing issues before I send it."
"Pull today's mortgage rates and draft an email to my fence-sitter clients."

Note for administrators: the connector includes tools that create records and send messages. Claude asks for confirmation before running a tool, and every action is performed as the signed-in user — so it lands in Follow Up Boss attributed to that person, and appears in the normal FUB activity history.

Security and permissions

Per-user OAuth. Every Pro user authenticates individually with their own Follow Up Boss email. There is no shared account, shared API key, or service credential that a whole team connects through.
Permissions inherit from Follow Up Boss. The connector operates within the user's existing FUB role — an admin's OAuth gets admin scope, an agent's OAuth gets agent scope. Connecting Claude does not widen anyone's access to CRM data beyond what they can already see when they log into Follow Up Boss directly.
Revocable tokens. Access tokens are JWTs and can be revoked at any time from the Ace dashboard. Revoking a token immediately ends that Claude connection.
No model training on customer data. Follow Up Ace does not train models on your CRM data.
PII handling. Personally identifiable information is tokenized before it reaches the model.
Seat-gated. Because the connector requires an active Ace Pro seat, removing or downgrading a seat also removes that user's ability to authorize the connector.

For the full data-handling statement, see the Follow Up Ace privacy policy.

Troubleshooting

The sign-in step won't complete, or you can't reach the Integrations page.
The connector requires an active Ace Pro seat. Confirm the Pro seat is assigned to that user and the subscription is active under Billing in the Ace admin dashboard.

The verification code hasn't arrived.
First, confirm a code was actually requested. In Claude Code, claude mcp add on its own never sends one — you have to run /mcp and complete the browser sign-in, and a server sitting at Needs authentication has not sent anything yet. If you did reach the sign-in screen, check the spam folder and confirm you entered the address on your Ace seat (if that address is a mail alias, type the alias — the code follows alias delivery into the same inbox). Codes expire after a few minutes — request a new one if the old one has aged out.

The connector shows as connected, but Claude isn't using the tools.
Connectors are enabled per conversation. Open the + (tools) menu in the conversation and switch Ace on under Connectors, then send your message again. It also helps to be explicit the first time — for example, "using Ace, find my hottest leads."

The connector is connected but no tools appear in the list.
Toggle the connector off and back on in the conversation's tools menu so Claude re-reads the tool list. In Claude Desktop, quit and reopen the app; in Claude Code, run /mcp to re-check the server's status and re-authenticate if prompted. If the list is still empty, the session's token may have been revoked — reconnect from Settings → Connectors.

"Server not reachable."
The Follow Up Ace MCP server is publicly hosted, so no VPN, allowlist, or firewall change is needed on your side. If the error persists, contact support so we can check the endpoint.

Connecting Ace to Claude, ChatGPT & Other AI Tools (MCP) — the same server in every other MCP client
Cheat Sheet: Ace MCP + Claude — prompts that work well once you're connected
Connect Ace to Claude in 60 seconds — the illustrated quick-start with screenshots
Install Claude Desktop (advanced) — the local desktop-extension option
The Follow Up Ace MCP server — product overview and the full tool surface
Privacy policy

Still have a question? Email [email protected].

Last updated: July 24, 2026

Was this article helpful?