Skip to main content
Glama
Cyoda

Cyoda Calculation Node MCP

Official
by Cyoda

Related Servers

Alternatives to Cyoda Calculation Node MCP

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to access and manage Zentria CRM data, including sales, customers, to-dos, and more, through the Model Context Protocol.
      80
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to manage Prismatic integrations, components, and flows via the Model Context Protocol, supporting code-native integration development and component lifecycle.
      75 npm
      26
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI assistants with access to AegisX UI components, CRUD generator commands, development patterns, and API contract discovery tools. It enables developers to browse component documentation, build generation commands, and test authenticated API endpoints through the Model Context Protocol.
      25 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely interact with Fireblocks services through the Model Context Protocol, supporting transaction management, vault and exchange account queries, network connections, and workspace user management.
      21 npm
      10
      MIT

    TDQS

    B3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools are clearly distinct by functional domain (edge messages, entities, workflows). The potential confusion between 'search_find_all' and 'search_search' is mitigated by their descriptions indicating different query capabilities, but an agent might still misselect.

    Naming Consistency2/5

    Tool names follow inconsistent conventions: some use prefixes like 'edge_message_', 'entity_', 'workflow_mgmt_', while others use 'search_'. The naming mixes full words with abbreviations ('mgmt') and appends '_tool' inconsistently.

    Tool Count4/5

    13 tools is a reasonable count for a server covering edge messages, entity CRUD, and workflow management. It is slightly on the higher side but not excessive.

    Completeness3/5

    The entity management covers CRUD and two search options, which is good. Edge messages lack delete/update. Workflow management is file-based and lacks direct lifecycle operations like create or delete, leaving notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues