Skip to main content
Glama
vitrionbv

@vitrion/zentria-mcp

Official
by vitrionbv

Related Servers

Alternatives to @vitrion/zentria-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • 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
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI models to interact with Zoho CRM via Model Context Protocol, supporting CRUD operations, COQL queries, search, and deal stage management.
      -
    • 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.
      174 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to query, mutate, and analyze Salesforce CRM data natively through the Model Context Protocol, without requiring API glue code.
      7 npm
      3
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage a fully customizable CRM, including contacts, companies, sales pipelines, custom objects and fields, file uploads, and data relationships via MCP over HTTP.
      MIT

    TDQS

    B3.2/5.0

    Scored across 80 tools

    Disambiguation3/5

    Most tools are partitioned clearly by domain prefixes, but there are overlapping concepts such as sales people/contacts versus customer contacts, and STL leads versus CRM leads versus submissions. Descriptions and API paths help, but an agent could still easily select the wrong tool in those contact/lead/submission clusters.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern with domain prefixes for sub-resources. Special actions like move-deal-stage, change-member-role, and archive-customer still obey the same action-object convention, making the set highly predictable.

    Tool Count1/5

    80 tools is far beyond the recommended 3-15 range and even beyond the 25+ threshold, placing it in the 50+ extreme category. Even if each endpoint is legitimate for the underlying API, this is an overwhelming surface for an agent to navigate.

    Completeness3/5

    Several resources have full CRUD-like coverage, and the server spans many real domains. However, many entities lack delete operations, members have no removal tool, and STL/CRM leads and submissions have notable read-only or partial workflows, which creates lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues