Skip to main content
Glama

Related Servers

Alternatives to Volkern MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with multiple CRM systems through a unified set of MCP tools, such as finding contacts, accounts, and deals, while supporting mock, REST, and vendor-specific backends.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Integrates WhatsApp with AI agents, enabling message sending, chat search, media sharing, approval workflows, and activity summaries via any MCP client.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables users to manage CRM leads, opportunities, projects, tasks, and sales records within ERPNext directly through MCP-compatible clients. It supports global searches, timesheet entries, and access to dashboard KPIs using natural language.
      -
    • 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

    TDQS

    B3.2/5.0

    Scored across 40 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific CRM/ERP resources and actions, with clear boundaries like create_contact vs. update_contact. However, some overlap exists: volkern_create_cita and volkern_update_cita could be confused with volkern_cita_accion (which handles confirm/cancel/reschedule), and volkern_create_lead's update behavior on duplicate email might blur with volkern_update_lead. Descriptions help clarify, but minor ambiguity remains.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case, using clear action verbs like create, get, list, update, send, and complete. The naming is highly predictable and readable across all 40 tools, with no deviations in style or convention, making it easy for agents to infer functionality.

    Tool Count2/5

    With 40 tools, the count feels excessive for a CRM/ERP server, likely leading to cognitive overload and reduced usability. While the domain is broad, many tools could be consolidated (e.g., separate list tools for each resource) or parameterized. This heavy toolset may overwhelm agents and slow down decision-making.

    Completeness5/5

    The toolset provides comprehensive coverage for CRM/ERP workflows, including full CRUD operations for leads, contacts, appointments, deals, contracts, and quotations, plus lifecycle actions like sending documents and logging interactions. No obvious gaps exist; agents can handle end-to-end processes from lead creation to contract signing and task management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues