An open-source Node.js MCP server that connects any AI assistant to Follow Up Boss, the most widely used CRM in real estate. 160 tool definitions mapping the complete FUB REST API — contacts, deals, tasks, emails, SMS, automations, pipelines, webhooks, and everything in between.

Instead of clicking through CRM screens, you talk to your AI: “Add a note to Sarah’s file that she’s interested in Lake Travis properties and move her deal to Under Contract.” Done. One sentence replaces five minutes of point-and-click.

What it does

The server maps the full Follow Up Boss API surface to MCP tool definitions:

Contacts — create, search, update, merge, tag, enrich, manage relationships, check for duplicates, bulk update. The search supports filtering by tag, stage, source, assigned agent, date range, and custom fields.

Deals and Pipelines — create deals, move them through custom pipeline stages, track values, attach documents, assign team members. Pipeline stage progression triggers are exposed so the AI can automate deal workflows.

Communication — send emails and SMS through FUB’s delivery infrastructure, log calls with duration and outcome tracking, manage email and text templates with merge-field support, view full conversation history threaded by contact.

Tasks — create, assign, prioritize, and track completion across your team. Due dates, reminders, and task types all exposed as tool parameters.

Automations — trigger action plans, add contacts to automation sequences, manage smart lists, configure drip campaign enrollment. The AI can see which automations a contact is in and modify their enrollment.

Teams and Users — handle lead assignments, round robin distribution, pond management, team inboxes, and user permission scoping.

If FUB has an API endpoint for it, this MCP server exposes it. No exceptions, no partial coverage.

How it’s built

Building 160 tool definitions sounds like grunt work, but it’s actually an exercise in API translation design. Each FUB endpoint needs to be mapped to an MCP tool with a precise JSON Schema for parameters, sensible defaults for optional fields, and descriptions clear enough that an AI assistant chooses the right tool in context without being told which one to use.

The tool description engineering is the non-obvious challenge. “Create a person” vs “update a person” vs “merge two people” vs “check for duplicate” — the AI needs to understand the semantic distinction between these operations and select correctly based on conversational context. Getting that right required iterating on descriptions with real-world usage: I’d say something to Claude, watch which tool it picked, and refine the description until the selection was consistently correct. That’s prompt engineering applied to tool design, and it’s where most MCP servers fail — they expose the API but don’t make it usable.

Authentication is handled securely during setup, with automatic token refresh. The server provides a clean setup experience: copy .env.example, add your FUB API key, and you’re running.

This isn’t a side project — it powers the daily CRM operations at Neuhaus Realty Group. Every contact update, deal progression, task assignment, and follow-up email flows through this server. I manage my entire brokerage’s CRM through natural language, and the tool definitions have been hardened against 18 months of real production use.

Install

git clone https://github.com/mindwear-capitian/followupboss-mcp-server.git
cd followupboss-mcp-server
cp .env.example .env
# Add your FUB API key to .env
npm install && npm start

Works with Claude Code, Claude Desktop, Cursor, or any MCP-compatible client.

Why I built it

I use Follow Up Boss every day. It’s a great CRM, but I was spending too much time clicking through screens to do things that should take seconds. Add a note. Move a deal. Tag a contact. Send a follow-up. Each one is three clicks and a page load. Multiply that by fifty contacts a day and you’re losing an hour to UI friction.

I wanted to collapse the distance between thinking “I should update Sarah’s file” and it being done. Now I say it to Claude and it happens. That workflow change — from clicking to speaking — sounds small but it compounds. Over a day of real estate work, it saves an hour. Over a year, it changes how you operate.

The open-source decision was easy: every real estate agent using FUB has the same friction. The Local Austin MCP gives agents data tools; this one gives them CRM superpowers. Together they cover the two systems an agent lives in all day.

License

Elastic License v2 (ELv2)