Skip to main content
Glama
kingdee-k3cloud-mcp

kingdee-k3cloud-mcp

Related Servers

Alternatives to kingdee-k3cloud-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP server for Kingdee Cloud (K3Cloud) ERP that enables AI assistants to query and operate ERP data through natural language, supporting bills, metadata, and read/write operations.
      8
      2
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants such as Claude, Cursor, and Windsurf to query and operate Kingdee Cloud Star ERP in natural language, covering procurement, sales, inventory, finance, production, cost, assets, and approval workflows through MCP tools.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude, Cursor, and other MCP-compatible AI assistants to query and operate Kingdee Cloud Star ERP in natural language across purchasing, sales, inventory, finance, production, costs, assets, and audit workflows.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude, Cursor, and other AI assistants to query and operate Kingdee Cloud Star ERP in natural language through MCP tools. It supports purchasing, sales, inventory, finance, production, costs, assets, auditing, workflow, and metadata operations.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude, Cursor, and other AI assistants to query and operate Kingdee Cloud Star ERP—covering purchasing, sales, inventory, manufacturing, costing, fixed assets, financial reports, and approvals—using natural language through 87 MCP tools.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to interact with Odoo ERP, allowing natural language queries, record creation, updates, and deletions.
      LGPL 3.0

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation3/5

    The six query variants (query_bill, query_bill_json, query_bill_all, query_bill_to_file, query_bill_range, count_bill) overlap heavily; descriptions explain when to use each (format, paging, output destination), but an agent must read carefully to avoid picking the wrong one. execute_operation also overlaps with submit/audit/unaudit for Forbid/Enable actions.

    Naming Consistency5/5

    All 15 tools follow a consistent snake_case verb_noun pattern (save_bill, audit_bill, delete_bill, query_bill, view_bill, push_bill). The query_* family is prefixed consistently, making scanning predictable.

    Tool Count4/5

    15 tools is at the top of the ideal range and each cluster serves a real need (lifecycle ops, query modes, metadata). The query family is somewhat bloated at six tools, but each targets a distinct scale/format use case.

    Completeness4/5

    Bill lifecycle is well covered: save (create/update), submit, audit, unaudit, delete, push-down, plus rich query and metadata inspection. Minor gaps exist—no tool to list/discover available form_ids or bill types, and no draft/withdraw or attachment handling.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data