LabscoMCP early access ↗
adamzhang1987MCP SERVER

Kingdee K3Cloud ERP

Query and operate a Kingdee K3Cloud ERP in plain language — stock, orders, approvals — without opening the web client.

by adamzhang1987 ↗ERP & Vertical Business SystemsCommunity

LABSCO SUMMARY

The generic form_id design is why this covers your ERP rather than a handful of hard-coded documents.

K3Cloud has hundreds of form types, and a server that named each one would always be missing yours; here one parameter selects the form and query_metadata tells the model what fields it has, so a document nobody anticipated still works. The high-level query primitives are the practical part — automatic paging, date sharding and streaming to file mean an export of a whole month does not become a loop the model has to drive and get wrong. Set the read-only mode unless you actually want approvals and deletions available; the write tools include audit, unaudit and delete.

What it is

A Python server over the Kingdee Cloud Cosmic (K3Cloud) Web API that exposes ERP documents through one generic form_id parameter, so the same tools work for materials, customers, sales orders and purchase orders alike.

What you get

  • query_bill and query_bill_json — a document query against any form, returned as structured data
  • query_bill_all — paging handled for you, so the model does not have to loop
  • query_bill_range — a query sharded by date, for periods too large for one call
  • query_bill_to_file — results streamed straight to a file, for exports that would not fit in a response
  • count_bill and query_metadata — how many records match, and what fields a form actually has
  • The write side: save_bill, submit_bill, audit_bill, unaudit_bill, delete_bill, push_bill and execute_operation
  • view_bill for a single document
  • A read-only mode that stops an assistant from changing anything
  • Automatic session recovery, so a long-running server survives K3Cloud session timeouts
  • Stdio locally, or SSE and streamable HTTP when the server is shared
  • Parameter validation on every tool before the call reaches Kingdee

Requirements

Five environment variables from your Kingdee instance — KD_SERVER_URL ending in /k3cloud/, KD_ACCT_ID, KD_USERNAME, KD_APP_ID and KD_APP_SEC — obtained by registering a third-party login authorization in the Kingdee admin console. The server exits at startup if any are missing. Python 3.10 or higher; installed with pip as kingdee-k3cloud-mcp or run with uvx. The repository recommends a dedicated integration user with only the module permissions it needs, rather than an administrator account.

Setup effort

One command plus credentials — uvx kingdee-k3cloud-mcp, then supply credentials

See installation options