Skip to main content
Glama
jayson-svg

BackCrew GorillaDesk MCP Server

by jayson-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to BackCrew GorillaDesk MCP Server

No user-submitted related servers found.

    Related Servers

    • GoHighLevel API v2 MCP Server

      kbgphp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage GoHighLevel sub-account CRM data, including contacts, custom fields, tags, workflows, and calendar configurations through natural language.
      35 npm
      MIT

    • gorgias-mcp

      NoBanks
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage Gorgias support tickets: list open tickets, read conversation history, draft internal notes, send outbound replies (gated), and look up customer history.
      MIT

    • 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.
      35 npm
      MIT

    • Twenty CRM MCP Server

      mhenry3164
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Twenty CRM with AI assistants like Claude, enabling natural language interactions with customer data. Supports CRUD operations for people, companies, tasks, notes, and advanced search.
      11 npm
      104
      MIT

    • Planhat MCP

      da-troll
      A
      license
      B
      quality
      A
      maintenance
      Enables interacting with Planhat customer data via natural language, supporting CRUD operations on companies, contacts, opportunities, notes, conversations, users, assets, issues, tickets, tasks, licenses, and invoices.
      60
      MIT
    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

    B3.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: company info, user collection vs single user, customer collection vs create/update, customer notes, and phone type lookup. There is no meaningful overlap or ambiguity between tool purposes.

    Naming Consistency5/5

    All tool names follow a consistent lower_snake_case verb_noun pattern, such as list_users, get_user, create_customer, and add_customer_note. The naming clearly signals both the action and the resource, making the set predictable.

    Tool Count5/5

    Eight tools is a well-scoped size for this server's apparent focus on company, user, and customer data. Each tool has a clear purpose and none feel redundant or unnecessary.

    Completeness3/5

    The customer workflow has create, list, and update support but lacks a dedicated get-by-id and delete operation, leaving the customer lifecycle incomplete. Note management is also add-only, and users are read-only, so some common management workflows require external workarounds.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources