Skip to main content
Glama

Related Servers

Alternatives to accelo-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage GoHighLevel CRM data including contacts, conversations, opportunities, calendars, and forms through MCP tools and resources.
      51
      AGPL 3.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to manage RogerRoger CRM data including people, organizations, lists, tags, and tasks through standardized MCP tools.
      22
      11
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read and write CRM data—companies, contacts, opportunities, tasks, and interactions—through MCP, with OAuth and provenance tracking for every value.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible LLMs to interact with the MOCO ERP API, providing full read/write access to time tracking, projects, invoices, contacts, and other endpoints.
      28
      ISC
    • A
      license
      C
      quality
      C
      maintenance
      Provides AI assistants with access to all public GoHighLevel API endpoints as MCP tools, enabling contact, conversation, opportunity, calendar, and other CRM operations with configurable safety gates for writes and deletes.
      55
      21
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to access and manage CiviCRM data, including contacts, activities, contributions, events, and memberships, with full custom field support.
      5
      MIT

    TDQS

    B3.2/5.0

    Scored across 219 tools

    Disambiguation4/5

    Most tools are clearly scoped to a resource and action, and the many list/count/get/create/update/delete tools are distinct. Some overlap exists in enumerations and filters, but the descriptions explicitly guide how to distinguish them. A few tools (e.g., accelo_list_enum vs accelo_list_object_filters) require careful reading but are not truly ambiguous.

    Naming Consistency5/5

    All tools follow a strict accelo_verb_noun pattern (e.g., accelo_list_companies, accelo_get_task, accelo_create_issue). The prefix is consistent and the verb+noun style is uniform across all 219 tools.

    Tool Count2/5

    With 219 tools, the surface is extremely large for any single agent to navigate effectively. While each tool may be warranted for the breadth of Accelo's API, the sheer count makes selection and maintenance burdensome, and the toolset feels heavy rather than well-scoped.

    Completeness4/5

    The server covers a vast domain with CRUD operations for most objects, plus helpers like progressions, timers, webhooks, and filters. Minor gaps exist (e.g., no contact delete), but overall the surface is remarkably comprehensive for Accelo's model.