followupboss-mcp-server
This MCP server provides full read/write access to your Follow Up Boss CRM through AI tools like Claude, enabling natural language management of virtually all CRM data.
Contacts & People: Search, create, update, delete, and claim contacts; check duplicates; manage tags, stages, relationships, attachments, and unclaimed leads.
Deals & Pipelines: Create, update, and delete deals; manage pipeline stages; track values, closing dates, custom fields, and attachments.
Tasks & Appointments: Create, update, and delete tasks and appointments; manage appointment types and outcomes.
Communication: Log and retrieve calls; send texts and view message history; manage email and SMS templates with mail merge.
Events & Notes: Create and list lead events, property inquiries, and notes on contact records.
Email Marketing: Manage campaigns and track email marketing events.
Smart Lists & Action Plans: View smart lists; assign contacts to action plans and automations; update statuses.
Custom Fields: Create, update, and delete custom fields for contacts and deals.
Teams, Groups & Ponds: Manage team structure, round robin groups, and lead ponds.
Webhooks: Set up, update, delete, and list webhooks; retrieve webhook events.
Inbox Apps: Add messages/notes, manage conversation participants, update statuses, and handle reactions and threaded replies.
Identity & Users: Get account/API key info, current user details, list agents, and manage users.
Meta Tools:
aboutandhelptools for usage guidance; optional safe mode to disable delete operations.
Follow Up Boss MCP Server — Built for Realtors
Talk to your Follow Up Boss CRM in plain English from Claude AI (or any MCP-compatible tool). 160 tools covering the official API, including the
aboutandhelptools. Built by a working real estate broker, not a dev shop.
Built by Ed Neuhaus — broker / owner at Neuhaus Realty Group in Austin, Texas. Licensed since 2007, broker since 2009, 19+ years in real estate. I built this because I wanted to talk to my own FUB account in plain English. It's free for self-host use under the Elastic License 2.0.
One-click install on Hostinger
No terminal needed. Get your own server and connect it to Claude on the web, desktop or phone. Pick the KVM 1 plan.
Affiliate link: if you buy through this button, Hostinger pays the author a commission. Your price is the same. The software is free; the server is a paid Hostinger plan.
Step-by-step guide: deploy/hostinger
Three ways to install
Way | Needs a server? | Works in | Setup |
Deploy on Hostinger (button above) | Yes, your own Hostinger VPS | Claude on the web, desktop and phone | About 15 minutes, no terminal |
Claude Desktop file | No, it runs on your computer | Claude Desktop | Download the |
Install it yourself (download the code, or Docker) | Your computer or any server | Any MCP tool | Install it yourself below (uses Terminal) |
New in 2.0
One-click install on Hostinger, with HTTPS and a password login built in.
Tools checked against the Follow Up Boss API docs and a live account. 99 tool descriptions rewritten, and 132 of the 160 tools called against a real account before release. The tools that FUB used to reject now work.
Steadier connections. A server restart no longer drops Claude, and both the new and the older versions of the MCP standard work.
Fewer tools when you want them.
FUB_TOOL_GROUPS(for examplecore,setup) loads only the groups you use:core,setup,marketing,integrations,delete. Every tool also tells Claude whether it only reads or makes changes.New leads first.
listPeoplelists the newest contacts first.
Full list: CHANGELOG.
Other things I'm working on
EdNeuhaus.com — My builder profile. How this project is built: edneuhaus.com/projects/fub-mcp/
NeuhausRE.com — My brokerage's site, AI-powered home search
StaySTRA.com — Short-term rental investment analyzer
Austin MLS MCP — hosted MLS MCP server (live MLS data via Claude, ChatGPT, Perplexity, and more)
Kendall Creek Properties — Sister brokerage
Want to thank me?
Got a real estate referral? I take referrals from licensed agents in any state for clients moving to or from Texas. Reach out via neuhausre.com/contact/.
Write about it. Blog post, LinkedIn, X — tag me and link to neuhausre.com.
Open an issue or PR if you find a bug or build something useful.
WARNING: This tool can read AND change your Follow Up Boss account. It can create and update contacts, deals, tasks, notes, and other data in your CRM. Delete tools are off unless you turn off Safe Mode. Back up your FUB data before you start, and review what the AI wants to change before you confirm it. The authors are not responsible for any data loss or unintended changes to your FUB account.
Read before you set
FUB_SYSTEM/FUB_SYSTEM_KEY(Terms of Service risk)Several FUB API endpoints are marked "Restricted - Registered Systems Only" and require
X-System+X-System-Keyheaders (this MCP exposes them asFUB_SYSTEM+FUB_SYSTEM_KEYenv vars). These endpoints include: webhooks, inbox apps, automations (2.0), text-message logging, person/deal attachments.You get these credentials by registering your own system with FUB. Registration is self-serve at https://apps.followupboss.com/system-registration: you choose the system name, and FUB issues a 32-character key. The name and key are yours alone. FUB's API terms require you to keep the key confidential and not share it.
How FUB uses the name:
On restricted endpoints, FUB checks the name you registered. A name that does not match your key is refused (403), and webhooks are listed and created under the registered name.
On all other endpoints, the name is a label. FUB shows it on the notes and records the MCP creates, so set
FUB_SYSTEMto a name you will recognize in your timeline.DO NOT:
Reuse
X-Systemcredentials from another app or integration you've found online.Use a name you did not register to reach restricted endpoints.
Borrow a partner's credentials.
Doing any of the above to access restricted endpoints may violate Follow Up Boss's Terms of Service and may lead to the suspension of your FUB account. FUB's rate-limit + identification policy is documented at https://docs.followupboss.com/reference/identification.
If you don't have your own legitimate registered-system credentials, leave these env vars unset. The MCP will throw a clear, actionable error on every restricted tool ("requires X-System + X-System-Key …") rather than silently bypassing the gate. The unrestricted 130+ tools all work fine on a regular FUB API key.
Use at your own risk. The authors of this project are not responsible for any TOS violations, account suspensions, bans, or data loss arising from your use of the restricted endpoints.
License note: This project moved from MIT to Elastic License 2.0 in v1.1.2. You may use, modify, and self-host for your own business at no cost. You may not offer it as a hosted/managed service to third parties. For commercial hosting rights, reach out via neuhausre.com/contact/. Versions ≤ v1.1.1 remain MIT-licensed.
What This Does
This server acts as a bridge between your Follow Up Boss account and AI tools like Claude. Once connected, you can talk to Claude in plain English and it will read, create, update, and manage your FUB data directly.
What you can do:
Contacts & People -- Search contacts, create new leads, update stages, manage tags, check duplicates, view relationships
Deals & Pipeline -- Create and manage deals, move them through pipeline stages, track values and closing dates
Tasks & Appointments -- Create follow-up tasks, schedule appointments, set reminders, track outcomes
Communication -- View call logs and text message history. Note: the API's "create text message" endpoint is log-only (FUB does not deliver SMS via the API); it is also a registered-system-only endpoint — see the warning above.
Email Templates -- Create, edit, and merge email templates with contact data
Smart Lists & Action Plans -- View smart lists, assign people to action plans and automations
Custom Fields -- Create and manage custom fields for contacts and deals
Teams, Groups & Ponds -- Manage team structure, round robin groups, and lead ponds
Webhooks -- Set up and manage webhook integrations
And more -- Inbox apps, reactions, threaded replies, email marketing campaigns, timeframes
Related MCP server: Follow Up Boss MCP Server
What You'll Need
A Follow Up Boss account with API access (most paid plans include this)
Claude Desktop, Claude Code, or any MCP-compatible AI tool
Node.js 20 or higher -- This is a free tool that runs JavaScript. If you don't have it, download it from nodejs.org (choose the LTS version)
Install it yourself
Step 1: Get Your FUB API Key
Your API key is like a password that lets this server talk to your FUB account.
Log into Follow Up Boss
Go to Admin (top menu) > Integrations > API Keys & Lead Email
Click Create API Key, name it
Claude, and copy the key (a long string of letters and numbers)
Step 2: Download & Install
If you know git:
git clone https://github.com/mindwear-capitian/followupboss-mcp-server.git
cd followupboss-mcp-server
npm installIf you don't know git:
Click the green "Code" button at the top of this page
Select "Download ZIP"
Unzip the downloaded file
Open Terminal (Mac) or Command Prompt (Windows)
Navigate to the unzipped folder:
cd path/to/followupboss-mcp-serverInstall dependencies:
npm install
Docker (on a server you run yourself):
docker run -d --name fub-mcp -p 127.0.0.1:3000:3000 \
-e FUB_API_KEY=your_api_key_here \
-e MCP_AUTH_PASSWORD=a-password-of-12-or-more-characters \
-v fub-mcp-data:/data \
ghcr.io/mindwear-capitian/followupboss-mcp-server:2The server listens at http://localhost:3000/mcp and asks for that password when an MCP tool connects. Claude on the web and phone need HTTPS, so for those use the Hostinger install. With Docker you can skip Step 3.
Step 3: Run Setup
npm run setupThis will:
Ask for your API key
Test the connection to make sure it works
Ask you to choose Safe Mode or Full Access
Save your settings in a local
.envfileShow you exactly how to connect it to Claude
Safe Mode vs Full Access
Safe Mode (default) | Full Access | |
Read data (contacts, deals, etc.) | Yes | Yes |
Create new records | Yes | Yes |
Update existing records | Yes | Yes |
Delete records | No | Yes |
Tools available | 136 | 160 |
Safe Mode is the default and recommended for most users. It disables the 24 tools that issue HTTP DELETE requests, including inbox app deactivation. Create, update, and bulk-update tools remain available and can still make consequential changes. You can switch modes at any time by changing FUB_SAFE_MODE in your .env file or AI tool config.
Quick Verify (Optional)
Before connecting to Claude, you can verify everything works:
npm testYou should see:
PASS Server starts and MCP handshake succeeds
PASS Lists 136 tools
PASS Read-only API call works (account: ok)
3 passed, 0 failedIf all 3 pass, you're good to go. If something fails, double-check your API key in the .env file.
Step 4: Connect to Your AI Tool
Pick the tool you use below. Each one needs a small config file edit -- the setup wizard (npm run setup) will show you the exact paths and JSON for your computer, but here are the manual instructions for each.
What's a config file? It's a settings file that tells your AI tool where to find this server. You'll copy/paste a small block of text into it. That's it.
Claude Desktop
Open Finder (Mac) or File Explorer (Windows)
Go to this file:
Mac:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
If the file doesn't exist, create it
Paste this (replace the two placeholder values with yours):
{
"mcpServers": {
"followupboss": {
"command": "node",
"args": ["/full/path/to/followupboss-mcp-server/index.js"],
"env": {
"FUB_API_KEY": "your_api_key_here"
}
}
}
}Replace
/full/path/to/with where you downloaded this projectReplace
your_api_key_herewith your FUB API keyRestart Claude Desktop (fully quit and reopen)
Claude Code (CLI)
Run this one command in your terminal (replace the path):
claude mcp add followupboss -- node /full/path/to/followupboss-mcp-server/index.jsThen restart Claude Code.
Cursor
Open Cursor
Go to Settings > Developer > click "Edit Config" (this opens
~/.cursor/mcp.json)Paste this:
{
"mcpServers": {
"followupboss": {
"command": "node",
"args": ["/full/path/to/followupboss-mcp-server/index.js"],
"env": {
"FUB_API_KEY": "your_api_key_here"
}
}
}
}Replace the path and API key with yours
Restart Cursor
Windsurf
Open Windsurf
Go to Settings > Cascade > MCP Servers
Or manually edit this file:
Mac:
~/.codeium/windsurf/mcp_config.jsonWindows:
%USERPROFILE%\.codeium\windsurf\mcp_config.json
Paste this:
{
"mcpServers": {
"followupboss": {
"command": "node",
"args": ["/full/path/to/followupboss-mcp-server/index.js"],
"env": {
"FUB_API_KEY": "your_api_key_here"
}
}
}
}Replace the path and API key with yours
Fully quit and restart Windsurf
VS Code with GitHub Copilot
Requires VS Code 1.99 or newer and GitHub Copilot extension.
Open VS Code
Press
Cmd+Shift+P(Mac) orCtrl+Shift+P(Windows)Type "MCP: Open User Configuration" and select it
Paste this:
{
"servers": {
"followupboss": {
"type": "stdio",
"command": "node",
"args": ["/full/path/to/followupboss-mcp-server/index.js"],
"env": {
"FUB_API_KEY": "your_api_key_here"
}
}
}
}Replace the path and API key with yours
Use the tools in Copilot's Agent mode
Note: VS Code uses
"servers"and requires"type": "stdio"-- slightly different from the other tools.
Cline (VS Code Extension)
Open VS Code with Cline installed
Click the MCP Servers icon in the Cline sidebar
Click "Configure MCP Servers"
Paste this:
{
"mcpServers": {
"followupboss": {
"command": "node",
"args": ["/full/path/to/followupboss-mcp-server/index.js"],
"env": {
"FUB_API_KEY": "your_api_key_here"
}
}
}
}Replace the path and API key with yours
Gemini CLI (Google)
This works with Google's Gemini CLI tool, not the Gemini website.
Edit (or create) this file:
Mac:
~/.gemini/settings.jsonWindows:
%USERPROFILE%\.gemini\settings.json
Paste this:
{
"mcpServers": {
"followupboss": {
"command": "node",
"args": ["/full/path/to/followupboss-mcp-server/index.js"],
"env": {
"FUB_API_KEY": "your_api_key_here"
}
}
}
}Replace the path and API key with yours
Continue.dev (VS Code Extension)
In your project, create a folder called
.continue/mcpServers/if it doesn't existCreate a file called
followupboss.jsoninside itPaste this:
{
"mcpServers": {
"followupboss": {
"command": "node",
"args": ["/full/path/to/followupboss-mcp-server/index.js"],
"env": {
"FUB_API_KEY": "your_api_key_here"
}
}
}
}Replace the path and API key with yours
Use the tools in Continue's Agent mode
ChatGPT, OpenAI API, and Grok
These tools only support remote MCP servers (on the internet with HTTPS), not local ones. The Hostinger install gives you exactly that: use https://<your server>/mcp as the server address and sign in with your password. Claude on the web and phone use the same setup.
Usage Examples
Once connected, just talk to your AI tool normally. Here are some things you can ask:
"Show me all my leads from this week"
"Create a task to follow up with John Smith tomorrow at 2pm"
"What deals do I have in my pipeline over $500k?"
"Add a note to Jane Doe's profile: Had a great phone call, she's interested in the Oak Park listing"
"List all my upcoming appointments for this week"
"Who are my uncontacted leads?"
"Move the Smith deal to the 'Under Contract' stage"
"Show me all contacts tagged 'hot lead'"
"Create a new email template called 'Open House Follow Up'"
"What action plans do I have set up?"
All 160 Available Tools
Events (3 tools)
Tool | Description |
| List events with filtering by person, type, property |
| Create a new event (lead event, property inquiry, etc.) |
| Get a single event by ID |
People / Contacts (8 tools)
Tool | Description |
| Search and filter contacts extensively |
| Create a new contact |
| Get a contact by ID |
| Update contact details, stage, tags, etc. |
| Delete (trash) a contact |
| Check if a contact exists by email or phone |
| List unclaimed leads in ponds |
| Claim an unclaimed lead |
Person Attachments (4 tools)
Tool | Description |
| Attach a file to a contact |
| Get an attachment by ID |
| Update an attachment |
| Delete an attachment |
Relationships (5 tools)
Tool | Description |
| List relationships for a contact |
| Create a relationship between two contacts |
| Get a relationship by ID |
| Update a relationship |
| Delete a relationship |
Identity (2 tools)
Tool | Description |
| Get account information for the API key |
| Get the current authenticated user |
Notes (5 tools)
Tool | Description |
| List notes, optionally filtered by personId |
| Create a note on a contact |
| Get a note by ID |
| Update a note |
| Delete a note |
Calls (4 tools)
Tool | Description |
| List call records |
| Log a call |
| Get a call by ID |
| Update a call record |
Text Messages (3 tools)
Tool | Description |
| List text messages (needs one filter, e.g. personId) |
| Log a text message on a contact (FUB does not send it) |
| Get a text message by ID |
Users (3 tools)
Tool | Description |
| List all users/agents |
| Get a user by ID |
| Delete a user |
Smart Lists (2 tools)
Tool | Description |
| List all smart lists |
| Get a smart list by ID |
Action Plans (4 tools)
Tool | Description |
| List all action plans |
| List people in action plans |
| Add a contact to an action plan |
| Update action plan status for a contact |
Automations (6 tools)
Tool | Description |
| List all automations |
| Get an automation by ID |
| List people in automations |
| Get automation-person entry |
| Add a contact to an automation |
| Update automation status for a contact |
Email Templates (6 tools)
Tool | Description |
| List email templates |
| Create an email template |
| Get a template by ID |
| Update a template |
| Merge template with contact data (mail merge) |
| Delete a template |
Text Message Templates (6 tools)
Tool | Description |
| List text message templates |
| Create a text message template |
| Get a template by ID |
| Update a template |
| Merge template with contact data |
| Delete a template |
Email Marketing (5 tools)
Tool | Description |
| List email marketing events |
| Create email marketing events |
| List email marketing campaigns |
| Create a campaign |
| Update a campaign |
Custom Fields (5 tools)
Tool | Description |
| List all custom fields |
| Create a custom field |
| Get a custom field by ID |
| Update a custom field |
| Delete a custom field |
Stages (5 tools)
Tool | Description |
| List all pipeline stages |
| Create a stage |
| Get a stage by ID |
| Update a stage |
| Delete a stage (moves its people to |
Tasks (5 tools)
Tool | Description |
| List tasks |
| Create a task |
| Get a task by ID |
| Update a task |
| Delete a task |
Appointments (5 tools)
Tool | Description |
| List appointments |
| Create an appointment |
| Get an appointment by ID |
| Update an appointment |
| Delete an appointment |
Appointment Types (5 tools)
Tool | Description |
| List appointment types |
| Create a type |
| Get a type by ID |
| Update a type |
| Delete a type (moves its appointments to |
Appointment Outcomes (5 tools)
Tool | Description |
| List outcomes |
| Create an outcome |
| Get an outcome by ID |
| Update an outcome |
| Delete an outcome (moves its appointments to |
Webhooks (6 tools)
Tool | Description |
| List all webhooks |
| Create a webhook |
| Get a webhook by ID |
| Update a webhook |
| Delete a webhook |
| Get events for a webhook |
Pipelines (5 tools)
Tool | Description |
| List all pipelines |
| Create a pipeline |
| Get a pipeline by ID |
| Update a pipeline |
| Delete a pipeline |
Deals (5 tools)
Tool | Description |
| List deals with filtering |
| Create a deal |
| Get a deal by ID |
| Update a deal |
| Delete a deal |
Deal Attachments (4 tools)
Tool | Description |
| Attach a file to a deal |
| Get an attachment by ID |
| Update an attachment |
| Delete an attachment |
Deal Custom Fields (5 tools)
Tool | Description |
| List deal custom fields |
| Create a deal custom field |
| Get a field by ID |
| Update a field |
| Delete a field |
Groups (6 tools)
Tool | Description |
| List all groups |
| List round robin groups |
| Create a group |
| Get a group by ID |
| Update a group |
| Delete a group |
Teams (5 tools)
Tool | Description |
| List all teams |
| Create a team |
| Get a team by ID |
| Update a team |
| Delete a team |
Team Inboxes (1 tool)
Tool | Description |
| List all team inboxes |
Ponds (5 tools)
Tool | Description |
| List all ponds |
| Create a pond |
| Get a pond by ID |
| Update a pond |
| Delete a pond (gives its people to user |
Timeframes (1 tool)
Tool | Description |
| List all timeframes |
Inbox Apps (10 tools)
Tool | Description |
| Add a message to a conversation |
| Update a message |
| Add a note to a conversation |
| Update conversation status |
| Get conversation participants |
| Add a participant |
| Remove a participant |
| Install an inbox app |
| Deactivate the inbox app |
| List installations |
Reactions (3 tools)
Tool | Description |
| Get reactions for an item |
| Add a reaction |
| Remove a reaction |
Threaded Replies (1 tool)
Tool | Description |
| Get threaded replies for an item |
Convenience Tools
Tool | Description |
| Remove a single tag without affecting others (handles read-modify-write internally) |
| Look up a person by email; reports ambiguity with candidate IDs instead of silently choosing when multiple contacts match |
| Find all people with specific tags (comma-separated, OR logic) |
| Update multiple people at once with automatic rate limiting |
| Discover all tags in your account by scanning contacts |
Meta Tools (2 tools, new in v1.1.2)
Tool | Description |
| Author bio, related projects, contributors, "how to thank me" |
| Usage tips, common tool examples, bug report links |
Rate Limiting
The server automatically retries requests when FUB's rate limits are hit (HTTP 429). It reads the Retry-After header and backs off with increasing delays, up to 3 retries per request. FUB's limits are:
Global: 250 requests per 10 seconds
People updates: 25 per 10 seconds
Notes: 10 per 10 seconds
The bulkUpdatePeople tool also adds a built-in pause every 20 operations to stay under the PUT limit.
Troubleshooting
"Cannot connect" or "Connection refused"
Make sure Node.js is installed: run
node --versionin your terminal (should show v20 or higher)Make sure you ran
npm installin the project folderDouble-check the file path in your Claude config
"Invalid API key" or "401 Unauthorized"
Re-check your API key in FUB: Admin > Integrations > API Keys & Lead Email
Make sure there are no extra spaces when you copy/paste
Run
npm run setupagain to test your key
"Tool not found" in Claude
Restart Claude Desktop after adding the server config
Check that the JSON in your config file is valid (no missing commas or brackets)
Claude doesn't seem to know about FUB
Make sure the server name in your config matches exactly
Check Claude Desktop's developer console for error messages
Try asking Claude: "What MCP tools do you have available?"
FAQ
Is my data safe?
Your API key stays on your computer, or on your own server if you use the Hostinger install, and is sent only to Follow Up Boss's official API. Your CRM data goes between Follow Up Boss, your server, and the AI tool you use (for example Claude). None of it goes to the author.
Does this cost anything?
This server is free to self-host, and its code is public under the Elastic License 2.0 (source-available). You just need a Follow Up Boss account with API access (included in most paid plans).
Can Claude modify my FUB data?
Yes, Claude can create and update records in your FUB account. Delete tools are off by default (Safe Mode). Every tool tells the AI whether it changes data, so tools like Claude can ask you before a change. If you want read-only access, you can create a restricted API key in FUB.
Where are the call recording URLs?
Nowhere, and it is not this server hiding them. Follow Up Boss masks recordingUrl at the API level for every integration -- the raw API returns * Recording URL is hidden for privacy reasons * no matter what headers or permissions you use, and FUB has confirmed directly that recording URLs will never be exposed through the API. Writing a recordingUrl is also a no-op (FUB masks it right back on read), so the call tools no longer accept it. If you need call audio, capture it on the dialer side; you can store your transcript on the call with updateCall (note field). Full story in issue #2.
What's MCP?
MCP (Model Context Protocol) is an open standard created by Anthropic that lets AI tools like Claude connect to external services. Think of it as a universal plug that lets Claude talk to your apps. Learn more about MCP.
Who made this?
Built by Ed Neuhaus, broker at Neuhaus Realty Group and creator of StaySTRA, both in Austin, TX. We use Follow Up Boss every day and built this to make our own workflow faster.
Contributing
Contributions are welcome! Here's how:
Fork this repository
Create a feature branch:
git checkout -b my-featureMake your changes
Test them:
npm run test:offline(no FUB account needed). If you have a test contact,TEST_PERSON_ID=<id> npm run test:livecalls every tool against your own account.Commit:
git commit -m "Add my feature"Push:
git push origin my-featureOpen a Pull Request
Please keep the code style consistent and make sure all 160 tools continue to work.
License
Elastic License 2.0 -- self-host free, no SaaS resale. Versions ≤ v1.1.1 remain MIT-licensed; existing forks of those versions are unaffected. See LICENSE and NOTICE for full terms and attribution.
Built by Ed Neuhaus
Available Tools
136 toolsaboutARead-onlyIdempotent
Get information about this MCP server, its author, and the projects behind it. Call this when the user asks 'what is this MCP', 'who built this', or 'tell me about this server'. Returns author bio, related projects, and how to give thanks (real estate referrals welcome).
Inputs: no named parameters.
addPersonToActionPlanB
Add a person to an action plan
Inputs: personId (required), actionPlanId (required).
addPersonToAutomationC
Add a person to an automation
Inputs: personId (required), automationId (required).
bulkUpdatePeopleADestructive
Apply the same updatePerson changes to many people, throttled (pauses 11s per 20 people). Use this instead of looping updatePerson. Returns per-person success.
Inputs: ids (required), updates (required), mergeTags.
checkDuplicateCRead-onlyIdempotent
Check if a person already exists by email or phone
Inputs: email, phone.
claimPersonC
Claim an unclaimed person
Inputs: personId (required).
createAppointmentA
Create an appointment. Use start/end (UTC; offset suffix allowed), typeId/outcomeId, invitees [{userId}] or [{personId}]. sendInvitation=true emails invitees (SMS too if reminders are on); default false.
Inputs: end (required), start (required), title (required), allDay, +7 more.
createAppointmentOutcomeB
Create an appointment outcome (account owner only).
Inputs: name, orderWeight.
createAppointmentTypeB
Create an appointment type (account owner only).
Inputs: name, orderWeight.
createCallB
Log a call on a person. personId, phone, and isIncoming are required. userId can only be set by administrators (defaults to API user).
Inputs: phone (required), personId (required), isIncoming (required), note, +6 more.
createCustomFieldA
Create a custom field (account owners only). The type cannot be changed later.
Inputs: type (required), label (required), choices, hideIfEmpty, +2 more.
createDealA
Create a deal. name and stageId are required. Use peopleIds (array) and price (whole number); do not use personId or value. Custom field values may be passed as extra properties (e.g. customField1).
Inputs: name (required), stageId (required), price, userIds, +12 more.
createDealAttachmentA
Attach an externally hosted file to a deal by URI. Restricted to registered systems (needs FUB_SYSTEM and FUB_SYSTEM_KEY). FUB does not host uploads here; omitting uri returns 403.
Inputs: uri (required), dealId (required), fileName (required), fileSize.
createDealCustomFieldA
Create a deal custom field. Only the account owner can do this. label and type are required; choices applies only to dropdown fields.
Inputs: type (required), label (required), choices, readOnly, +3 more.
createEmCampaignA
Create an email marketing campaign. The origin + originId pair must be unique; never reuse it. Subject and bodyHtml support merge fields.
Inputs: origin (required), originId (required), name, subject, +1 more.
createEmEventB
Send email marketing events to FUB, up to 1000 per call. Recipients with no matching contact are skipped and listed in recipientsNotFound.
Inputs: emEvents (required).
createEventA
Create an event (lead registration, inquiry, page view). Dedupes the person by phone/email and creates them if new. Events older than 1 day count as historical and fire no workflows. 'Inquiry' becomes Property Inquiry if property is set, else General Inquiry.
Inputs: type, person, source, system, +10 more.
createGroupA
Create a lead-routing group. Admin accounts only. name and users (user IDs) are required; the member list key is users, not userIds.
Inputs: name (required), users (required), type, claimWindow, +4 more.
createNoteC
Create a note on a person.
Inputs: personId (required), body, isHtml, subject.
createPersonA
Create a person. Custom fields: add top-level keys prefixed 'custom' (e.g. customClosingDate; see listCustomFields). Set deduplicate=true to avoid duplicates. source and sourceUrl can only be set here, not on update.
Inputs: tags, price, stage, emails, +17 more.
createPersonAttachmentA
Attach an externally-hosted file to a person. "Restricted - Registered Systems Only": requires FUB_SYSTEM + FUB_SYSTEM_KEY env vars. uri must point to an externally hosted file — FUB does NOT host uploads via this endpoint (omitting URI returns 403).
Inputs: uri (required), fileName (required), personId (required), fileSize.
createPipelineA
Create a pipeline with optional stages (account owner only). Each stage needs name and closedStage.
Inputs: name (required), stages, description, orderWeight.
createPondB
Create a pond. name, userId (the pond lead agent) and userIds (all member user IDs) are all required.
Inputs: name (required), userId (required), userIds (required).
createReactionA
Add an emoji reaction to a Note, Call or ThreadedReply as the API key owner. Beta endpoint.
Inputs: refId (required), refType (required), body.
createRelationshipA
Create a relationship contact (own record, e.g. Spouse) linked to a person. It is not a link between two existing people.
Inputs: type, emails, phones, lastName, +3 more.
createStageA
Create a stage. orderWeight defaults to 1000; FUB then renumbers all stages in steps of 1000.
Inputs: name (required), orderWeight.
createTaskA
Create a task on a person. personId is required, and one of assignedUserId or assignedTo is required. dueDate is YYYY-MM-DD; use dueDateTime for a specific time.
Inputs: name, type, dueDate, personId, +5 more.
createTeamA
Create a team. name and userIds (all member user IDs) are required; leaderIds is the complete list of team leaders. Needs team access (403 otherwise).
Inputs: name (required), userIds (required), leaderIds.
createTemplateB
Create an email template. Merge fields (e.g. %contact_first_name%) work only in subject and body.
Inputs: body (required), name (required), subject (required), isShared.
createTextMessageA
LOG a text already sent by a registered SMS system; it does not send anything. Needs X-System credentials. personId, message, toNumber, fromNumber are all required.
Inputs: message (required), personId (required), toNumber (required), fromNumber (required), +3 more.
createTextMessageTemplateC
Create a text message template. Message text goes in message.
Inputs: name (required), message (required), isShared.
createWebhookB
Create a webhook for one event. url must be https. Account owner or registered system only.
Inputs: url (required), event (required).
getAppointmentCRead-onlyIdempotent
Get an appointment by ID
Inputs: id (required).
getAppointmentOutcomeCRead-onlyIdempotent
Get appointment outcome by ID
Inputs: id (required).
getAppointmentTypeCRead-onlyIdempotent
Get appointment type by ID
Inputs: id (required).
getAutomationCRead-onlyIdempotent
Get an automation by ID
Inputs: id (required).
getAutomationPersonCRead-onlyIdempotent
Get an automation-person entry by ID
Inputs: id (required).
getCallBRead-onlyIdempotent
Get a call by ID
Inputs: id (required).
getCurrentUserARead-onlyIdempotent
Get the current authenticated user (GET /me)
Inputs: no named parameters.
getCustomFieldCRead-onlyIdempotent
Get a custom field by ID
Inputs: id (required).
getDealCRead-onlyIdempotent
Get a deal by ID
Inputs: id (required).
getDealAttachmentCRead-onlyIdempotent
Get a deal attachment by ID
Inputs: id (required).
getDealCustomFieldBRead-onlyIdempotent
Get a deal custom field by ID
Inputs: id (required).
getEventCRead-onlyIdempotent
Get a single event by ID
Inputs: id (required).
getGroupCRead-onlyIdempotent
Get a group by ID
Inputs: id (required).
getIdentityARead-onlyIdempotent
Get identity/account information for the API key
Inputs: no named parameters.
getNoteCRead-onlyIdempotent
Get a note by ID
Inputs: id (required).
getPersonARead-onlyIdempotent
Get one person by ID. Pass fields=allFields or allCustom to include custom fields.
Inputs: id (required), fields.
getPersonAttachmentCRead-onlyIdempotent
Get a person attachment by ID
Inputs: id (required).
getPersonByEmailARead-onlyIdempotent
Look up one person by email. Returns the contact, or an ambiguity result with candidate IDs. Use this to find a contact; use listPeople for other filters.
Inputs: email (required).
getPipelineBRead-onlyIdempotent
Get a pipeline by ID
Inputs: id (required).
getPondCRead-onlyIdempotent
Get a pond by ID
Inputs: id (required).
getReactionsARead-onlyIdempotent
Get ONE reaction by the reaction's own ID. To list a note's reactions, fetch the note with includeReactions=true instead.
Inputs: id (required).
getRelationshipCRead-onlyIdempotent
Get a relationship by ID
Inputs: id (required).
getSmartListCRead-onlyIdempotent
Get a smart list by ID
Inputs: id (required).
getStageCRead-onlyIdempotent
Get a stage by ID
Inputs: id (required).
getTaskCRead-onlyIdempotent
Get a task by ID
Inputs: id (required).
getTeamCRead-onlyIdempotent
Get a team by ID
Inputs: id (required).
getTemplateBRead-onlyIdempotent
Get an email template by ID
Inputs: id (required).
getTextMessageBRead-onlyIdempotent
Get a text message by ID
Inputs: id (required).
getTextMessageTemplateBRead-onlyIdempotent
Get a text message template by ID
Inputs: id (required).
getThreadedRepliesARead-onlyIdempotent
Get ONE threaded reply by the reply's own ID. To list a note's replies, fetch the note with includeThreadedReplies=true instead.
Inputs: id (required).
getUserCRead-onlyIdempotent
Get a user by ID
Inputs: id (required).
getWebhookBRead-onlyIdempotent
Get a webhook by ID. Account owner or registered system only.
Inputs: id (required).
getWebhookEventsARead-onlyIdempotent
Get the events delivered for a webhook (id, eventCreated, event, resourceIds, uri). Account owner or registered system only.
Inputs: id (required).
helpARead-onlyIdempotent
Get usage tips for this MCP server, common tool examples, and how to report bugs or request features. Call this when the user asks for help, examples, or how to use this MCP.
Inputs: no named parameters.
inboxAppAddMessageA
Add a message to an inbox app conversation (creates the conversation on first use). Conversations are keyed by YOUR externalConversationId. person and owner are needed on the first message of a conversation.
Inputs: sender (required), message (required), inboxAppId (required), isIncoming (required), +12 more.
inboxAppAddNoteB
Add an internal note to an inbox app conversation, keyed by your externalConversationId.
Inputs: body (required), user (required), inboxAppId (required), externalConversationId (required).
inboxAppCreateParticipantB
Add a participant to an inbox app conversation. Give exactly one of personId, userId, relationshipId, or name/email/phone.
Inputs: inboxAppId (required), extConversationId (required), name, email, +5 more.
inboxAppGetParticipantsC
List participants of an inbox app conversation.
Inputs: inboxAppId (required), extConversationId (required).
inboxAppInstallA
Install an inbox app for a user or account-wide. Needs the publishedInboxAppId from FUB's app catalog and a webhook subscriptionUrl for replies.
Inputs: userId (required), subscriptionUrl (required), publishedInboxAppId (required).
inboxAppUpdateConversationA
Update an inbox app conversation: subject, archive state, person, or assignment. Send only fields to change.
Inputs: inboxAppId (required), extConversationId (required), person, subject, +4 more.
inboxAppUpdateMessageA
Update the delivery status of an inbox app message. Identify the message by id or externalMessageId. Message text cannot be changed here.
Inputs: inboxAppId (required), id, deliveryStatus, externalMessageId, +1 more.
listActionPlansCRead-onlyIdempotent
List action plans. Filter by status, names, or IDs.
Inputs: ids, next, sort, limit, +3 more.
listActionPlansPeopleCRead-onlyIdempotent
List people assigned to action plans
Inputs: limit, offset, personId, actionPlanId.
listAppointmentOutcomesBRead-onlyIdempotent
List appointment outcomes. Default sort is orderWeight.
Inputs: next, sort, limit, offset.
listAppointmentsARead-onlyIdempotent
List appointments. Filter by personId (comma list allowed), userId, or a start+end date range (both required together).
Inputs: end, next, limit, start, +3 more.
listAppointmentTypesCRead-onlyIdempotent
List appointment types. Default sort is orderWeight.
Inputs: next, sort, limit, offset.
listAutomationsBRead-onlyIdempotent
List Automations 2.0 automations. Needs registered-system credentials and Automations 2.0.
Inputs: next, limit, offset, status, +2 more.
listAutomationsPeopleBRead-onlyIdempotent
List person/automation pairings. Needs registered-system credentials.
Inputs: next, limit, offset, status, +2 more.
listAvailableTagsARead-onlyIdempotent
List distinct tags by scanning recent contacts (up to 500, 100 per page). Rarely used tags may be missed. Use searchPeopleByTag to find people with a known tag.
Inputs: limit.
listCallsARead-onlyIdempotent
List calls, filterable by person or phone numbers.
Inputs: next, limit, phone, offset, +3 more.
listCustomFieldsBRead-onlyIdempotent
List custom fields. Use limit=100 to get all in one call.
Inputs: sort, label, limit, offset.
listDealCustomFieldsARead-onlyIdempotent
List deal custom fields. Paginated: FUB returns 10 per page unless limit is set; pass limit=100 to get more in one call.
Inputs: next, sort, label, limit, +1 more.
listDealsARead-onlyIdempotent
List deals, filtered by pipeline, user, person or status. Archived and Deleted deals are hidden unless includeArchived=1 or includeDeleted=1. Use getDeal for one deal by ID.
Inputs: id, next, sort, limit, +9 more.
listEmCampaignsARead-onlyIdempotent
List email marketing campaigns, optionally by origin system and origin ID.
Inputs: limit, offset, origin, originId.
listEmEventsCRead-onlyIdempotent
List email marketing events (delivered, opened, clicked, etc).
Inputs: type, limit, offset, personId, +1 more.
listEventsARead-onlyIdempotent
List events, newest first by FUB default. Filter by person, event type, or property.
Inputs: next, type, limit, offset, +3 more.
listGroupsARead-onlyIdempotent
List lead-routing groups (not accessible to lender accounts). Returns up to 100 per call; if _metadata.next is set, call again with next.
Inputs: next, sort, type, limit, +1 more.
listInboxAppInstallationsARead-onlyIdempotent
List installations of one published inbox app. Needs a registered third-party system (FUB_SYSTEM and FUB_SYSTEM_KEY).
Inputs: publishedInboxAppId (required), next, limit, offset.
listNotesBRead-onlyIdempotent
List notes, optionally filtered by personId
Inputs: limit, offset, personId.
listPeopleARead-onlyIdempotent
List/search people, newest created first by default. Custom-field filters: pass any custom* key (e.g. customClosingDate); dates: ',2026-01-01' = on or before, '2026-01-01' = on or after, 'a,b' = inclusive. Filter by name, email, phone, stage name, tags (ANY), owner, price, smart list.
Inputs: id, name, next, sort, +23 more.
listPipelinesBRead-onlyIdempotent
List pipelines, optionally by exact name.
Inputs: name, next, limit, offset.
listPondsARead-onlyIdempotent
List ponds (shared lead pools). Returns up to 100 per call; if _metadata.next is set, call again with next.
Inputs: next, limit, offset.
listRelationshipsARead-onlyIdempotent
List relationship contacts (spouse, partner, etc.), optionally for one person or by name.
Inputs: name, next, sort, limit, +4 more.
listRoundRobinGroupsARead-onlyIdempotent
List round robin groups, including each group's next round-robin user. Not accessible to lender accounts.
Inputs: sort, type.
listSmartListsARead-onlyIdempotent
List all smart lists. By default only classic FUB smart lists are returned. Pass all: true to also include smart lists created in the current FUB UI (otherwise modern smart lists are invisible).
Inputs: all, fub2, next, limit, +1 more.
listStagesCRead-onlyIdempotent
List pipeline stages. Default sort is orderWeight.
Inputs: next, sort, limit, offset.
listTasksARead-onlyIdempotent
List tasks. Use due=overdue for overdue tasks, due=today for today's, assignedUserId for one user's tasks, personId for one contact's. Add isCompleted=false for open tasks only. Filters combine.
Inputs: due, name, next, sort, +10 more.
listTeamInboxesARead-onlyIdempotent
List team inboxes with their users. Returns up to 100 per call; if _metadata.next is set, call again with next.
Inputs: next, limit, offset.
listTeamsARead-onlyIdempotent
List teams with their userIds and leaderIds. Returns up to 100 per call; if _metadata.next is set, call again with next.
Inputs: next, limit, offset.
listTemplatesCRead-onlyIdempotent
List email templates
Inputs: next, limit, offset.
listTextMessagesARead-onlyIdempotent
List text messages. FUB requires at least one filter: personId, phone, toNumber, fromNumber, threadId, sharedInboxId, groupTextId, participants or id.
Inputs: id, next, limit, phone, +8 more.
listTextMessageTemplatesCRead-onlyIdempotent
List text message templates
Inputs: next, limit, offset.
listTimeframesARead-onlyIdempotent
List timeframes (lead time-to-buy options). Returns up to 100 per call; if _metadata.next is set, call again with next.
Inputs: next, limit, offset.
listUnclaimedBRead-onlyIdempotent
List unclaimed people (in ponds, not assigned)
Inputs: limit, offset.
listUsersBRead-onlyIdempotent
List users (agents, brokers, lenders). Filter by role, exact name, or email.
Inputs: id, name, next, role, +6 more.
listWebhooksARead-onlyIdempotent
List webhooks. Account owner or registered system only. Filter by event or status.
Inputs: next, sort, event, limit, +2 more.
mergeTemplateARead-onlyIdempotent
Merge an email template with a person's data and return the rendered email. Does not send anything.
Inputs: recipients, templateId, mergePersonId.
mergeTextMessageTemplateARead-onlyIdempotent
Merge a text message template with a person's data and return the rendered text. Does not send anything.
Inputs: templateId (required), personId, recipients.
removeTagFromPersonADestructiveIdempotent
Remove one tag from a person, leaving other tags untouched (case-insensitive). Use this instead of updatePerson tags, which replaces ALL tags.
Inputs: id (required), tag (required).
searchPeopleByTagARead-onlyIdempotent
Find people with a tag (GET /people?tags=). Use this for a simple tag lookup; use listPeople when combining tags with other filters. OR-matching of multiple tags is unverified.
Inputs: tags (required), next, sort, limit, +2 more.
updateActionPlanPersonCDestructiveIdempotent
Update a person's action plan status
Inputs: id (required), status.
updateAppointmentADestructiveIdempotent
Update an appointment. FUB requires start and end on EVERY update (even partial edits) or it returns 'Valid Start and End dates are required'. Refetch with getAppointment first if you only have the id. Invitees: [{userId:int}] for a FUB user, [{personId:int}] for a contact (optional name/email). The shape {type,id} is NOT FUB's; it is auto-converted, but prefer userId/personId. This tool never sends invitation emails (sendInvitation is not sent; FUB's default is off), but FUB syncs appointments to Google/Outlook calendars for invitees, so a person invitee may still get a calendar invite from the calendar side.
Inputs: id (required), end, start, title, +6 more.
updateAppointmentOutcomeBDestructiveIdempotent
Update an appointment outcome (account owner only).
Inputs: id (required), name, orderWeight.
updateAppointmentTypeBDestructiveIdempotent
Update an appointment type (account owner only).
Inputs: id (required), name, orderWeight.
updateAutomationPersonADestructiveIdempotent
Pause or resume a person in an automation. Needs registered-system credentials.
Inputs: id (required), status.
updateCallADestructiveIdempotent
Update a call record. Only calls created by the same API system/account can be updated.
Inputs: id (required), note, phone, userId, +6 more.
updateCustomFieldADestructiveIdempotent
Update a custom field (account owners only). The type cannot be changed; delete and recreate instead.
Inputs: id (required), label, choices, hideIfEmpty, +2 more.
updateDealADestructiveIdempotent
Update a deal by ID; send only fields to change. peopleIds and userIds replace the full list. Use peopleIds (not personId) and price (not value). Custom field values may be passed as extra properties (e.g. customField1).
Inputs: id (required), name, price, stageId, +12 more.
updateDealAttachmentADestructiveIdempotent
Update a deal attachment by ID. FUB requires dealId, uri and fileName on every update, even if unchanged.
Inputs: id (required), uri (required), dealId (required), fileName (required), +1 more.
updateDealCustomFieldADestructiveIdempotent
Update a deal custom field by ID. Only the account owner can do this. Send only fields to change.
Inputs: id (required), type, label, choices, +4 more.
updateEmCampaignADestructiveIdempotent
Update an email campaign's subject or body. Only account owners and admins can do this. Merge fields are allowed.
Inputs: id (required), name, origin, subject, +2 more.
updateGroupADestructiveIdempotent
Update a group by ID. Admin accounts only. Send only fields to change; the current users are kept when users is not sent.
Inputs: id (required), name, type, users, +5 more.
updateNoteBDestructiveIdempotent
Update a note. Send only fields to change.
Inputs: id (required), body, isHtml, subject, +1 more.
updatePersonADestructiveIdempotent
Update a person. tags replaces all tags unless mergeTags=true; phones replaces all numbers. Custom fields: top-level 'custom*' keys; JSON null clears one. source/sourceUrl cannot be changed.
Inputs: id (required), tags, price, stage, +15 more.
updatePersonAttachmentBDestructiveIdempotent
Update a person attachment (externally hosted file). Needs registered-system credentials (X-System headers).
Inputs: id (required), uri (required), fileName (required), personId (required), +1 more.
updatePipelineADestructiveIdempotent
Update a pipeline and its stages (owner only). Stages with id are updated, without id are created.
Inputs: id (required), name, stages, description, +1 more.
updatePondADestructiveIdempotent
Update a pond by ID. If userIds is sent, send the COMPLETE member list; it replaces the existing one.
Inputs: id (required), name, userIds.
updateRelationshipADestructiveIdempotent
Update a relationship contact. emails/phones/addresses arrays OVERWRITE existing values (empty array = unchanged). personId cannot be changed.
Inputs: id (required), type, emails, phones, +3 more.
updateStageADestructiveIdempotent
Update a stage's name or position. Stages with isProtected=true cannot be renamed. FUB renumbers all stage weights in steps of 1000.
Inputs: id (required), name, orderWeight.
updateTaskBDestructiveIdempotent
Update a task. Mark done with isCompleted=true. dueDate is YYYY-MM-DD; use dueDateTime for a specific time.
Inputs: id (required), name, type, dueDate, +6 more.
updateTeamADestructiveIdempotent
Update a team by ID. If userIds or leaderIds is sent, send the COMPLETE list; it replaces the existing one.
Inputs: id (required), name, userIds, leaderIds, +1 more.
updateTemplateBDestructiveIdempotent
Update an email template. Merge fields work only in subject and body.
Inputs: id (required), body, name, subject, +1 more.
updateTextMessageTemplateCDestructiveIdempotent
Update a text message template. Message text goes in message.
Inputs: id (required), name, message, isShared.
updateWebhookADestructiveIdempotent
Update a webhook. url must be https. Account owner or registered system only.
Inputs: id (required), url, event.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 136 tools
The vast surface is still largely partitioned by resource+action, and descriptions actively steer between near-neighbors (getPersonByEmail vs listPeople, searchPeopleByTag vs listPeople, removeTagFromPerson vs updatePerson, bulkUpdatePeople vs updatePerson, templates vs text message templates vs email campaigns). A few genuine overlaps remain — checkDuplicate vs getPersonByEmail, listCustomFields vs listDealCustomFields vs listStages, and getReactions/getThreadedReplies that only fetch by ID while listing lives elsewhere — but on the whole an agent can pick correctly.
The dominant pattern is verb_noun camelCase (listPeople, createDeal, updateAppointment, getWebhook), applied across nearly all 136 tools. Deviations are minor: namespace-prefixed tools (inboxAppAddMessage, inboxAppInstall, listInboxAppInstallations), plural names for single-item getters (getReactions, getThreadedReplies), the Em abbreviation (listEmEvents, createEmCampaign), and non-verb utility tools (about, help).
136 tools is far past the point where a single agent can hold the surface in mind, even though the underlying Follow Up Boss CRM is genuinely sprawling (people, deals, pipelines, appointments, automations, inbox apps, teams, ponds, webhooks). Many resources contribute 4-5 near-identical CRUD variants, so the count is defensible in principle but overwhelming in practice; splitting or namespace-scoping would help considerably.
Coverage is unusually broad: CRUD across people, deals, tasks, appointments, notes, calls, pipelines, stages, groups, teams, ponds, webhooks, automations, action plans, custom fields, plus specialized lookups. Gaps are mostly deletions (no delete tools for any resource), missing list operations for attachments and reactions/threaded replies (only get-by-ID), and no update paths for people's source/sourceUrl, but these are largely upstream API limitations rather than oversights.
Maintenance
Related MCP Connectors
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
Search Follow Up Boss leads, review calls and deals, and add notes, tasks and deal updates.
LinkedIn outreach MCP server — 19 tools for AI agents to prospect, sequence, and manage contacts.
The HubSpot MCP Server acts as a bridge that enables AI assistants and Large Language Models to securely interact with HubSpot CRM data through natural conversation, without requiring users to understand complex API structures. It provides read-only access to standard CRM objects (contacts, companies, deals, tickets, products, invoices, and more) and their associations, secured via OAuth 2.0, allowing AI agents to perform tasks like summarizing deals, fetching company updates, and looking up record changes.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server for GoHighLevel API v2 that provides 50+ tools for CRM, billing, marketing, and operations workflows, enabling natural language interaction with contacts, opportunities, conversations, and more.501MIT
- 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 gradedqualityDmaintenanceAn MCP server for GoHighLevel with 82 live-tested tools, enabling CRM operations like contact management, appointments, invoices, and workflows via natural language.Creative Commons Attribution Non Commercial 4.0 International
- AlicenseCqualityBmaintenanceA comprehensive MCP server covering the full GoHighLevel API surface with 651 tools, enabling management of contacts, opportunities, calendars, invoices, and more through natural language, with multi-tenant support and read-only safety defaults.5001MIT