Kingdee K3Cloud (Cloud Galaxy) ERP

Q: How do I install the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server?

Kingdee K3Cloud (Cloud Galaxy) ERP runs locally as a PyPI package, launched with uvx kingdee-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

Q: What is the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server?

Kingdee K3Cloud (Cloud Galaxy) ERP is an MCP server listed in the public MCP registry as io.github.WaHaiLong/kingdee-mcp. Third-party open-source MCP server for Kingdee K3Cloud ERP - 101 tools, 17 domains. Unofficial. This page covers its PyPI package (kingdee-mcp).

Q: Is the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server safe to use?

Kingdee K3Cloud (Cloud Galaxy) ERP scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Q: What tools does the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server expose?

Kingdee K3Cloud (Cloud Galaxy) ERP exposes 101 tools: kingdee_usage_report, kingdee_usage_stats, kingdee_discover_tables, kingdee_discover_columns, kingdee_describe_table, and 96 more. Their descriptions and schemas cost roughly 16,856 tokens of context every time the server is loaded.

Q: Is the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server still maintained?

Kingdee K3Cloud (Cloud Galaxy) ERP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

Q: What licence is the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server under?

Kingdee K3Cloud (Cloud Galaxy) ERP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

PYPI · KINGDEE-MCP

Third-party open-source MCP server for Kingdee K3Cloud ERP - 101 tools, 17 domains. Unofficial.

Available components

pypi · kingdee-mcp 71

+4 this week 71 71 Trust /100

Last scanned 4 Nov 2026 (1 day ago)

Scores higher than 67% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100

No malware found by supply-chain analysis.Pass
No known CVEs affecting this package version or its production dependencies.Pass
Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 9 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability72

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 16895 tokens (~164/item across 103 items; 101 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management33

Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage71

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
0% of tool parameters carry a description.Fail
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Tool Safety82

No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
2 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "kingdee_query_asset_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
An AI judge read all 102 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Nov 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
1 Nov 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
30 Oct 26 +16
- Malware scan: unverified → pass ▲ security
29 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
25 Oct 26 67

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed pypi/kingdee-mcp@0.2.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result	No attestation
Ecosystem	pypi
Reason	No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script

Hook	Tier	Command
build_backend	allowlisted	`hatchling.build`

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages

Packages resolved	29
Tree resolution	Complete

Background: SBOMs and build attestations, explained →

MCP tools · 101 exposed · ~16,856 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens

kingdee_audit_bills ~63

审核单据（待审核 → 已审核）。返回结构化结果：success=true 时表示单据已生效，next_action=null。 Returns: str: JSON，含 success / bill_ids 字段

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_audit_production_orders ~42

审核生产订单（PRD_MO）。 Returns: str: JSON，含 success / bill_ids

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_cancel_bills ~328

撤销单据或基础资料（草稿/审批中状态回退，action=CancelAssign）。 - FormId 参数化通用工具（非某单专用，理由：撤销是标准动作应走通用工具防重复），适用于单据 + 基础资料（如 SAL_SaleOrder / PUR_Requisition / BD_Customer / BD_Material 等）。 - action 依据：范探源 2026-08-07 三重证据查证（元数据 OperationNumber + OperationNumberConst.cs 反编译 + 官方论坛/第三方实测），撤销 = CancelAssign （旧文档误作 Cancel，勿引用）。 - 端点：默认走**独立 CancelAssign 端点**（无需 opNumber，QA 严过关 2026-08-07 真机验证 B→D 成功），data={"Ids":"1,2,3"} 或 {"Numbers":[...]}，比走 ExecuteOperation 更简单直接。 - 传参：bill_ids（FID 列表，优先）或 bill_nos（单据编号列表），至少一个。 - 二开单据自定义撤销动作时，可显式传 operation 覆盖默认 CancelAssign（此时走 ExecuteOperation + 顶层 opNumber）。 Returns: str: JSON，含 success / fid / ids / action / endpoint 字段（注意是 fid/ids 而非 id）

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_close_bill ~320

整单关闭单据（已审核单据业务关闭，opNumber 随表单而异）。 - FormId 参数化通用工具（非某单专用，理由：整单关闭是标准动作应走通用工具防重复），适用于单据（销售订单、采购申请单、发货通知单等）。 - action 依据：范探源 2026-08-07 三重证据查证 + QA 严过关真机实测——整单关闭 opNumber 因表单而异（如 SAL_SaleOrder=YLBillClose、PUR_Requisition=BillClose、 PUR_PurchaseOrder=BillClose、SAL_DELIVERYNOTICE=BillClose），无法静态固定，需真机确认。 - 端点/格式：ExecuteOperation，opNumber 放顶层，data 只放业务参数。 - 解析优先级：显式 operation 参数 > 该 form_id 元数据 Operations 按中文名「整单关闭/关闭单据」匹配 OperationNumber（复用元数据缓存 _query_metadata）；匹配不到返回明确中文错误（提示显式传 operation）。 - 传参：bill_ids（FID 列表，优先）或 bill_nos（单据编号列表），至少一个。 Returns: str: JSON，含 success / fid / ids / action / action_source / endpoint 字段

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_create_and_audit ~199

一次性走完 Save → Submit → Audit 三步，避免 AI 漏掉中间步骤。任意一步失败即停止（不自动重试），返回 halted_at 和 recovery_hint 告诉 AI 从哪里手动接手。失败日志按整体 op="create_and_audit" 记录一次（不会三倍膨胀）。适用场景：明确要"一条龙"创建并使单据生效，没有中间审批/校验需求。需要中间步骤校验时，请改用手工链路 kingdee_save_bill → kingdee_submit_bills → kingdee_audit_bills。 Returns: str: JSON。成功：success=true、halted_at=null、steps 三条均 success。失败：success=false、halted_at 指出卡点、recovery_hint 给出下一步建议。

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_create_lx_billing ~251

二开收款单(TRNV_Receipt)/付款单(TRNV_PaymentSlip) 一站式创建：push → save 补字段 → submit → audit。背景：金蝶 WebAPI push 接口对二开收/付款单 **不会携带业务字段**（金额、物料、SONo 等全为空/0），必须在 push 后用 save 把字段补上才能进入审核。本工具把这四步合并，专为账套初始化导在途收/付款数据设计。工作流： 1. push: 源单(SAL_SaleOrder/PUR_PurchaseOrder) → 草稿目标单（保留 _LK 上下游关联） 2. save: 把 amount / material / qty / so_no 等业务字段写入草稿（is_delete_entry=false 不破坏 _LK） 3. submit + audit（auto_audit=True 时）任一步失败立即停止，返回 halted_at 和 recovery_hint 指引手工接手。 Returns: str: JSON。含 steps、target_bill_no、target_fid、halted_at / recovery_hint。

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_delete_bills ~67

删除单据（仅草稿状态可删除，已提交/已审核的单据需先反审核）。返回结构化结果：success=true 时表示删除成功。 Returns: str: JSON，含 success / bill_ids 字段

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_describe_table ~185

查看指定表的完整结构（列名、类型、可空、默认值）。适用场景： - 知道表名，想了解完整字段列表 - 写 SQL 或做数据建模前，查看表结构 - 确认 Kingdee API 返回的字段在数据库里的实际类型已知金蝶常用表名前缀： - t_PUR_：采购相关（t_PUR_PurchaseOrder 采购订单） - t_SAL_：销售相关（t_SAL_SaleOrder 销售订单） - t_STK_：库存相关（t_STK_InStock 入库单） - t_BD_：基础资料（t_BD_Material 物料、t_BD_Supplier 供应商） Returns: str: 表结构详情

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_discover_columns ~116

按关键字搜索 SQL Server 中的列名（仅查系统目录，不读业务数据）。适用场景： - 想找一个"供应商编码"字段在哪些表里 - 接口映射时，确认某个字段在数据库里的实际名称 - 快速验证 Kingdee API 字段和数据库字段的对应关系 Returns: str: 列名搜索结果，含表名、列名、数据类型、是否可空

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_discover_metadata_candidates ~243

发现金蝶数据库中与指定 form_id 或 form_id 前缀对应的表。这是面向金蝶/K3 场景的辅助工具：根据 form_id 推测对应的数据库表名。 form_id → 表名对应规律： - PUR_PurchaseOrder → t_PUR_PurchaseOrder（采购订单） - SAL_SaleOrder → t_SAL_SaleOrder（销售订单） - STK_InStock → t_STK_InStock（入库单） - BD_Material → t_BD_Material（物料） - BD_Supplier → t_BD_Supplier（供应商） - BD_Customer → t_BD_Customer（客户）适用场景： - 想知道某个 form_id 对应数据库里哪张表 - 想探索某类单据的所有关联表（如采购全流程：订单→收料→入库） - 理解金蝶 form_id 和数据库表名的映射关系 Returns: str: form_id 与表名的候选映射列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_discover_tables ~123

搜索 SQL Server 中包含关键字的表名（仅查系统目录，不读业务数据）。适用场景： - 想知道"采购"相关的表有哪些 - 快速定位业务表名，不记得确切名称时 - 配合 kingdee_discover_columns 一起使用，先找表再看字段搜索范围：SQL Server 系统目录（information_schema.TABLES / sys.tables） Returns: str: 表名列表，含表名、类型、创建时间

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_download_attachment ~106

按 WebAPI V6.0 下载一块附件，返回 Base64 file_part，不写服务器本地文件。 file_id 使用上传返回的 FileId，不是附件内码 attachment_ids。首次 start_index=0；is_last=false 时用返回的 start_index 继续下载，直到 next_action=null。每块分别 Base64 解码后按顺序拼接字节，不要直接拼接 Base64 字符串。

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_enable_bills ~237

反禁用基础资料（opNumber=Enable）。 - FormId 参数化通用工具（非某单专用，理由：反禁用是标准动作应走通用工具防重复），仅适用于基础资料（如 BD_Customer / BD_Supplier / BD_Material / BD_Stock 等）。 - action 依据：范探源 2026-08-07 三重证据查证 + QA 严过关真机实测——反禁用 = Enable。 - 端点/格式：ExecuteOperation，opNumber=Enable 放**顶层**，data 只放业务参数。 - 传参：bill_ids（FID 列表，优先）或 bill_nos（编号列表，基础资料用 FNumber），至少一个。 - 二开基础资料自定义反禁用动作时，可显式传 operation 覆盖默认 Enable。 Returns: str: JSON，含 success / fid / ids / action / endpoint 字段（注意是 fid/ids 而非 id）

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_forbid_bills ~268

禁用基础资料（opNumber=Forbid，非 UnForbid；Disable 已废弃慎用）。 - FormId 参数化通用工具（非某单专用，理由：禁用是标准动作应走通用工具防重复），仅适用于基础资料（如 BD_Customer / BD_Supplier / BD_Material / BD_Stock 等）。 - action 依据：范探源 2026-08-07 三重证据查证 + QA 严过关真机实测——禁用 = Forbid， Disable 已废弃慎用，勿用 UnForbid（无此常量）。 - 端点/格式：ExecuteOperation，opNumber=Forbid 放**顶层**，data 只放业务参数。 - 传参：bill_ids（FID 列表，优先）或 bill_nos（编号列表，基础资料用 FNumber），至少一个。 - 二开基础资料自定义禁用动作时，可显式传 operation 覆盖默认 Forbid。 Returns: str: JSON，含 success / fid / ids / action / endpoint 字段（注意是 fid/ids 而非 id）

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_get_bill_template ~135

获取常用单据的「已验证 model 骨架」模板（销售报价单/销售订单/采购订单等）。返回该表单的正确字段名、必填项、分录必填字段组成的 model 示例，AI 只需替换占位符填业务数据，跳过字段摸索。占位符形如 <客户编码>。保存前建议再用 kingdee_validate_bill 校验。支持的 form_id：SAL_Quotation / SAL_SaleOrder / PUR_PurchaseOrder（其它表单返回提示）。

Input Output Examples

Name	Type	Req	Description
form_id	string	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_get_fields ~231

获取指定表单的完整字段信息和业务规则。不知道查询哪些字段时，或需要了解表单的业务限制时，先调用此工具。本工具会调用金蝶 QueryBusinessInfo 接口拉取真实字段定义（带缓存）。返回内容： - name/desc/db_tables/business_rules: 来自本地表单目录 - recommended_fields: 推荐查询字段（精简版，给 LLM 看的） - metadata.fields: 所有主表字段（含 caption/type/must） - metadata.entries: 所有分录子表及其字段 - metadata.required_fields: 主表必填字段列表 - save_template: 自动生成的最小可保存 model 骨架（仅含必填字段）字段格式说明： - FXxx 是普通字段 - FXxx.FName 是关联字段取名称（例：FSupplierId.FName） - FXxx.FNumber 是关联字段取编码（例：FSupplierId.FNumber） Returns: str: JSON 格式的字段信息

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_list_forms ~105

搜索金蝶系统中可用的表单类型（form_id）。不知道 form_id 时，先调用此工具搜索。例如： - 输入"员工"返回 BD_Empinfo - 输入"采购"返回采购相关的表单列表 - 留空返回所有常用表单 Returns: str: JSON 格式的表单列表，含 form_id、名称、描述、推荐字段、数据库表名

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_push_and_audit ~133

一次性走完 Push → (可选 Submit + Audit) 全流程。 Push 生成的目标单默认是草稿；本工具自动批量提交+审核所有生成的目标单 FID。任何一步失败即停止；失败日志按整体 op="push_and_audit" 记录一次。 auto_submit_audit=False 时退化为纯 push（与 kingdee_push_bill 等价，但返回 steps 结构）。 Returns: str: JSON。含 steps、target_bill_nos、target_fids、halted_at / recovery_hint。

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_push_bill ~448

将源单据下推生成目标单据（如销售订单下推销售出库单、采购订单下推采购入库单）。常用下推场景： - 销售订单 → 销售出库单: form_id=SAL_SaleOrder, target_form_id=SAL_OUTSTOCK - 采购订单 → 采购入库单: form_id=PUR_PurchaseOrder, target_form_id=STK_InStock - 采购订单 → 收料通知单: form_id=PUR_PurchaseOrder, target_form_id=PUR_ReceiveBill - 销售订单 → 销售退货单: form_id=SAL_SaleOrder, target_form_id=SAL_RETURNSTOCK 转换规则说明： - 默认（rule_id=空，enable_default_rule=false）：Kingdee 使用系统配置的默认转换规则 - enable_default_rule=true：强制启用该单据的默认下推规则，忽略 rule_id - rule_id 显式指定：绕过默认规则，直接使用指定规则（下推失败时常用此方式）采购订单下推限制（关联数量规则）： - 采购订单【关联数量】>=【订单数量】时，无法下推收料单/入库单（关联数量 = 累计收料数量 + 累计入库数量） - 勾选【控制交货数量】时： - 关联数量 >= 交货下限时，无法下推 - 关联数量 + 本次下推数量 > 交货上限时，目标单据无法保存 - 单据状态必须为"已审核"，且未关闭、业务状态为"正常" 响应包含： - Result.ResponseStatus：保存结果（IsSuccess 判断整体是否成功） - Result.ConvertResponseStatus：每行下推转换结果（可查看具体分录成功/失败） Returns: str: JSON，含 success / bill_nos / next_action 字段（成功时包含目标单据编号）

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_push_production_pick ~53

从生产订单下推生成生产领料单（PRD_PickMtrl）。 Returns: str: JSON，含 success / target_bill_nos / next_action

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_push_production_stock_in ~55

从生产领料单下推生成生产入库单（PRD_Instock）。 Returns: str: JSON，含 success / target_bill_nos / next_action

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_push_stock_transfer ~218

从调拨申请单下推到直接调拨单（STK_TransferApply -> STK_TransferDirect）。用于将调拨申请单下推生成直接调拨单，一步完成调拨。参数说明： - form_id: 固定为 STK_TransferApply（调拨申请单） - target_form_id: 固定为 STK_TransferDirect（直接调拨单） - source_bill_nos: 调拨申请单的单据编号列表转换规则说明： - 默认（rule_id=空）：使用系统配置的默认转换规则 - enable_default_rule=true：强制启用默认下推规则 - rule_id 显式指定：绕过默认规则，使用指定规则响应包含： - Result.ResponseStatus：保存结果（IsSuccess 判断整体是否成功） - Result.ConvertResponseStatus：每行下推转换结果 Returns: str: JSON，含 success / bill_nos / next_action 字段

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_approval_flow ~184

查询金蝶云星空的审批流程记录。记录单据从提交到最终审核的完整审批轨迹，包括每个节点的审批人、时间、结果和意见。用于审批追溯、流程优化、合规检查。推荐场景： - 审批追溯：某张单据走过了哪些审批节点 - 流程优化：分析审批时长和瓶颈 - 合规检查：确认关键单据是否按流程审批注意：金蝶审批流程数据可能存储在多个表单中，如 V_SFA_ApprovalRecord（审批记录）、Workflow_Instance（流程实例）等。如查询无结果，请用 kingdee_get_fields 查看实际可用字段。 Returns: str: JSON 格式的审批流程列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_asset_card ~152

查询资产卡片（FA_FAGet 或子单据）。资产卡片是固定资产的详细记录，包含原值、累计折旧、净值、卡片状态等信息。常用 filter_string： - 指定资产编号: "FNumber='FA001'" - 指定保管人: "FCustodian.FNumber='EMP001'" - 已计提折旧: "FTotalDepreciate>0" 推荐 field_keys： FID,FNumber,FName,FAssetSource,FOriginalAmount,FTotalDepreciate,FNetAmount,FDepreciateMonth,FUsefulLife,FSalvageValue,FCustodian.FName

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_asset_depreciation ~142

查询资产折旧记录（FA_DepreciationBill）。折旧记录是固定资产计提折旧的明细，反映每月折旧费用、累计折旧、净值变化。常用 filter_string： - 指定期间: "FYear=2024 and FPeriod=3" - 指定资产: "FAssetId.FNumber='FA001'" 推荐 field_keys： FID,FYear,FPeriod,FAssetId.FNumber,FAssetId.FName,FDepreciateDeptId.FName,FDepreciateAmount,FOriginalAmount,FTotalDepreciate,FNetAmount

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_asset_scrape ~143

查询资产报废单（FA_Scrape）。资产报废记录固定资产的处置，包括正常报废、提前报废、毁损等。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定资产: "FAssetId.FNumber='FA001'" - 报废类型: "FScrapeType='NORMAL'" 推荐 field_keys： FID,FBillNo,FScrapeDate,FDocumentStatus,FAssetId.FNumber,FAssetId.FName,FOriginalAmount,FTotalDepreciate,FNetAmount,FScrapeType,FHandleMethod

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_asset_transfer ~131

查询资产调拨单（FA_Transfer）。资产调拨记录固定资产在部门或使用人之间的转移。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定资产: "FAssetId.FNumber='FA001'" - 原使用部门: "FOldDeptId.FNumber='D001'" 推荐 field_keys： FID,FBillNo,FTransferDate,FDocumentStatus,FAssetId.FNumber,FAssetId.FName,FOldDeptId.FName,FNewDeptId.FName,FTransferReason

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_audit_log ~214

查询金蝶云星空的审计日志（BOS_AuditLog）。记录单据的审核操作：谁在什么时候审核了哪张单据、审核结果是什么。用于合规审计、审批追溯、反舞弊检查。推荐场景： - 合规要求：保留所有审核操作的审计轨迹 - 问题排查：某张单据的审核历史 - 责任追溯：谁在什么时间通过了/驳回了审批返回字段说明： - FCREATEDATE: 审核时间 - FCREATORID: 审核人 - FOBJECTID: 单据内码 - FFORMID: 单据类型 - FAUDITRESULT: 审核结果（通过/驳回/取消） - FMEMO: 审核意见 Returns: str: JSON 格式的审计日志列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_bills ~203

查询金蝶云星空任意单据列表，支持过滤、排序和分页。适用 form_id 示例：PUR_PurchaseOrder（采购订单）、SAL_SaleOrder（销售订单）、 STK_InStock（采购入库）、SAL_OUTSTOCK（销售出库）、STK_MisDelivery（其他出库）。也可查基础资料：BD_Currency（币别）、BD_AccountBook（账簿）、 BD_VOUCHERGROUP（凭证字）、BD_RateType（汇率类型）等。这类表单的查询视图没有 FID 列，工具会自动去掉 FID 字段与 FID 排序，无需调用方特殊处理（#28）。 Returns: str: JSON，含 form_id / count / has_more / data 字段；发生自动降级时额外带 notice 字段说明

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_change_log ~197

查询金蝶云星空的单据变更记录（BOS_ModifyLog）。记录单据字段的修改历史：谁在什么时候修改了什么字段、从什么值改成了什么值。用于数据变更追溯、合规审计、问题排查。推荐场景： - 数据治理：追踪关键字段的变更历史 - 问题排查：某张单据的修改记录 - 合规要求：保留重要数据的修改轨迹返回字段说明： - FCREATEDATE: 修改时间 - FCREATORID: 修改人 - FOBJECTID: 单据内码 - FFIELDNAME: 字段名称 - FOLDVALUE: 修改前的值 - FNEWVALUE: 修改后的值 Returns: str: JSON 格式的变更记录列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_cost_adjustments ~105

查询成本调整单（STK_CostAdjust）。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定调整类型: "FAdjustType='1'" 推荐 field_keys： FBillNo,FDate,FDocumentStatus,FCostOrgId.FNumber,FCostOrgId.FName,FAdjustType,FAdjustAmount Returns: str: JSON 格式的成本调整单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_cost_calculation ~120

查询成本计算单（CB_CostCalBill）列表。常用 filter_string： - 指定年度: "FYear=2024" - 指定期间: "FPeriod='01'" - 指定物料: "FMaterialId.FNumber='MAT001'" 推荐 field_keys： FYear,FPeriod,FMaterialId.FNumber,FMaterialId.FName,FCostAmt,FMaterialCost,FLabourCost Returns: str: JSON 格式的成本计算单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_cost_centers ~90

查询成本中心基础资料（CB_CostCenter）。常用 filter_string： - 指定编码: "FNumber like 'CC%'" - 启用状态: "FIsActive='1'" 推荐 field_keys： FNumber,FName,FDeptId.FName,FIsActive Returns: str: JSON 格式的成本中心列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_cost_items ~90

查询成本项目基础资料（CB_CostItem）。常用 filter_string： - 指定编码: "FNumber like 'CI%'" - 成本项目类型: "FCostItemType='1'" 推荐 field_keys： FNumber,FName,FCostItemType,FIsActive Returns: str: JSON 格式的成本项目列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_cost_trend ~129

查询成本价趋势分析表（STK_CostTrend）。分析物料成本价格的变化趋势。常用 filter_string： - 指定物料: "FMaterialId.FNumber='MAT001'" - 指定日期范围: "FDate>='2024-01-01' and FDate<='2024-12-31'" 推荐 field_keys： FMaterialId.FNumber,FMaterialId.FName,FDate,FCostPrice,FPriceChange Returns: str: JSON 格式的成本价趋势列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_data_backup ~162

查询金蝶云星空的数据备份记录。记录系统的数据备份和恢复操作。用于灾备验证、合规检查、恢复演练。推荐场景： - 灾备验证：确认备份是否按计划执行 - 合规要求：保留备份操作的审计轨迹 - 恢复演练：查找可用的备份点注意：金蝶备份数据可能存储在系统配置表或其他后台表单中，如需访问请确认当前用户有系统管理权限。如查询无结果，请用 kingdee_get_fields 查看实际可用字段。 Returns: str: JSON 格式的数据备份记录列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_delivery_notice ~325

查询发货通知单。对应金蝶 ApiDoc 销售管理域「发货通知」模块，FormId: SAL_DELIVERYNOTICE。用于查询待发货/已发货通知单及其客户信息，支持按客户、日期、单据状态筛选。 ⚠️ 字段 Key 警示（真机实测，范探源已验证）：本账套客户字段的元数据 Key 是 **FCustomerID**（大写 ID 后缀）。误用 FCustId 会报「元数据中标识为FCustId的字段不存在」——本环境的 FCustId 在元数据中不存在，切勿改回 FCustId。字段 Key 一律以 kingdee_get_fields 元数据为准。 ⚠️ 动作范围说明：标准保存/提交/审核动作已由通用 kingdee_save_bill / kingdee_submit_bills / kingdee_audit_bills 等按 FormId 参数化覆盖，本工具仅做查询，不负责写操作。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定客户: "FCustomerID.FNumber='C001'" - 日期区间: "FDate>='2026-05-01' and FDate<='2026-05-31'" 推荐 field_keys（已按本环境元数据校验可用）： FID,FBillNo,FDate,FDocumentStatus,FCustomerID.FName

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_expense_reimburse ~59

查询费用报销单。专门用于查询费用报销单据，支持按状态、金额、日期筛选。 Returns: str: JSON 格式的费用报销单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_finished_product_cost ~116

查询完工入库产品成本（CB_FinishInCostQuery）。常用 filter_string： - 指定生产订单: "FMoBillNo='MO000001'" - 指定期间: "FYear=2024 and FPeriod='01'" 推荐 field_keys： FMoBillNo,FMaterialId.FNumber,FMaterialId.FName,FFinishQty,FCostPrice,FCostAmt Returns: str: JSON 格式的完工成本列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_fixed_asset ~169

查询固定资产卡片主数据（FA_FAGet / BD_MainData，formId: FA）。固定资产是企业长期使用的有形资产，如房屋、机器设备、运输工具等。支持按资产编号、名称、状态、使用部门等条件筛选。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定资产编号: "FNumber='FA001'" - 指定使用部门: "FUseDeptId.FNumber='D001'" - 在用资产: "FStatus='USING'" 推荐 field_keys： FID,FNumber,FName,FAssetSource,FSpecification,FUsedPeriod,FOriginalAmount,FDepreciateRate,FUseDeptId.FName,FDocumentStatus,FStatus

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_instant_cost_compare ~129

查询即时成本对比分析表（STK_InstantCostCompare）。对比即时成本与核算成本的差异。常用 filter_string： - 指定物料: "FMaterialId.FNumber='MAT001'" - 指定仓库: "FStockId.FNumber='WH01'" 推荐 field_keys： FMaterialId.FNumber,FMaterialId.FName,FStockId.FName,FInstantCost,F核算成本,FDiffAmt Returns: str: JSON 格式的即时成本对比列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_inventory ~105

查询即时库存数量（STK_Inventory）。常用 filter_string： - 指定物料: "FMaterialId.FNumber='MAT001'" - 指定仓库: "FStockId.FNumber='WH01'" - 有库存: "FBaseQty>0"（默认已设置） Returns: str: JSON 格式的库存列表，含物料编码、名称、仓库、数量、单位

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_loan_balance ~212

查询历史借款余额（人人报销域）。对应金蝶 ApiDoc「人人报销 → 历史借款余额」模块，FormId: ER_HistoricalLoanBalance。用于查询员工/部门的借款余额快照，支持按状态、申请人、日期筛选。 ⚠️ 环境注意：该单据在部分账套（如芯之蝶测试账套 <ACCT_ID>）未启用， kingdee_get_fields 会返回「未知表单」。本工具代码已就绪，待目标账套启用该模块后即可连真机使用；字段 Key 以金蝶标准元数据为准，若实测报「字段不存在」请先用 kingdee_get_fields 复核。推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FApplicantId.FName,FEmployeeId.FName,FLoanAmount,FRepaidAmount,FUnRepayAmount

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_material_cost ~125

查询物料成本库（BD_MaterialCost）。返回物料的标准成本、最新成本、平均成本等信息。常用 filter_string： - 指定物料: "FMaterialId.FNumber='MAT001'" - 指定成本组织: "FCostOrgId.FNumber='100'" 推荐 field_keys： FMaterialId.FNumber,FMaterialId.FName,FUnitId.FName,FStdCost,FLatestCost,FAvgCost Returns: str: JSON 格式的物料成本列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_material_cost_usage ~113

查询生产材料耗用成本（CB_MaterialCostQuery）。常用 filter_string： - 指定生产订单: "FMoBillNo='MO000001'" - 指定物料: "FMaterialId.FNumber='MAT001'" 推荐 field_keys： FMoBillNo,FMaterialId.FNumber,FMaterialId.FName,FConsumeQty,FCostPrice,FCostAmt Returns: str: JSON 格式的材料耗用成本列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_material_target_cost ~104

查询物料目标成本单（BD_MatTargetCost）。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定物料: "FMaterialId.FNumber='MAT001'" 推荐 field_keys： FBillNo,FDate,FDocumentStatus,FMaterialId.FNumber,FMaterialId.FName,FTargetCost Returns: str: JSON 格式的目标成本单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_materials ~105

查询物料基础资料（BD_Material）。常用 filter_string： - 按编码前缀: "FNumber like 'HG%'" - 按名称模糊: "FName like '%钢板%'" - 已审核启用: "FDocumentStatus='C'" Returns: str: JSON 格式的物料列表，含编码、名称、规格、单位、物料分组

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_misc_movement_detail ~197

查询杂项出入库明细表（STK_MiscMovementDetail）。用于查看杂项出入库的明细数据，包括其他入库、其他出库等。常用 filter_string： - 指定日期范围: "FBillDate>='2024-01-01' and FBillDate<='2024-12-31'" - 指定物料: "FMaterialId.FNumber='MAT001'" - 指定仓库: "FStockId.FNumber='WH01'" 推荐 field_keys（默认已包含关键字段）： FID,FBillNo,FBillDate,FDocumentStatus,FStockOrgId.FName, FMaterialId.FNumber,FMaterialId.FName,FUnitId.FName,FQty,FPrice,FAmount Returns: str: JSON 格式的杂项出入库明细列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_mrp_result ~90

查询 MRP 运算结果（PLAN_MRPResult）。来自销售订单/销售预测/库存不足等需求，经 MRP 运算生成的计划订单建议。可下推生成采购申请/生产订单。 Returns: str: JSON 数组，每条含 FBillNo/FMaterialId/FSrcBillNo/FPurchaseQty 等字段。

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_number_rule ~106

查询金蝶系统中的单据编号规则列表。常用 filter_string： - 指定单据类型: "FObjectType='SAL_SaleOrder'" - 指定规则名: "FNumberRuleId.FNumber='NR001'" 推荐 field_keys： FNumberRuleId,FName,FNumber,FObjectType,FPrefix,FSequenceLength,FDateFormat Returns: str: JSON 格式的单据编号规则列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

Install

How do I install the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server?

Kingdee K3Cloud (Cloud Galaxy) ERP runs locally as a PyPI package, launched with uvx kingdee-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · kingdee-mcp

Client

Showing Claude. Snippets for every client (markdown)

# add to Claude Code

claude mcp add wahailong-kingdee-mcp -- uvx kingdee-mcp

Common questions

What is the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server?

Kingdee K3Cloud (Cloud Galaxy) ERP is an MCP server listed in the public MCP registry as io.github.WaHaiLong/kingdee-mcp. Third-party open-source MCP server for Kingdee K3Cloud ERP - 101 tools, 17 domains. Unofficial. This page covers its PyPI package (kingdee-mcp).

Is the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server safe to use?

Kingdee K3Cloud (Cloud Galaxy) ERP scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server expose?

Kingdee K3Cloud (Cloud Galaxy) ERP exposes 101 tools: kingdee_usage_report, kingdee_usage_stats, kingdee_discover_tables, kingdee_discover_columns, kingdee_describe_table, and 96 more. Their descriptions and schemas cost roughly 16,856 tokens of context every time the server is loaded.

Is the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server still maintained?

Kingdee K3Cloud (Cloud Galaxy) ERP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Kingdee K3Cloud (Cloud Galaxy) ERP MCP server under?

Kingdee K3Cloud (Cloud Galaxy) ERP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Badge

Put this score in your README. The image is served from a stable URL, updates when the score does, and links back to the evidence on this page. It shows nothing that is not already published here.

Score Verified Plain

The two-cell badge: our name, and this channel's current score out of 100.

Markdown

 [![VerifyMCP trust score for Kingdee K3Cloud Cloud Galaxy ERP](https://verifymcp.io/badge/wahailong-kingdee-mcp/kingdee-mcp.svg)](https://verifymcp.io/servers/wahailong-kingdee-mcp/kingdee-mcp)

HTML

 <a href="https://verifymcp.io/servers/wahailong-kingdee-mcp/kingdee-mcp"><img src="https://verifymcp.io/badge/wahailong-kingdee-mcp/kingdee-mcp.svg" alt="VerifyMCP trust score for Kingdee K3Cloud Cloud Galaxy ERP" height="20"></a>

A single cell stating that the server is listed here. Carries no number.

Markdown

 [![VerifyMCP trust score for Kingdee K3Cloud Cloud Galaxy ERP](https://verifymcp.io/badge/wahailong-kingdee-mcp/kingdee-mcp.svg?variant=verified)](https://verifymcp.io/servers/wahailong-kingdee-mcp/kingdee-mcp)

HTML

 <a href="https://verifymcp.io/servers/wahailong-kingdee-mcp/kingdee-mcp"><img src="https://verifymcp.io/badge/wahailong-kingdee-mcp/kingdee-mcp.svg?variant=verified" alt="VerifyMCP trust score for Kingdee K3Cloud Cloud Galaxy ERP" height="20"></a>

The score alone, tier-coloured, for a badge row that is already crowded.

Markdown

 [![VerifyMCP trust score for Kingdee K3Cloud Cloud Galaxy ERP](https://verifymcp.io/badge/wahailong-kingdee-mcp/kingdee-mcp.svg?variant=plain)](https://verifymcp.io/servers/wahailong-kingdee-mcp/kingdee-mcp)

HTML

 <a href="https://verifymcp.io/servers/wahailong-kingdee-mcp/kingdee-mcp"><img src="https://verifymcp.io/badge/wahailong-kingdee-mcp/kingdee-mcp.svg?variant=plain" alt="VerifyMCP trust score for Kingdee K3Cloud Cloud Galaxy ERP" height="20"></a>

Score history · last 30 days

25 Oct 4 Nov

Day	Score
25 Oct	67
26 Oct	67
27 Oct	67
28 Oct	67
29 Oct	53
30 Oct	69
31 Oct	69
1 Nov	70
2 Nov	70
3 Nov	71
4 Nov	71