Skip to main content
Glama
ampware-io

GHL Workflow MCP

by ampware-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to GHL Workflow MCP

No user-submitted related servers found.

    Related Servers

    • GHL MCP Server

      mnewby20305
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to manage GoHighLevel CRM contacts, pipelines, and workflows through natural language commands.
      69 npm
      MIT

    • ghl-mcp-server

      yeisonmbotero
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to operate GoHighLevel features not exposed by the official API, including workflows, forms, custom fields, pipelines, and A2P 10DLC status, via GHL's internal web-app API.
      21
      MIT

    • GHL Command

      drjerryrelth
      A
      license
      A
      quality
      A
      maintenance
      GoHighLevel MCP server for Claude. 212 tools across 43 modules, including the only programmatic GHL workflow builder (private API, reverse-engineered), funnel + page editor, form builder, pipeline builder, pre-deploy validator, multi-sub-account switching, bulk operations, and full account export. $97 one-time, lifetime updates.
      4
      1
      MIT

    • GoHighLevel MCP Server

      mastanley13
      A
      license
      Not graded
      quality
      F
      maintenance
      Connects Claude Desktop to GoHighLevel CRM, providing 269+ tools across 19 categories for complete contact management, messaging, sales, marketing, e-commerce, and business operations through AI automation.
      13 npm
      194
      ISC
    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

    A3.7/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with descriptions explicitly guiding when to use which tool (e.g., get_workflow vs read_workflow_outline vs read_workflow_step, and update_workflow vs patch_workflow). The list_* tools are separated by entity type, and connection tools are unique. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., list_tags, create_workflow, read_workflow_step, patch_workflow). The few single-verb names like reconnect and launch_chrome are still clear and consistent with the overall style.

    Tool Count3/5

    With 30 tools, the set is heavy, but the server covers a broad GoHighLevel domain including many entity types needed for workflow construction. Each tool serves a distinct purpose, though some consolidation (e.g., a generic list tool with a type parameter) could reduce the count without losing functionality.

    Completeness4/5

    The server provides comprehensive CRUD and lifecycle coverage for workflows (create, read, update, delete, publish, clone, patch) and folders, plus all the list operations needed to reference GHL entities. Minor gaps exist, such as no update or delete for tags, but these are not critical for core workflow management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources