fub-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@fub-mcp who's in my Hot Leads smart list?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
fub-mcp
A comprehensive Model Context Protocol server for the Follow Up Boss real estate CRM API. Not affiliated with or endorsed by Follow Up Boss.
Generates one MCP tool per FUB API operation (~130+ tools) directly from FUB's published OpenAPI spec, plus a small set of hand-written extras for behavior that's real but undocumented. Runs entirely on your machine — your API key never leaves it.
Install
Claude Desktop (recommended — no Terminal, no Node.js)
Download
fub-mcp.mcpb(it lands in your Downloads folder).Install it from inside Claude Desktop: open Settings → Extensions → Advanced settings → Install Extension… and choose the downloaded file. (Dragging the file onto the Claude Desktop window also works. On macOS, double-clicking works too, but on Windows double-clicking does not — Claude Desktop doesn't register the file type, so Windows offers Notepad instead. Cancel that prompt and use the in-app route.)
Paste your Follow Up Boss API key into the masked field (FUB → Admin → API), then click Install. Claude Desktop stores the key in your system keychain (macOS Keychain / Windows Credential Manager); it is never typed into a chat and never sent anywhere except directly to Follow Up Boss.
Turn it on. Installing does not enable it: go to Settings → Extensions, find Follow Up Boss, and switch the toggle on.
Start a new chat and try "List my 3 most recently added contacts."
Claude Desktop ships its own Node.js runtime, so nothing else needs installing. Notes:
the bundle isn't code-signed yet, so Claude Desktop may show an unverified-developer
caution. It is pure JavaScript (no native binaries) and has been tested end to end on
both macOS and Windows. To update, download the newest .mcpb and install it over
the old one.
Claude Code, other MCP clients, or Terminal users
claude mcp add fub-mcp --env FUB_API_KEY=your-key -- npx -y fub-mcpor add this to your MCP client's config (e.g. claude_desktop_config.json):
{
"mcpServers": {
"fub-mcp": {
"command": "npx",
"args": ["-y", "fub-mcp"],
"env": {
"FUB_API_KEY": "your-fub-api-key"
}
}
}
}Requires Node.js 18+. Get your API key from Follow Up Boss: Admin → API.
Optional: macOS-only key-entry popup
If you'd rather not put your key in a config file, macOS users can run
npx -y fub-mcp setup: a native masked dialog collects the key, validates it against
the live API, saves it to ~/.fub-mcp/.env (readable only by your user), and adds a
secret-free entry to Claude Desktop's config. Claude Desktop users should prefer the
extension above, which needs no Terminal and stores the key in the OS keychain. This
popup is not available on Windows or Linux (use the extension, or the commands above).
Recommended for heavy use: register your own FUB system
Follow Up Boss asks API users to register their system, and registered systems get a
higher request rate (FUB's API states this in its responses). By default this tool
identifies itself as an unregistered fub-mcp. FUB's terms also say a system key is
private and must not be shared, so a shared one can't ship with this project: each
customer registers their own.
Register at https://apps.followupboss.com/system-registration (system name, a "System ID Header" of your choosing such as
acme-realty-claude, your name, email, and organization). Read the terms linked on that page.FUB provides your X-System-Key after you register.
In Claude Desktop, open Settings → Extensions → Follow Up Boss and fill in the two optional fields: your registered system ID (the System ID Header) and your system key. Restart Claude Desktop. (Other clients: set
FUB_MCP_SYSTEM_NAMEandFUB_MCP_SYSTEM_KEY.)
Keep the system key private, like your API key. Paste it only into that masked field. Never put it in a chat, email, screenshot, or plain-text file; if you need a copy, use a password manager. The setup instructions tell Claude never to ask for it. If a key ever lands somewhere it shouldn't, email api@followupboss.com and ask for a replacement.
Optional environment variables
Variable | Default | Purpose |
|
| Sent as |
| unset | Only needed if you've separately registered your own system. |
|
| Set to |
Related MCP server: Follow Up Boss MCP Server
Delete safety
Follow Up Boss DELETE calls are permanent. This server treats them as opt-in at two layers:
Server-level opt-in: unless
FUB_MCP_ALLOW_DELETE=1is set in the server's environment, delete tools aren't registered at all — the model never sees them as callable.Per-call confirmation: even with that flag set, every delete tool requires a
confirm: trueargument, and its description instructs the model to get explicit, specific confirmation from the user before calling it — not to infer consent from general intent.
Neither layer trusts the model alone; both must be satisfied.
What's generated vs. hand-written
Most tools (list_people, create_note, update_deal, ...) are generated at build
time straight from FUB's OpenAPI spec (vendored in src/openapi/fub-openapi.json —
refresh it from https://docs.followupboss.com/openapi to pick up FUB API changes).
A few things needed hand-written overrides in src/overrides/:
list_notes— FUB's docs only documentGET /notes/{id}, but the pluralGET /notesendpoint works today and supports apersonIdfilter. Confirmed against the live API; treated as best-effort since it's unofficial.update_persontag handling — adding tags should passmergeTags=true(defaulted for you); removing a tag has no dedicated endpoint and requires a fetch → filter → PUT-the-whole-array-back pattern (documented in the tool description).Notes vs. templates HTML handling — notes need
isHtml: trueset explicitly for HTML bodies; email templates take raw HTML directly with no such flag. These are easy to mix up, so both tools' descriptions call it out.Two spec quirks fixed transparently by the generator: a couple of endpoints use
:idinstead of{id}for path params, and the rate-limit endpoints' documented paths double up the/v1prefix that's already in the base URL.
Skills
Three Claude Skills ship alongside the server for common multi-step workflows the tools alone don't capture:
query-smart-list— resolve a Smart List by name (not just ID) before filtering people by it.create-html-email-template— build and upload an HTML email template correctly (see the HTML-handling gotcha above), including FUB's%merge_field%syntax.create-text-template— build an SMS template with the same merge fields, plus FUB's own texting-compliance guidance (opt-out language, carrier-filtering avoidance).
Using this outside Claude
ChatGPT Custom GPT: see
gpt/for a trimmed, ≤30-operation OpenAPI schema and setup instructions — each person builds their own GPT with their own API key, no shared/hosted backend involved.Claude web or mobile without the desktop app: not currently supported. Claude.ai's custom-connector UI only supports OAuth (or an org-admin-only static header beta) for remote connectors, so there's no individual, bring-your-own-key path there today the way there is for a Custom GPT. Reaching pure web/mobile users would require a hosted, multi-tenant OAuth backend — out of scope for this repo for now.
Development
npm install
npm run build
npm run inspect # opens the MCP Inspector against the built serversrc/openapi/generate-tools.ts does the spec → tool-schema conversion;
src/overrides/index.ts is where undocumented endpoints, description corrections,
and default overrides live. src/tools.ts merges the two and applies delete-gating.
License
MIT
Available Tools
133 toolscreate_action_plans_personA
Apply an Action Plan to a person. (POST /actionPlansPeople) ⚠️ Action Plans are a deprecated FUB feature — Automations are the current, recommended mechanism going forward. Unless the user specifically names an existing legacy Action Plan they already rely on, prefer the automationsPerson tools (create_automations_person to trigger one, update_automations_person to pause/unpause) over this one for new workflows.
Inputs: personId (required), actionPlanId (required), extraBody, extraQuery.
create_appointmentC
Create an appointment. (POST /appointments)
Inputs: end (required), start (required), title (required), allDay, +9 more.
create_appointment_outcomeC
Create an appointment outcome. (POST /appointmentOutcomes)
Inputs: name, extraBody, extraQuery, orderWeight.
create_appointment_typeC
Create an appointment type. (POST /appointmentTypes)
Inputs: name, extraBody, extraQuery, orderWeight.
create_automations_personB
Manually trigger an Automation for a specified Person. (POST /automationsPeople)
Inputs: personId, extraBody, extraQuery, automationId.
create_callC
Add a call. (POST /calls)
Inputs: phone (required), personId (required), isIncoming (required), note, +8 more.
create_custom_fieldC
Create a custom field. (POST /customFields)
Inputs: type (required), label (required), choices, extraBody, +4 more.
create_dealC
Add a deal. (POST /deals)
Inputs: name (required), stageId (required), price, userIds, +14 more.
create_deal_attachmentB
Add an attachment to a deal. (POST /dealAttachments)
Inputs: uri (required), dealId (required), fileName (required), fileSize, +2 more.
create_deal_custom_fieldB
Create a deals custom field. (POST /dealCustomFields)
Inputs: type (required), label (required), choices, readOnly, +5 more.
create_em_campaignC
Create an email marketing campaign. (POST /emCampaigns)
Inputs: name, origin, subject, bodyHtml, +3 more.
create_em_eventB
Notify Follow Up Boss about marketing emails sent, opens, clicks, bounces, unsubscribes and spam reports. (POST /emEvents)
Inputs: emEvents, extraBody, extraQuery.
create_eventA
Send in a lead or an event related to a lead. (POST /events) Use this — not create_person — when a NEW LEAD needs to be registered and should trigger FUB's lead routing, automations, and per-source workflows. create_person only inserts a bare contact record and triggers none of that; this is the actual lead-ingestion event. Set type to one of Registration, Inquiry, Seller Inquiry, Property Inquiry, General Inquiry, Viewed Property, Saved Property, Visited Website, Incoming Call, Unsubscribed, Property Search, Saved Property Search, Visited Open House, or Viewed Page — Registration for a genuinely new lead. Set source (and system if relevant) since lead routing rules commonly key off source. FUB auto-deduplicates the nested person object by phone/email — no separate deduplicate flag needed here, unlike create_person. ⚠️ If occurredAt is set to more than 1 day in the past, FUB treats the event as historical and will NOT trigger routing/automations at all — leave it unset (defaults to now) or within the last day if the point is to actually trigger workflows; only backdate it deliberately for importing historical data where you specifically don't want anything to fire.
Inputs: type, person, source, system, +12 more.
create_groupC
Create a new group. (POST /groups)
Inputs: name (required), users (required), type, extraBody, +6 more.
create_noteA
Add a note. (POST /notes) If body contains HTML markup, you must also pass isHtml=true — unlike email templates, FUB does not auto-detect HTML in notes.
Inputs: personId (required), body, isHtml, subject, +2 more.
create_people_relationshipB
Create a new relationship for a person. (POST /peopleRelationships)
Inputs: type, emails, phones, lastName, +5 more.
create_personA
Manually add a new person. (POST /people) FUB's docs also list a wildcard "custom*" field here for reading/writing custom fields directly (e.g. a "Closing Date" field as custom.ClosingDate) — that's not a literal field name, so it's not in this tool's fixed schema. Pass custom. entries via extraBody instead. Call list_custom_fields first to get exact names. deduplicate defaults to false, meaning creating a person whose email or phone matches an existing contact creates a SEPARATE duplicate record rather than erring or merging — a common way CRMs end up full of duplicate leads. Unless the user clearly wants an intentional second/separate record (e.g. a shared household phone), pass deduplicate=true, or call get_people_check_duplicate first and confirm with the user if a likely match already exists. ⚠️ This does NOT register a new lead in FUB's sense: it creates a bare contact record only — no lead routing, no automations, no per-source workflows fire. If the user actually means "a new lead just came in" (e.g. from a website registration, an inquiry, an open house sign-in) rather than "just add this person to my CRM," use create_event instead — that's what actually triggers FUB's lead routing and automations.
Inputs: tags, price, stage, emails, +19 more.
create_person_attachmentB
Attach a file to a person. (POST /personAttachments)
Inputs: uri (required), fileName (required), personId (required), fileSize, +2 more.
create_pipelineB
Add a pipeline. (POST /pipelines)
Inputs: name (required), stages, extraBody, extraQuery, +2 more.
create_pondB
Create a pond. (POST /ponds)
Inputs: name (required), userId (required), userIds (required), extraBody, +1 more.
create_reactionB
Add a reaction to a corresponding reference data object, e.g. "Note" or "ThreadedReply" (POST /reactions/{refType}/{refId})
Inputs: refId (required), refType (required), body, extraBody, +1 more.
create_stageB
Create a new stage. (POST /stages)
Inputs: name (required), extraBody, extraQuery, orderWeight.
create_taskB
Create a new task. (POST /tasks)
Inputs: personId (required), name, type, dueDate, +7 more.
create_teamB
Create a new team. (POST /teams)
Inputs: name (required), userIds (required), extraBody, leaderIds, +1 more.
create_templateA
Create a new email template. (POST /templates) body is the raw HTML of the email template directly — there is no separate isHtml/html flag for templates (unlike notes, which need isHtml=true explicitly). FUB templates support %merge_field% placeholders that FUB substitutes when a human actually sends the template (not by this tool — this just saves the template text as-is). Reference:
Contact: %contact_name% (full), %contact_first_name%, %contact_last_name%, %contact_email%, %contact_phone%, %contact_address%, %contact_street%, %contact_city%, %contact_state%, %contact_zipcode%, %contact_country%, %contact_rels_first_name% (first names of the contact's linked relationships, e.g. spouse/family added via peopleRelationships).
Company (from Admin > Company settings): %company_name%, %company_phone%.
Agent / Lender / Sender — same field set, swap the prefix (agent = assigned agent, lender = assigned lender, sender = whoever is actually sending this particular message, which may be neither): %agent_name%, %agent_first_name%, %agent_last_name%, %agent_email%, %agent_phone% (the FUB-assigned calling/texting number), %agent_mobile_phone% (their real/personal number), %agent_merge_field_1% (one free-form field each user sets in My Settings > Other Settings > Edit User Merge Field — commonly a booking link or social profile). ⚠️ %_phone% vs %mobile_phone% is genuinely ambiguous — always confirm with the user which one they mean before using either; picking wrong sends the recipient the wrong callback number.
Inquiry (how the contact became a lead, e.g. clicking "Get more info" on a listing site): %inquiry_address%, %inquiry_address_url% (only if the lead source provided one), %inquiry_address_preview% (renders an HTML photo+link box — email only, meaningless in a plain-text SMS template).
Recently viewed (populated only when synced with a provider that shares property views): %viewed_address%, %viewed_address_url%, %viewed_address_preview%, %last_5_preview% (up to 5 as HTML boxes, email only).
Other: %source_name% (lead source, e.g. "Zillow" — "I saw your inquiry on %source_name%"), %greeting_time% ("Morning"/"Afternoon"/"Evening" based on send time — "Good %greeting_time%, %contact_first_name%"), %tour_time% (populated if the contact scheduled a tour via Zillow).
Custom fields: %custom% (e.g. %custom_website%, %custom_birthday%, %custom_spouse_name%). Call list_custom_fields to confirm a field exists — but note its API name (e.g. customBirthday, camelCase) and its merge-field name (%custom_birthday%, snake_case) are different spellings of the same field, and there's no API that returns the merge-field spelling directly, so confirm the exact form with the user (or FUB's own Merge Fields dropdown in the template composer) if it's not obvious from the label.
A merge field with no value for a given contact is simply left blank when the template is used — not an error, not a visible placeholder.
Inputs: body (required), name (required), subject (required), isShared, +2 more.
create_text_messageA
Create a record of an externally sent text message. (POST /textMessages)
Inputs: message (required), personId (required), toNumber (required), fromNumber (required), +5 more.
create_text_message_templateA
Create a text message template. (POST //textMessageTemplates) FUB templates support %merge_field% placeholders that FUB substitutes when a human actually sends the template (not by this tool — this just saves the template text as-is). Reference: Contact: %contact_name% (full), %contact_first_name%, %contact_last_name%, %contact_email%, %contact_phone%, %contact_address%, %contact_street%, %contact_city%, %contact_state%, %contact_zipcode%, %contact_country%, %contact_rels_first_name% (first names of the contact's linked relationships, e.g. spouse/family added via peopleRelationships). Company (from Admin > Company settings): %company_name%, %company_phone%. Agent / Lender / Sender — same field set, swap the prefix (agent = assigned agent, lender = assigned lender, sender = whoever is actually sending this particular message, which may be neither): %agent_name%, %agent_first_name%, %agent_last_name%, %agent_email%, %agent_phone% (the FUB-assigned calling/texting number), %agent_mobile_phone% (their real/personal number), %agent_merge_field_1% (one free-form field each user sets in My Settings > Other Settings > Edit User Merge Field — commonly a booking link or social profile). ⚠️ %_phone% vs %mobile_phone% is genuinely ambiguous — always confirm with the user which one they mean before using either; picking wrong sends the recipient the wrong callback number. Inquiry (how the contact became a lead, e.g. clicking "Get more info" on a listing site): %inquiry_address%, %inquiry_address_url% (only if the lead source provided one), %inquiry_address_preview% (renders an HTML photo+link box — email only, meaningless in a plain-text SMS template). Recently viewed (populated only when synced with a provider that shares property views): %viewed_address%, %viewed_address_url%, %viewed_address_preview%, %last_5_preview% (up to 5 as HTML boxes, email only). Other: %source_name% (lead source, e.g. "Zillow" — "I saw your inquiry on %source_name%"), %greeting_time% ("Morning"/"Afternoon"/"Evening" based on send time — "Good %greeting_time%, %contact_first_name%"), %tour_time% (populated if the contact scheduled a tour via Zillow). Custom fields: %custom% (e.g. %custom_website%, %custom_birthday%, %custom_spouse_name%). Call list_custom_fields to confirm a field exists — but note its API name (e.g. customBirthday, camelCase) and its merge-field name (%custom_birthday%, snake_case) are different spellings of the same field, and there's no API that returns the merge-field spelling directly, so confirm the exact form with the user (or FUB's own Merge Fields dropdown in the template composer) if it's not obvious from the label. A merge field with no value for a given contact is simply left blank when the template is used — not an error, not a visible placeholder. Texting-specific, per FUB's own Compliance/Carrier Filtering guidance: initial/first-outreach text templates should include opt-out language ("Reply STOP to unsubscribe") and introduce the sender/company by name. Avoid designing a template purely for identical mass-blasting — carriers filter messages that look like spam, personalization (via merge fields) reduces that risk. If the template includes a URL, use the full URL rather than a shortened link, since shorteners are more likely to get carrier-filtered.
Inputs: name (required), message (required), isShared, extraBody, +1 more.
create_webhookB
Subscribe to a new webhook. (POST /webhooks)
Inputs: url (required), event (required), extraBody, extraQuery.
get_appointmentC
Retrieve an appointment by id. (GET /appointments/{id})
Inputs: id (required), extraQuery.
get_appointment_outcomeB
Retrieve an appointment outcome by ID. (GET /appointmentOutcomes/{id})
Inputs: id (required), extraQuery.
get_appointment_typeC
Retrieve an appointment type by ID (GET /appointmentTypes/{id})
Inputs: id (required), extraQuery.
get_automationC
Retrieve an Automation by ID. (GET /automations/{id})
Inputs: id (required), extraQuery.
get_automations_personB
Retrieve an Automation-Person pairing. (GET /automationsPeople/{id})
Inputs: id (required), extraQuery.
get_callB
Retrieve a call by id. (GET /calls/{id})
Inputs: id (required), extraQuery.
get_custom_fieldB
Get a custom field by id. (GET /customFields/{id})
Inputs: id (required), extraQuery.
get_dealA
Retrieve a deal by id. (GET /deals/{id})
Inputs: id (required), extraQuery.
get_deal_attachmentC
Get a deal attachment by id. (GET /dealAttachments/{id})
Inputs: id (required), extraQuery.
get_deal_custom_fieldB
Get a deals custom field by ID. (GET /dealCustomFields/{id})
Inputs: id (required), extraQuery.
get_eventA
Retrieve a single event by id. (GET /events/{id})
Inputs: id (required), extraQuery.
get_groupB
Retrieve a group by id. (GET /groups/{id})
Inputs: id (required), extraQuery.
get_groups_round_robinC
Lists groups and includes round-robin data. (GET /groups/roundRobin)
Inputs: sort, type, extraQuery.
get_identityB
Get identity and authentication information. (GET /identity)
Inputs: extraQuery.
get_inbox_apps_conversations_participantsC
Retrieves participants in an Inbox App conversation. (GET /inboxApps/{inboxAppId}/conversations/{extConversationId}/participants)
Inputs: inboxAppId (required), extConversationId (required), extraQuery.
get_installed_appB
Lists Inbox App installation(s) and ID(s) for your Published Inbox App on the current FUB account. (GET /inboxApps/installedApps/{publishedInboxAppId})
Inputs: publishedInboxAppId (required), extraQuery.
get_meB
Retrieve information about the currently authenticated user. (GET /me)
Inputs: extraQuery.
get_noteA
Retrieve a note by id. (GET /notes/{id})
Inputs: id (required), extraQuery, includeReactions, includeThreadedReplies.
get_people_check_duplicateB
Check whether a person exists in Follow Up Boss. (GET /people/checkDuplicate)
Inputs: email, phone, extraQuery.
get_people_relationshipA
Get a specific relationship. (GET /peopleRelationships/{id})
Inputs: id (required), extraQuery.
get_people_unclaimedA
Get unclaimed leads. (GET /people/unclaimed) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: limit, offset, extraQuery.
get_personA
Retrieve a person by id. (GET /people/{id}) Use fields to request only what you need instead of full records when scanning many people. For custom fields, call list_custom_fields first to discover the exact field names/labels rather than guessing.
Inputs: id (required), fields, extraQuery.
get_person_attachmentC
Retrieve an attachment by ID. (GET /personAttachments/{id})
Inputs: id (required), extraQuery.
get_pipelineB
Retrieve a pipeline by id. (GET /pipelines/{id})
Inputs: id (required), extraQuery.
get_pondA
Get a pond by id. (GET /ponds/{id})
Inputs: id (required), extraQuery.
get_rate_limit_limitsA
Currently-configured rate limits for the calling partner system. Cheaper than /v1/rateLimit/usage (no Redis fan-out). (GET /rateLimit/limits)
Inputs: extraQuery.
get_rate_limit_usageB
24-hour request volume, rate-limit hits, and currently-configured limits for the calling partner system. (GET /rateLimit/usage)
Inputs: extraQuery.
get_reactionA
Fetch a reaction (GET /reactions/{id})
Inputs: id (required), extraQuery.
get_smart_listB
Retrieve a Smart List by id. (GET /smartLists/{id})
Inputs: id (required), extraQuery.
get_stageC
Get a stage by id. (GET /stages/{id})
Inputs: id (required), extraQuery.
get_taskA
Get a task by id. (GET /tasks/{id})
Inputs: id (required), extraQuery.
get_teamA
Get a team by id. (GET /teams/{id})
Inputs: id (required), extraQuery.
get_templateA
Retrieve an email template by id, optionally merging fields. (GET /templates/{id})
Inputs: id (required), extraQuery, mergePersonId.
get_text_messageA
Retrieve a text message by id. (GET /textMessages/{id})
Inputs: id (required), extraQuery.
get_text_message_templateB
Retrieve a text message template by id. (GET /textMessageTemplates/{id})
Inputs: id (required), extraQuery.
get_threaded_replyB
Fetches a threaded reply (GET /threadedReplies/{id})
Inputs: id (required), extraQuery.
get_userC
Retrieve a user by id. (GET /users/{id})
Inputs: id (required), extraQuery.
get_webhookB
Get details of a specific webhook. (GET /webhooks/{id})
Inputs: id (required), extraQuery.
get_webhook_eventA
Get a list of events for a given webhook. (GET /webhookEvents/{id})
Inputs: id (required), extraQuery.
list_action_plansA
Get a list of Action Plans. (GET /actionPlans) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes. ⚠️ Action Plans are a deprecated FUB feature — Automations are the current, recommended mechanism going forward. Unless the user specifically names an existing legacy Action Plan they already rely on, prefer the automationsPerson tools (create_automations_person to trigger one, update_automations_person to pause/unpause) over this one for new workflows.
Inputs: ids, sort, limit, names, +3 more.
list_action_plans_peopleA
List Action Plans applied to a particular person or list people on a particular Action Plan. (GET /actionPlansPeople) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes. ⚠️ Action Plans are a deprecated FUB feature — Automations are the current, recommended mechanism going forward. Unless the user specifically names an existing legacy Action Plan they already rely on, prefer the automationsPerson tools (create_automations_person to trigger one, update_automations_person to pause/unpause) over this one for new workflows.
Inputs: limit, offset, personId, extraQuery, +1 more.
list_appointment_outcomesA
List appointment outcomes. (GET /appointmentOutcomes) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: sort, limit, offset, extraQuery.
list_appointmentsA
Search for appointments. (GET /appointments) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: end, limit, start, offset, +3 more.
list_appointment_typesA
List appointment types. (GET /appointmentTypes) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: sort, limit, offset, extraQuery.
list_automationsA
Get a list of Automations (GET /automations) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: limit, offset, status, extraQuery, +2 more.
list_automations_peopleA
Get a list of pairings of Automations and the People on which they have or will be run. (GET /automationsPeople)
Inputs: status, personId, extraQuery, automationId.
list_callsA
Search for calls. (GET /calls) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: limit, phone, offset, personId, +3 more.
list_custom_fieldsA
List all custom fields. (GET /customFields) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: sort, label, limit, offset, +1 more.
list_deal_custom_fieldsA
List all deals custom fields available in your account. (GET /dealCustomFields) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: sort, label, limit, offset, +1 more.
list_dealsC
Search for deals. (GET /deals)
Inputs: status, userId, personId, extraQuery, +3 more.
list_em_campaignsA
List email marketing campaigns. (GET /emCampaigns)
Inputs: origin, originId, extraQuery.
list_em_eventsA
List email marketing events. (GET /emEvents) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: type, limit, offset, personId, +2 more.
list_eventsA
Search for events. (GET /events) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: next, type, limit, offset, +4 more.
list_groupsC
List groups. (GET /groups)
Inputs: sort, type, extraQuery.
list_notesA
List notes, optionally filtered by person. This endpoint is NOT in FUB's published API docs (only GET /notes/{id} is documented there), but the plural GET /notes endpoint works today and supports filtering by personId — confirmed against the live API. Since it's undocumented, treat it as best-effort: if FUB changes this behavior, fall back to get_note by id. (GET /notes) Defaults to limit=100. This endpoint paginates via a cursor, not offset: pass the previous response's _metadata.next value as next to get the following page.
Inputs: next, limit, personId, extraQuery.
list_peopleA
Search for people. (GET /people) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes. Use fields to request only what you need instead of full records when scanning many people. For custom fields, call list_custom_fields first to discover the exact field names/labels rather than guessing. FUB's docs also list a wildcard "custom*" field here for reading/writing custom fields directly (e.g. a "Closing Date" field as custom.ClosingDate) — that's not a literal field name, so it's not in this tool's fixed schema. Pass custom. entries via extraQuery instead. Call list_custom_fields first to get exact names.
Inputs: id, name, sort, tags, +23 more.
list_people_relationshipsC
Get relationships between people in Follow Up Boss. (GET /peopleRelationships)
Inputs: name, sort, lastName, personId, +2 more.
list_pipelinesC
Search for pipelines. (GET /pipelines)
Inputs: name, extraQuery.
list_pondsA
Get a list of ponds. (GET /ponds) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: limit, offset, extraQuery.
list_smart_listsA
Get a list of Smart Lists. (GET /smartLists) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: all, fub2, limit, offset, +1 more.
list_stagesA
Retrieve a list of stages. (GET /stages) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: sort, limit, offset, extraQuery.
list_tasksC
Get a list of tasks. (GET /tasks)
Inputs: due, name, type, dueEnd, +6 more.
list_team_inboxesC
Get a list of Team Inboxes (GET /teamInboxes)
Inputs: extraQuery.
list_teamsA
Get a list of teams. (GET /teams) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: limit, offset, extraQuery.
list_templatesA
Lists all email templates. (GET /templates) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: limit, offset, extraQuery.
list_text_messagesA
List text messages for a person or phone number. (GET /textMessages)
Inputs: personId, toNumber, extraQuery, fromNumber.
list_text_message_templatesA
Lists all text message templates. (GET /textMessageTemplates) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: limit, offset, extraQuery.
list_timeframesC
Get a list of timeframes. (GET /timeframes)
Inputs: extraQuery.
list_usersA
Search for users. (GET /users) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes. Use fields to request only what you need instead of full records when scanning many people. For custom fields, call list_custom_fields first to discover the exact field names/labels rather than guessing.
Inputs: name, role, sort, email, +5 more.
list_webhooksA
Get a list of webhooks. (GET /webhooks) Defaults to limit=100 (FUB's max per page) rather than its own default of 10 — bulk requests are the common case here. If the response's _metadata shows more results remain, keep paginating: use offset for offset-based endpoints, or the _metadata.next cursor value (as the next argument) for cursor-based endpoints like notes.
Inputs: sort, event, limit, offset, +2 more.
post_inbox_apps_conversations_participantsA
Adds a participant to an Inbox App conversation. (POST /inboxApps/{inboxAppId}/conversations/{extConversationId}/participants)
Inputs: inboxAppId (required), extConversationId (required), name, email, +7 more.
post_inbox_apps_installC
Installs your Inbox App for an account. (POST /inboxApps/install)
Inputs: userId (required), subscriptionUrl (required), publishedInboxAppId (required), extraBody, +1 more.
post_inbox_apps_messageB
Adds a message to an existing or new Inbox App conversation. (POST /inboxApps/{inboxAppId}/message)
Inputs: sender (required), message (required), inboxAppId (required), isIncoming (required), +14 more.
post_inbox_apps_noteB
Adds a note to an Inbox App conversation. (POST /inboxApps/{inboxAppId}/note)
Inputs: body (required), user (required), inboxAppId (required), externalConversationId (required), +2 more.
post_inbox_apps_system_messageC
Adds a system confirmation message to an existing or new Inbox App conversation. (POST /inboxApps/{inboxAppId}/systemMessage)
Inputs: message (required), inboxAppId (required), externalMessageId (required), externalConversationId (required), +5 more.
post_people_claimB
Claim a lead. (POST /people/claim)
Inputs: personId, extraBody, extraQuery.
post_people_ignore_unclaimedC
Ignore a lead. (POST /people/ignoreUnclaimed)
Inputs: personId, extraBody, extraQuery.
post_templates_mergeA
Merge an email template with multiple recipients. (POST /templates/merge) Despite the name, this almost certainly does NOT send anything — inferred from its identical-shaped sibling post_text_message_templates_merge, which was verified live 2026-09 (firing it at a real phone number produced no delivery and no new record in list_text_messages, only a rendered string back); the email variant itself wasn't separately fired to avoid sending an unwanted email. It's a preview/render utility for the edge case of one message greeting multiple recipients at once (e.g. "Hey Bob, Alice and Carol...") — useful for composing that combined greeting, not for actually delivering it.
Inputs: extraBody, extraQuery, recipients, templateId, +1 more.
post_text_message_templates_mergeA
Merge a text message template with multiple recipients. (POST /textMessageTemplates/merge) Despite the name, this does NOT send anything — verified live 2026-09: firing this at a real phone number produced no delivery and no new record in list_text_messages, only a rendered string back ({"mergedTemplate": "..."}). It's a preview/render utility for the edge case of one text greeting multiple recipients at once (e.g. "Hey Bob, Alice and Carol..."), not an actual send.
Inputs: templateId (required), personId, extraBody, extraQuery, +1 more.
put_inbox_apps_messageC
Update an Inbox App Message. (PUT /inboxApps/{inboxAppId}/message)
Inputs: inboxAppId (required), id, extraBody, extraQuery, +3 more.
update_action_plans_personA
Update the status of an Action Plan to Person relationship. (PUT /actionPlansPeople/{id}) ⚠️ Action Plans are a deprecated FUB feature — Automations are the current, recommended mechanism going forward. Unless the user specifically names an existing legacy Action Plan they already rely on, prefer the automationsPerson tools (create_automations_person to trigger one, update_automations_person to pause/unpause) over this one for new workflows.
Inputs: id (required), status (required), extraBody, extraQuery.
update_appointmentC
Update an appointment. (PUT /appointments/{id})
Inputs: id (required), end (required), start (required), title (required), +9 more.
update_appointment_outcomeC
Update an appointment outcome. (PUT /appointmentOutcomes/{id})
Inputs: id (required), name, extraBody, extraQuery, +1 more.
update_appointment_typeC
Update an appointment type. (PUT /appointmentTypes/{id})
Inputs: id (required), name, extraBody, extraQuery, +1 more.
update_automations_personB
Pause or unpause an Automation for a Person. (PUT /automationsPeople/{id})
Inputs: id (required), status, extraBody, extraQuery.
update_callC
Update a call. (PUT /calls/{id})
Inputs: id (required), note, phone, userId, +9 more.
update_conversationB
Updates an Inbox App conversation. (PUT /inboxApps/{inboxAppId}/conversations/{extConversationId})
Inputs: inboxAppId (required), extConversationId (required), person, subject, +6 more.
update_custom_fieldC
Update a custom field. (PUT /customFields/{id})
Inputs: id (required), label, choices, extraBody, +5 more.
update_dealC
Update a deal. (PUT /deals/{id})
Inputs: id (required), name, price, stageId, +14 more.
update_deal_attachmentB
Update a deal attachment. (PUT /dealAttachments/{id})
Inputs: id (required), uri (required), dealId (required), fileName (required), +3 more.
update_deal_custom_fieldB
Update a deals custom field. (PUT /dealCustomFields/{id})
Inputs: id (required), type (required), label (required), choices, +7 more.
update_em_campaignC
Update an email marketing campaign. (PUT /emCampaigns/{id})
Inputs: id (required), name, subject, bodyHtml, +2 more.
update_groupB
Update a group. (PUT /groups/{id})
Inputs: id (required), name (required), users (required), type, +7 more.
update_noteB
Edit a note. (PUT /notes/{id}) If body contains HTML markup, you must also pass isHtml=true.
Inputs: id (required), body, isHtml, subject, +3 more.
update_people_relationshipC
Update details of a specific relationship. (PUT /peopleRelationships/{id})
Inputs: id (required), type, emails, phones, +5 more.
update_personA
Update a person by id. (PUT /people/{id}) FUB's docs also list a wildcard "custom*" field here for reading/writing custom fields directly (e.g. a "Closing Date" field as custom.ClosingDate) — that's not a literal field name, so it's not in this tool's fixed schema. Pass custom. entries via extraBody instead. Call list_custom_fields first to get exact names. Tag removal has no dedicated endpoint: to remove a tag, first GET this person, filter the tag out of their current tags array yourself, then PUT the full filtered array back (with mergeTags left at its default of false so it replaces rather than merges). To add tags, just pass the new tags with mergeTags=true (this tool's default) so they're unioned with the person's existing tags. ⚠️ DATA LOSS RISK, confirmed against the live API: emails, phones, and addresses are REPLACED wholesale if you include them — there is no merge flag for these like there is for tags. Sending a single new phone number wipes out every other phone number the person had. To add one without losing the rest, GET the person first, append to their existing emails/phones/addresses array yourself, and PUT the complete merged array back. Never send a partial list unless the user explicitly wants everything else removed. collaborators is also settable here even though FUB's own docs don't list it on this endpoint (confirmed working in practice) — it has the same replace-not-merge behavior as tags/phones: omitting an existing collaborator's user id removes them, so GET the person first and merge if you only want to add one. Pass it via extraBody. Setting stage to "Trash" hides the person from default list views (FUB excludes trashed people from GET /people unless includeTrash is set) — it's reversible, but feels like the contact vanished to someone who isn't expecting it, so this requires confirm=true just like a delete, even though it isn't one.
Inputs: id (required), tags, price, stage, +17 more.
update_person_attachmentC
Update an attachment by ID. (PUT /personAttachments/{id})
Inputs: id (required), uri (required), fileName (required), personId (required), +3 more.
update_pipelineC
Update a pipeline. (PUT /pipelines/{id})
Inputs: id (required), name, stages, extraBody, +3 more.
update_pondB
Update a pond by id. (PUT /ponds/{id})
Inputs: id (required), name, userId, userIds, +2 more.
update_stageC
Update a stage. (PUT /stages/{id})
Inputs: id (required), name, extraBody, extraQuery, +1 more.
update_taskC
Update a task. (PUT /tasks/{id})
Inputs: id (required), name, type, personId, +5 more.
update_teamB
Update a team by id. (PUT /teams/{id})
Inputs: id (required), name, userIds, extraBody, +2 more.
update_templateA
Update an email template. (PUT /templates/{id}) FUB templates support %merge_field% placeholders that FUB substitutes when a human actually sends the template (not by this tool — this just saves the template text as-is). Reference: Contact: %contact_name% (full), %contact_first_name%, %contact_last_name%, %contact_email%, %contact_phone%, %contact_address%, %contact_street%, %contact_city%, %contact_state%, %contact_zipcode%, %contact_country%, %contact_rels_first_name% (first names of the contact's linked relationships, e.g. spouse/family added via peopleRelationships). Company (from Admin > Company settings): %company_name%, %company_phone%. Agent / Lender / Sender — same field set, swap the prefix (agent = assigned agent, lender = assigned lender, sender = whoever is actually sending this particular message, which may be neither): %agent_name%, %agent_first_name%, %agent_last_name%, %agent_email%, %agent_phone% (the FUB-assigned calling/texting number), %agent_mobile_phone% (their real/personal number), %agent_merge_field_1% (one free-form field each user sets in My Settings > Other Settings > Edit User Merge Field — commonly a booking link or social profile). ⚠️ %_phone% vs %mobile_phone% is genuinely ambiguous — always confirm with the user which one they mean before using either; picking wrong sends the recipient the wrong callback number. Inquiry (how the contact became a lead, e.g. clicking "Get more info" on a listing site): %inquiry_address%, %inquiry_address_url% (only if the lead source provided one), %inquiry_address_preview% (renders an HTML photo+link box — email only, meaningless in a plain-text SMS template). Recently viewed (populated only when synced with a provider that shares property views): %viewed_address%, %viewed_address_url%, %viewed_address_preview%, %last_5_preview% (up to 5 as HTML boxes, email only). Other: %source_name% (lead source, e.g. "Zillow" — "I saw your inquiry on %source_name%"), %greeting_time% ("Morning"/"Afternoon"/"Evening" based on send time — "Good %greeting_time%, %contact_first_name%"), %tour_time% (populated if the contact scheduled a tour via Zillow). Custom fields: %custom% (e.g. %custom_website%, %custom_birthday%, %custom_spouse_name%). Call list_custom_fields to confirm a field exists — but note its API name (e.g. customBirthday, camelCase) and its merge-field name (%custom_birthday%, snake_case) are different spellings of the same field, and there's no API that returns the merge-field spelling directly, so confirm the exact form with the user (or FUB's own Merge Fields dropdown in the template composer) if it's not obvious from the label. A merge field with no value for a given contact is simply left blank when the template is used — not an error, not a visible placeholder.
Inputs: id (required), body (required), name (required), subject (required), +2 more.
update_text_message_templateA
Update a text message template. (PUT /textMessageTemplates/{id}) FUB templates support %merge_field% placeholders that FUB substitutes when a human actually sends the template (not by this tool — this just saves the template text as-is). Reference: Contact: %contact_name% (full), %contact_first_name%, %contact_last_name%, %contact_email%, %contact_phone%, %contact_address%, %contact_street%, %contact_city%, %contact_state%, %contact_zipcode%, %contact_country%, %contact_rels_first_name% (first names of the contact's linked relationships, e.g. spouse/family added via peopleRelationships). Company (from Admin > Company settings): %company_name%, %company_phone%. Agent / Lender / Sender — same field set, swap the prefix (agent = assigned agent, lender = assigned lender, sender = whoever is actually sending this particular message, which may be neither): %agent_name%, %agent_first_name%, %agent_last_name%, %agent_email%, %agent_phone% (the FUB-assigned calling/texting number), %agent_mobile_phone% (their real/personal number), %agent_merge_field_1% (one free-form field each user sets in My Settings > Other Settings > Edit User Merge Field — commonly a booking link or social profile). ⚠️ %_phone% vs %mobile_phone% is genuinely ambiguous — always confirm with the user which one they mean before using either; picking wrong sends the recipient the wrong callback number. Inquiry (how the contact became a lead, e.g. clicking "Get more info" on a listing site): %inquiry_address%, %inquiry_address_url% (only if the lead source provided one), %inquiry_address_preview% (renders an HTML photo+link box — email only, meaningless in a plain-text SMS template). Recently viewed (populated only when synced with a provider that shares property views): %viewed_address%, %viewed_address_url%, %viewed_address_preview%, %last_5_preview% (up to 5 as HTML boxes, email only). Other: %source_name% (lead source, e.g. "Zillow" — "I saw your inquiry on %source_name%"), %greeting_time% ("Morning"/"Afternoon"/"Evening" based on send time — "Good %greeting_time%, %contact_first_name%"), %tour_time% (populated if the contact scheduled a tour via Zillow). Custom fields: %custom% (e.g. %custom_website%, %custom_birthday%, %custom_spouse_name%). Call list_custom_fields to confirm a field exists — but note its API name (e.g. customBirthday, camelCase) and its merge-field name (%custom_birthday%, snake_case) are different spellings of the same field, and there's no API that returns the merge-field spelling directly, so confirm the exact form with the user (or FUB's own Merge Fields dropdown in the template composer) if it's not obvious from the label. A merge field with no value for a given contact is simply left blank when the template is used — not an error, not a visible placeholder. Texting-specific, per FUB's own Compliance/Carrier Filtering guidance: initial/first-outreach text templates should include opt-out language ("Reply STOP to unsubscribe") and introduce the sender/company by name. Avoid designing a template purely for identical mass-blasting — carriers filter messages that look like spam, personalization (via merge fields) reduces that risk. If the template includes a URL, use the full URL rather than a shortened link, since shorteners are more likely to get carrier-filtered.
Inputs: id (required), name (required), message (required), isShared, +2 more.
update_webhookC
Update a webhook. (PUT /webhooks/{id})
Inputs: id (required), url, event, status, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 133 tools
Most tools map cleanly to a resource+action, but the sheer number (133) and similar names create real ambiguity: create_event vs. create_person, list_events vs. list_em_events, and the people/claim/ignore_unclaimed cluster are easy to confuse. Descriptions help, but the boundaries are not immediately evident from the names alone.
The dominant list_/get_/create_/update_ pattern is undermined by several post_/put_ prefixed tools (post_people_claim, put_inbox_apps_message) and inconsistent singular/plural forms (create_automations_person vs. list_automations_people). This mixes verb styles and noun forms within the same resource families, making the naming pattern unreliable.
133 tools is an extreme count for any MCP server; it far exceeds the 50+ threshold for a severe mismatch. While a full CRM API is inherently large, exposing every endpoint as a separate tool creates a heavy, unwieldy surface that is hard for agents to navigate.
The surface is remarkably broad, covering people, deals, pipelines, stages, notes, calls, tasks, appointments, templates, webhooks, teams, automations, and custom fields. However, there are notable gaps: no delete operation exists for any resource, events lack update, and there is no actual send capability for emails/texts (only template merge/render utilities).
Maintenance
Related MCP Connectors
Run Follow Up Boss from AI chat: ask about leads, get summaries, write notes and tasks back.
Search Follow Up Boss leads, review calls and deals, and add notes, tasks and deal updates.
Real estate CRM for Claude and ChatGPT: find leads and listings, report on pipeline, log follow-ups.
Real estate agency CRM: listings, clients, leads and viewings from your AI assistant (OAuth).
Related MCP Servers
- AlicenseBqualityAmaintenanceMCP server for Follow Up Boss CRM with 157 tools covering 100% of the official API. Manage contacts, deals, pipeline, tasks, emails, smart lists, action plans, webhooks, and more through natural language.13634Elastic 2.0
- AlicenseCqualityCmaintenanceAn MCP server that gives AI agents full access to Follow Up Boss CRM via natural language, enabling CRUD operations on people, deals, appointments, and more through 160 tools.10033 npm1Elastic 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to directly interact with the entire GoHighLevel CRM via 563+ tools across 44 categories, allowing natural language control for contacts, messaging, opportunities, calendars, and more.16 npm1ISC
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact with Follow Up Boss CRM, allowing lead management, task scheduling, and pipeline tracking through natural language.MIT