Follow Up Boss MCP Server
Related Servers
Alternatives to Follow Up Boss MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA self-hosted MCP server that connects a Follow Up Boss CRM account to Claude, enabling CRM operations through natural language via 25 curated tools and a raw API tool.-
- FlicenseCqualityAmaintenanceMCP 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.13730-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for GoHighLevel with 82 live-tested tools, enabling CRM operations like contact management, appointments, invoices, and workflows via natural language.33 npmMIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server that connects AI assistants to GoHighLevel CRM, enabling management of contacts, conversations, calendars, pipelines, payments, and more through 60+ tools.6423 npm1MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP-native CRM backend for AI agents, enabling customer, opportunity, note, follow-up, and pipeline health management through 15 MCP tools.-
- AlicenseAqualityCmaintenanceMCP server that connects to a sales CRM database, enabling AI agents to search prospects, view pipeline status, manage follow-ups, and update records using natural language commands.574 npmISC
TDQS
Scored across 137 tools
Most tools have a clearly distinct resource+action target, but the sheer number creates some potentially confusing pairs (e.g., listEvents vs listEmEvents, listPeople vs searchPeopleByTag). Descriptions help resolve these, so ambiguity is limited.
The naming pattern is largely consistent: verb_noun with list<resources> for collections and get/create/update for individuals. A few exceptions like 'about', 'help', and 'checkDuplicate' deviate, but they are special-purpose tools and do not break the overall pattern.
With 137 tools, this server is extremely over-scoped. Even for a full CRM API, exposing every endpoint as an MCP tool is unwieldy and far exceeds the recommended 3-15 tool range.
The server covers a wide range of CRM resources with CRUD operations, but delete operations are notably absent for most resource types (people, deals, notes, etc.), creating dead ends that agents cannot work around.