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
      C
      maintenance
      An MCP server for GoHighLevel with 82 live-tested tools, enabling CRM operations like contact management, appointments, invoices, and workflows via natural language.
      20 npm
      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
      20 npm
      1
      MIT

    • ghl-mcp

      craig248
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for GoHighLevel sub-accounts, enabling management of CRM contacts, pipelines, calendars, invoices, and more via natural language.
      -
    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.9/5.0

    Scored across 137 tools

    Disambiguation4/5

    Tools are mostly distinct, each targeting a specific resource and action (e.g., listGroups vs listTeams). However, the high volume and similar naming patterns (list/get/update for many entities) could cause confusion, especially between generic events (listEvents) and email marketing events (listEmEvents). Overall, descriptions clarify intent, but the sheer count adds ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb+resource camelCase convention (e.g., createDeal, getPerson, listAutomations). The only exceptions are 'about' and 'help', which are meta tools and don't break the pattern. This is highly predictable and aids navigation.

    Tool Count1/5

    With 137 tools, this is far beyond the typical coherent set. Even for a comprehensive CRM API, this volume is overwhelming and likely to cause decision fatigue and misselection. It exceeds the 50+ threshold for extreme mismatch, making the tool surface impractical for agents.

    Completeness2/5

    The tool surface covers many entities (people, deals, tasks, appointments, etc.) but lacks delete operations for nearly all core resources (no deletePerson, deleteDeal, deleteGroup, etc.). This creates dead ends where updates are possible but removals are not. Additionally, some actions like actually sending emails/texts are missing (only logging is supported), leaving notable gaps in workflow completion.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources