Skip to main content
Glama
geopopos

GoHighLevel MCP Server

by geopopos

Related Servers

Alternatives to GoHighLevel MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A production-grade MCP server that wraps the GoHighLevel API v2, enabling Claude and other MCP clients to interact with GHL CRM as structured tools for managing contacts, conversations, pipelines, appointments, payments, and more.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A comprehensive MCP server that connects AI assistants to GoHighLevel CRM, enabling management of contacts, conversations, calendars, pipelines, payments, and more through 60+ tools.
      64
      27 npm
      1
      MIT
    • 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
    • F
      license
      Not graded
      quality
      B
      maintenance
      Remote MCP server for GoHighLevel that enables multi-tenant agency access via OAuth, allowing Claude or ChatGPT to use GHL tools through natural language.
      -

    TDQS

    B3.1/5.0

    Scored across 21 tools

    Disambiguation4/5

    Tools are clearly grouped by resource (conversations, tasks, calendars), and each has a distinct action. The only minor overlap is between get_calendar_events and get_appointment, but descriptions clarify that one lists events by date range while the other fetches a specific appointment.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern in snake_case (e.g., create_conversation, update_task, delete_appointment). Minor deviations include pluralization differences (get_messages vs get_conversation) and the special case 'complete_task', but the overall convention is predictable.

    Tool Count3/5

    21 tools is on the heavier side, falling into the 'feels heavy' range (16-25). However, the count is justified by covering CRUD for three distinct domains (conversations, tasks, appointments), so it is not excessive.

    Completeness4/5

    The server provides full CRUD for conversations, tasks, and appointments, plus message retrieval and sending. Minor gaps exist such as no update/delete for messages and no management of calendars themselves, but these are not critical to the core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues