WaHaiLong/KingdeeMCP

Kingdee Cloud Star MCP Server: lets AI assistants such as Claude/Cursor directly query and operate ERP systems in natural language (97 tools covering procurement, sales, inventory, finance, and more)

This repository also configures its own agents. See what KingdeeMCP tells them →

114Stars on the repository
8Mods indexed here, across every type
2mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

kingdee-doc-release

01

WaHaiLong/KingdeeMCP

Agent Claude Code

Docs & Release Engineer for the kingdee-mcp project. Maintains docs/ and mcpoptimizationnotes.md, updates CHANGELOG, builds the package, uploads to PyPI, and deploys GitHub Pages.

not rated 114 +4 2mo ago A 49 tokens original MIT

WaHaiLong/KingdeeMCP

Agent Claude Code

Lead of the Kingdee MCP Dev Squad. Coordinates WebAPI integration, MCP tool implementation, QA and PyPI release to fully cover the Kingdee OpenAPI (ApiDoc) interfaces inside kingdee-mcp.

not rated 114 +4 2mo ago A 51 tokens original MIT

WaHaiLong/KingdeeMCP

Agent Claude Code

MCP Tool Developer for the kingdee-mcp project. Implements @mcp.tool endpoints from WebAPI field mappings, maintains validateandfix / findsimilarfield logic, and reuses the speed-up tools (validatebill / getbilltemplate / refreshmetadata).

not rated 114 +4 2mo ago A 60 tokens original MIT

kingdee-qa-engineer

04

WaHaiLong/KingdeeMCP

Agent Claude Code

QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.

not rated 114 +4 2mo ago A 49 tokens original MIT

WaHaiLong/KingdeeMCP

Agent Claude Code

Kingdee WebAPI integration engineer for the kingdee-mcp project. Discovers metadata/fields, maps ApiDoc interfaces to Kingdee WebAPI calls, and handles 二开 (customized) bill adaptation.

not rated 114 +4 2mo ago A 49 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: