Skip to main content
Glama
optimize-overseas

LACRM MCP Server

Related Servers

Alternatives to LACRM MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for Pipedrive CRM providing 88 tools for full CRUD on deals, persons, organizations, activities, and more, with custom field resolution and safety guards.
      88
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for Keap CRM, providing tools to manage contacts, tags, opportunities, notes, tasks, campaigns, and users via the Keap REST API v1.
      15
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that provides 36 tools for interacting with the amoCRM (Kommo) API v4, covering leads, contacts, companies, and tasks. It supports full entity lifecycles, account analytics, and bulk operations with integrated OAuth 2.0 and rate limiting.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for interacting with Keap CRM, enabling contact and tag management, batch operations, custom fields, and advanced query optimization.
      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
      39 npm
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 88 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but the sheer number of tools and overlapping retrieval patterns (e.g., get_pipeline_custom_fields vs get_custom_fields with pipeline filter, search_* vs get_*_attached_to_contact) create some potential for misselection. Descriptions are detailed enough to resolve most ambiguity.

    Naming Consistency4/5

    The naming convention is overwhelmingly consistent: snake_case verb_noun (create/edit/delete/get/search) with resource names. Minor deviations like the bulk_* prefix and compound suffixes (e.g., _attached_to_contact, _in_group) are predictable and readable, so the overall pattern is strong.

    Tool Count1/5

    With 88 tools, this is an extreme number for an MCP server, even considering the broad CRM domain. Many tools are convenience wrappers (e.g., get_X_attached_to_contact vs search_X) and schema/guide tools could be consolidated, making the surface feel bloated.

    Completeness4/5

    The tool set provides extensive CRUD coverage for contacts, companies, pipelines, statuses, notes, tasks, events, emails, groups, teams, custom fields, webhooks, and relationships. Notable minor gaps include no delete_file and no global file search, but core workflows are fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues