Skip to main content
Glama
Weichie-com

teamleader-mcp

by Weichie-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to teamleader-mcp

No user-submitted related servers found.

    Related Servers

    • Twenty MCP Server

      iteramind
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to interact with Twenty CRM data through natural language, providing tools for managing contacts, companies, opportunities, tasks, and more via the Model Context Protocol.
      88 npm
      MIT

    • AI-Assisted CRM MCP Server

      MdJafirAshraf
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform CRM operations like creating contacts, managing deals, and updating leads through natural language using the Model Context Protocol.
      4
      -

    • Relatio CRM MCP Server

      charbelkassab
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage CRM prospects, activities, reminders, and mailbox via natural language commands through the Model Context Protocol.
      3
      MIT

    • aha-mcp

      sergiolopezgsiot
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language interaction with Home Assistant for managing entities, automations, services, and dashboards via the Model Context Protocol.
      173 npm
      MIT

    • HubSpot MCP Server

      adeel0x01
      A
      license
      B
      quality
      D
      maintenance
      Integrates with HubSpot CRM APIs via the Model Context Protocol, enabling management of contacts, companies, deals, tickets, notes, engagements, workflows, and more through natural language.
      82
      5 npm
      4
      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.3/5.0

    Scored across 42 tools

    Disambiguation5/5

    Each tool follows a clear resource+action naming pattern, making purposes distinct. Potential overlaps like deal_move vs deal_update are differentiated by specific semantics. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools use teamleader_<resource>_<action> consistently. List operations use plural resources while info operations use singular, a predictable pattern. Minor variation like add vs create is contextually appropriate.

    Tool Count2/5

    At 42 tools, the server is heavily oversized, far exceeding the 25+ threshold. Even for a full CRM integration, the number introduces significant context overhead and suggests a lack of consolidation.

    Completeness3/5

    Multiple core entities have missing CRUD operations: contacts lack create/update/delete, events lack update/delete, products lack delete. While many modules are covered, these gaps are notable and will require workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources