Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

by mindwear-capitian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to followupboss-mcp-server

No user-submitted related servers found.

    Related Servers

    • Follow Up Boss Connector

      thehillisrockin
      F
      license
      Not graded
      quality
      C
      maintenance
      A 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.
      -

    • CashClaw GHL MCP

      centrender
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for GoHighLevel with 82 live-tested tools, enabling CRM operations like contact management, appointments, invoices, and workflows via natural language.
      116 npm
      MIT

    • fub-mcp

      gray-wilbee
      A
      license
      C
      quality
      A
      maintenance
      Enables AI assistants to work with the Follow Up Boss real estate CRM API through 130+ tools for operations like people, notes, deals, and smart lists, while keeping the user's API key local and delete operations opt-in.
      133
      38 npm
      1
      MIT

    • ghl-mcp

      AustinMander
      A
      license
      B
      quality
      D
      maintenance
      MCP 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.
      50
      1
      MIT

    • ghl-mcp-server-v2

      zackscriven
      A
      license
      C
      quality
      C
      maintenance
      A 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.
      100
      116 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 136 tools

    Disambiguation3/5

    Most tools are clearly tied to a specific resource and action, but there are several overlapping boundaries: getPersonByEmail vs checkDuplicate, searchPeopleByTag vs listPeople with tags, and listEvents vs listEmEvents vs createEvent vs createEmEvent. The descriptions help disambiguate, but the set is large enough that misselection is a real risk.

    Naming Consistency4/5

    The server mostly follows a consistent camelCase verbNoun pattern: listX, createX, getX, updateX. Minor inconsistencies include listAutomationsPeople, about/help, and the abbreviated Em prefix, but these are understandable and do not seriously undermine predictability.

    Tool Count1/5

    At 136 tools, this is far beyond a well-scoped MCP surface. Even for a broad CRM API, the sheer volume creates a heavy selection burden for agents and dilutes the value of individual tools. A smaller, more curated set would be far more usable.

    Completeness3/5

    The server covers an impressively wide range of CRM entities: people, deals, appointments, tasks, pipelines, webhooks, templates, teams, and more. However, most entities lack delete/remove lifecycle operations, and some workflows are one-directional, such as logging text messages without sending them. The surface is broad but has notable lifecycle gaps.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources