KingdeeMCP: an MCP server for Kingdee Cloud Star ERP
KingdeeMCP
A third-party MCP server with 101 tools for Kingdee Cloud Star ERP: purchasing, sales, stock, finance and attachments
- 138 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Tools create, approve and delete ERP documents with the specified user's rights
- The config holds the login and password of a working account
- Purchasing, sales and finance data go to the model
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/kingdeemcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Tools create, approve and delete ERP documents with the specified user's rights
- The config holds the login and password of a working account
- Purchasing, sales and finance data go to the model
This is third-party code. Review the repository files before installing.
What it does
The server connects Claude, Cursor, Windsurf, Cline and other MCP clients to Kingdee Cloud Star ERP (金蝶云星空). The assistant takes plain-language requests: find approved purchase orders for the month, create a sales order, post stock documents, export balances. The 101 tools fall into 17 areas: production, costing, assets, audit, purchasing, sales, stock, document attachments, finance, subcontracting and reports. Generic tools work with any document: save, submit, approve, unapprove, delete, push down the chain. Dynamic metadata queries suggest form fields so the assistant does not guess. Four tools read the structure of a SQL Server database. The server starts with `uvx kingdee-mcp` over stdio, as well as over SSE and Streamable HTTP, and a Docker image exists.
Who it is for. Kingdee Cloud Star implementers and developers who check ERP settings and data by conversation, and staff who need quick lookups of documents.
Good fit when
- During implementation you need to check document statuses and stock quickly without opening ERP menus
- You demo the system live to a customer: "show purchase orders" and the answer arrives at once
- You need to learn a form structure and its fields before writing your own integration code
- A batch of documents has to be submitted or approved without clicking each by hand
Not a fit when
- You run another ERP: the server works only with Kingdee Cloud Star
- The production database and user rights are unclear, while tools can delete and approve documents
- You need an official integration from the vendor: the project is third-party and not tied to Kingdee
Example request
Show this month's posted purchase orders with amounts and suppliers and flag those where the warehouse has not received the goods yet.MCP
- Transport
- stdio, sse, http
- Authentication
- API key
Environment variables
KINGDEE_SERVER_URLrequired- Kingdee server address ending in `/k3cloud/`.
KINGDEE_ACCT_IDrequired- Account set ID.
KINGDEE_USERNAMErequired- Login of the integration account.
KINGDEE_PASSWORDrequired, secret- Password of that account.
Limitations
The project is third-party, not tied to or endorsed by Kingdee. Login uses the user's name and password (ValidateUser) and carries that user's permissions, so the author advises a dedicated integration account, not Administrator. You need the server address with `/k3cloud/`, the account set ID, a login and a password.
The SQL Server reading tools need an ODBC driver and work best with a read-only account. Documentation and messages are in Chinese. The last commit is from October 2026.
How to disable. Remove the kingdee server from the client config, stop the container if one runs, and revoke or change the integration account password in Kingdee.
FAQ
How do I check that connection settings are right?
Run the image with the `--check` flag: `docker run --rm --env-file .env ghcr.io/wahailong/kingdeemcp:latest --check`. It logs in to Kingdee once and does not start the server.
Which environment variables are needed?
Four: `KINGDEE_SERVER_URL`, `KINGDEE_ACCT_ID`, `KINGDEE_USERNAME` and `KINGDEE_PASSWORD`. Database probing adds `MCP_SQLSERVER_HOST`, `MCP_SQLSERVER_DATABASE`, `MCP_SQLSERVER_USER` and `MCP_SQLSERVER_PASSWORD`.
Can the server run remotely?
Yes, `uvx kingdee-mcp --transport sse` or `--transport streamable-http` with `--host` and `--port`. The Kingdee login and password are still set through environment variables in this mode.
Is it dangerous to give it Administrator rights?
The author advises against it and recommends a dedicated account. The server acts with that user's rights, and the tools include deleting and approving documents.
How does password login differ from AppID login?
Login by name and password (ValidateUser) runs requests as a real user and respects that user's rights and data limits, while third-party login by AppID and AppSecret does not. That is why the current version has no `KINGDEE_APP_ID` or `KINGDEE_APP_SEC` variables.
Discussion
No questions or reviews yet.
Related
MCP serversThe Apideck MCP server: an agent works with over 200 business systems: accounting, HRIS, CRM and files through one unified API
An MCP server to drive FreeCAD from Claude Desktop and other clients: create and edit models, run scripts and FEM analysis
CDEK MCP: calculator and HTTP server
CDEK MCP Server
A CDEK API MCP server with a delivery calculator across all tariffs, courier booking and an HTTP mode for external agent platforms
Microsoft Power Platform MCP server with 312 tools for flows, apps, Dataverse and Power Pages, driven in plain language.
Official Cybozu MCP server: an agent reads and changes kintone apps, records and spaces through the REST API.
An MCP server for driving Windows: the agent opens apps, clicks and types, reads window and UI state, and works with files and PowerShell
README in short
The README explains why the server helps during implementation and daily work, lists clients, gives install through `uvx` and `pip`, SSE and HTTP modes, Docker and a variables table. It ends with the 101 tools by group and the switch from AppID to password login.