Kingdee K3Cloud (Cloud Galaxy) ERP

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_query_operation_logs ~272

查询金蝶云星空的上机操作日志（BOS_OperateLog）。记录用户在系统中的所有操作：登录、登出、进入业务对象、业务操作等。用于安全审计、故障排查、操作追溯。推荐场景： - 排查某张单据是谁在什么时候操作的 - 安全审计：检查异常登录或批量操作 - 合规要求：追溯敏感操作记录返回字段说明： - FDATETIME: 操作时间 - FUSERID: 操作用户 - FCOMPUTERNAME: 机器名称 - FCLIENTIP: 客户端IP - FENVIRONMENT: 操作场景（0=登入系统, 1=进入业务对象, 3=业务操作, 4=登出系统） - FOPERATENAME: 操作名称（登录/单据查询/批量保存等） - FDESCRIPTION: 操作描述 - FInterId: 对象内码（关联单据号） - FTimeConsuming: 耗时(毫秒) - FClientType: 客户端类型 Returns: str: JSON 格式的操作日志列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_outsource_orders ~497

查询委外加工订单（SUB_SubReqOrder）列表。委外加工订单记录外协生产任务，包含 CP 测试、封装、FT 成品测试等工序的委托加工情况，是 WIP 在制量、逾期分析、回货预测的核心数据来源。常用 filter_string： - 在制（未结案）： "FDocumentStatus='C' and FStatus not in ('6','7')"（默认） - 指定供应商： "FSupplierId.FName like '%华力%'" - 逾期未完工： "FPlanFinishDate<GETDATE() and FStatus not in ('3','6','7')" - 30 天内到期： "FPlanFinishDate>=GETDATE() and FPlanFinishDate<=DATEADD(day,30,GETDATE())" - 指定批次： "FLot.FNumber='AP5E047'" - 指定产品型号： "FMaterialId.FSpecification='APT32F004B'" - 已完工待入库： "FStatus='3'" 关键字段说明： - FQty：委外订单总数量（颗） - FStockInQty：已入库数量（已完工回厂的数量） - FNoStockInQty：未入库在制量（FQty - FStockInQty，可为负表示超收） - FStatus：执行状态（1=开工，3=完工，6=结案，7=结算） - FPlanFinishDate：计划完工日（逾期判断基准） - FPurOrderNo：关联采购订单号（CP 委外专用，可反查晶圆来源采购单） - FLot.FNumber：批次号（WIP 追溯用） - F_XTR_Qty：晶圆辅单位片数（自定义扩展字段，如需可追加到 field_keys） 💡 REMEMBER: 若报"字段不存在"，用 kingdee_get_fields('SUB_SubReqOrder') 确认该账套可用字段 Returns: str: JSON，含 count / has_more / data 字段

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_partners ~74

查询客户（BD_Customer）或供应商（BD_Supplier）基础资料。 partner_type 取值：BD_Customer 或 BD_Supplier Returns: str: JSON 格式的客户/供应商列表，含编码、名称、简称、联系人、电话

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_pending_approvals ~58

查询待审批的单据列表。查询当前处于审批中状态（已提交、待审核）的单据。 Returns: str: JSON 格式的待审批单据列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_permission ~92

查询金蝶系统中的权限列表。常用 filter_string： - 指定角色: "FRoleId.FNumber='ROLE001'" - 指定对象类型: "FObjectType='BD_Material'" 推荐 field_keys： FPermissionId,FName,FNumber,FObjectType,FObjectName,FIsAllow Returns: str: JSON 格式的权限列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_permission_changes ~173

查询金蝶云星空的权限变更记录。记录用户权限的授予、撤销、修改操作。用于安全审计、合规检查、权限追溯。推荐场景： - 安全审计：谁在什么时候被授予/撤销了什么权限 - 合规要求：保留权限变更的审计轨迹 - 问题排查：某用户无法访问某功能的原因注意：金蝶权限数据可能存储在多个表单中，如 SEC_Permission（权限记录）、SEC_UserRole（用户角色关系）等。如查询无结果，请用 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_product_standard_cost ~115

查询产品标准成本（STD_ProductCostQuery）。常用 filter_string： - 指定物料: "FMaterialId.FNumber='MAT001'" - 指定成本版本: "FCostVersionId.FNumber='STD01'" 推荐 field_keys： FMaterialId.FNumber,FMaterialId.FName,FUnitId.FName,FStdCost,FMaterialCost,FLabourCost,FFeeCost Returns: str: JSON 格式的产品标准成本列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_production_orders ~159

查询生产订单（PRD_MO）列表。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定日期: "FDate>='2024-01-01'" - 进行中: "FStatus='2'" (1=计划,2=确认,3=投料,4=汇报,5=入库) - 指定物料: "FMaterialId.FNumber='MAT001'" 推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FMaterialId.FName,FQty,FPlanStartDate,FPlanFinishDate,FStatus Returns: str: JSON 格式的生产订单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_production_pick_materials ~131

查询生产领料单（PRD_PickMtrl）列表。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定生产订单: "FMoBillNo='MO000001'" - 指定仓库: "FStockId.FNumber='CK001'" 推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FMoBillNo,FMaterialId.FName,FPickQty,FStockId.FName Returns: str: JSON 格式的生产领料单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_production_plan ~60

查询生产计划单（PLAN_ProductionPlan）。生产计划单是 MRP 运算后手工调整的计划单据，可直接下推生成生产订单。 Returns: str: JSON 数组。

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_production_report ~82

查询生产汇报单（PRD_MOReport）。生产汇报记录工序完成数量/工时/良品率等信息，是生产入库的提前工序。 Returns: str: JSON 数组，含 FBillNo/FMOId/FMaterialId/FReportQty/FHourQty 等。

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_production_stock_in ~128

查询生产入库单（PRD_Instock）列表。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定生产订单: "FMoBillNo='MO000001'" - 指定仓库: "FStockId.FNumber='CK001'" 推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FMoBillNo,FMaterialId.FName,FInQty,FStockId.FName Returns: str: JSON 格式的生产入库单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_purchase_inquiry ~133

查洵采购询价单（SVM_InquiryBill/RFQ）列表。采购询价单（Request for Quotation）用于向供应商询价，收集报价信息。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定供应商: "FSupplierId.FNumber='S001'" 推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FSupplierId.FName,FMaterialId.FName,FPrice Returns: str: JSON 格式的询价单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_purchase_order_progress ~379

查询采购订单行明细及执行进度（含累计收料/入库数量）。与 kingdee_query_purchase_orders 的区别： - 本工具查询【表体分录级】字段，返回每行物料的详细执行情况 - 默认返回已审核单据，可通过 filter_string 过滤返回的关键字段（demo 账套实测）： - FBillNo: 单据编号 - FMaterialId.FNumber / FMaterialId.FName: 物料编码/名称 - FQty: 订单数量 - FReceiveQty: 累计收料数量 - FStockInQty: 累计入库数量 - FPrice: 单价（不含税） - FTaxPrice: 含税单价 - FAllAmount: 价税合计以下字段需启用供应链模块后才存在（demo 环境可能不存在）： - FLinkQty: 关联数量（=累计收料数量+累计入库数量） - FBusinessClose: 业务关闭状态（A=正常，B=业务关闭） - FFreezeStatus: 冻结状态（A=正常，B=冻结） - FTerminateStatus: 终止状态（A=正常，B=终止） - FDlyCntl_Low / FDlyCntl_High: 交货下限/上限业务关闭规则（需启用供应链）： - 累计入库数量 >= 交货下限时，该行自动【业务关闭】 - 累计入库数量 < 交货下限时，自动【业务反关闭】 Returns: str: JSON 格式的采购订单执行进度列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_purchase_orders ~296

查询采购订单（PUR_PurchaseOrder）列表。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定供应商: "FSupplierId.FNumber='S001'" - 指定日期: "FDate>='2024-01-01' and FDate<='2024-12-31'" - 未关闭: "FCloseStatus='A'" - 业务正常: "FBusinessClose='A'" 推荐 field_keys（默认已包含关键执行字段）： FID,FBillNo,FDate,FDocumentStatus,FSupplierId.FName,FPurchaseDeptId.FName, FTaxAmount,FAllAmount,FReceiveQty,FStockInQty 注：FTotalAmount/FLinkQty/FBusinessClose 等字段在 demo 环境可能不存在，如需关联数量，请用 FReceiveQty + FStockInQty 代替，或用 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_purchase_requisitions ~160

查询采购申请单（PUR_Requisition）列表。采购申请单是采购流程的起点，用于向采购部门提出物料或服务采购需求。申请单可下推生成采购订单、采购询价单等。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定申请人: "FApplicantId.FNumber='EMP001'" - 指定申请部门: "FRequestDeptId.FNumber='D001'" 推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FApplicantId.FName,FRequestDeptId.FName,FTotalAmount Returns: str: JSON 格式的采购申请单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_quality_inspections ~169

查洵来料检验单（QIS_InspectBill/IQC）列表。来料检验单用于对采购物料进行质量检验，判断是否允许入库。常用 filter_string： - 已检验: "FDocumentStatus='C'" - 检验结果-合格: "FResult='1'" 或 "FPassQty>0" - 检验结果-不合格: "FFailQty>0" 推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FSupplierId.FName,FMaterialId.FName,FPassQty,FFailQty,FInspectTypeId.FName Returns: str: JSON 格式的来料检验单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_receipts ~442

查询应收单（AR_Receivable）列表，支持按客户、日期、核销状态、打开状态过滤。应收单记录客户应收账款，包含应收金额、已核销金额、核销状态等信息，是营收、回款、应收余额、票据占比等财务指标的核心数据来源。常用 filter_string： - 已审核： "FDocumentStatus='C'"（默认） - 指定客户： "FCUSTOMERID.FNumber='C001'" - 指定月份： "FDATE>='2026-01-01' and FDATE<='2026-01-31'" - 未核销： "FWRITTENOFFSTATUS='A'" - 未关闭： "FOPENSTATUS='A'" - 期初数据： "FISINIT=true"（初始化单）或 "FISINIT=false"（业务单）关键字段说明： - FALLAMOUNTFOR：应收总金额（原币含税），财务核心指标 - FNOTAXAMOUNTFOR：应收不含税金额（原币），用于综合毛利率计算 - FRELATEHADPAYAMOUNT：已核销金额 - FWRITTENOFFSTATUS：核销状态（A=未核销，B=部分核销，C=完全核销） - FOPENSTATUS：打开状态（A=未关闭，B=已关闭，C=部分关闭） - FENDDATE_H：到期日 - FISINIT：是否为初始化单据（期初数据） ⚠️ 不同金蝶账套字段名可能不同（如 FCUSTOMERID 可能为 FCustId、FDate 可能为 FDATE），先调用 kingdee_get_fields('AR_Receivable') 确认该账套可用字段。 Returns: str: JSON，含 count / has_more / data 字段

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_report ~837

通过金蝶 WebAPI **GetSysReportData（查询报表数据）** 查询任意总账/财务报表。端点：Kingdee.BOS.WebApi.ServicesStub.DynamicFormService.GetSysReportData.common.kdsvc （实测确认：formid 必须作为独立 HTTP 表单字段、data 为内层参数的 JSON 字符串。此前"表单标识为空"的根因是 formid 被嵌进了 data JSON 对象；KDSReportAPIService 端点实测也一律 Unknown Error，不可用。）请求体为 HTTP 双字段：formid = 报表标识；data = JSON 字符串（即本工具 params.data）。 model 典型结构：FieldKeys(返回字段) + Model(过滤条件) + StartRow/Limit(分页)。与单据查询(ExecuteBillQuery)不同，报表分页用 StartRow/Limit，**不是** PageIndex/PageSize；账簿用 FACCTBOOKID.FNumber（按编码，如 "001"）；期间用 FSTARTYEAR/FSTARTPERIOD/FENDYEAR/FENDPERIOD，层级用 FBALANCELEVEL。 ⚠️ FieldKeys 必须是报表真实列 Key——猜的列名会触发服务端 totalWidth 渲染错误； FBALANCELEVEL=0（全部级次）时**必须**配 FSHOWFULLNAME=true，否则 AccountBalanceStatement.UpdateAcctName 会因 PadLeft(-N) 抛 "totalWidth 要求非负数"。 💡 0 行结果通常是该账簿/期间 T_GL_BALANCE 本身无数据，并非查询失败（book '001' 金蝶蓝海科技只有 2020 年演示数据，2026 年返回 0 行属于正常）。已实测确认的报表 formId（财务会计 → 总账）： - 科目余额表 = GL_RPT_AccountBalance - 总账账龄分析表 = GL_AgingSchedule（注意：无 RPT_ 前缀）其余报表 formId 需在 BOS/ApiDoc 逐张查证（核算维度余额表、数量金额总账、日报表、多账簿系列、试算平衡表、现金流量表、现金流量查询、报表项目 KDS_RptItem 等）。 params.data（model）权威结构——科目余额表（金蝶开发者社区官方案例 + 2026-08-05 实测 book '001' 金蝶蓝海科技 → 2020 年 2 月期初/本期/本年累计/期末数据完整 72 行）： {"FieldKeys":"FBALANCEID,FBALANCENAME,FACCTTYPE,FACCTGROUP,FCyName," "FBEGINDEBIT,FBEGINCREDIT,FDEBIT,FCREDIT," "FYTDDEBIT,FYTDCREDIT,FENDDEBIT,FENDCREDIT", "SchemeId":"","StartRow":0,"Limit":10, "IsVerifyBaseDataField":"true","FilterString":[], "Model":{"FACCTBOOKID":{"FNumber":"001"},"FCURRENCY":"1", "FSTARTYEAR":2020,"FSTARTPERIOD":2,"FENDYEAR":2020,"FENDPERIOD":2, "FBALANCELEVEL":1,"FSHOWDETAIL":false,"FFORBIDBALANCE":true, "FBALANCEZERO":true,"FPERIODNOBALANCE":true,"FYEARNOBALANCE":true, "FSHOWFULLNAME":true}} 返回：金蝶原始 JSON（含报表数据 Rows），前端/调用方按需解析。 Raises/Returns: str: JSON（成功为报表数据；失败为错误 JSON）

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_role ~88

查询金蝶系统中的角色列表。常用 filter_string： - 指定角色名: "FRoleID.FNumber='admin'" - 启用状态: "FIsActive=1" 推荐 field_keys： FRoleID,FName,FNumber,FIsActive,FCreateDate,FDescription Returns: str: JSON 格式的角色列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_sale_orders ~104

查询销售订单（SAL_SaleOrder）列表。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定客户: "FCustId.FNumber='C001'" 推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FCustId.FName,FSalesOrgId.FName,FTotalAmount Returns: str: JSON 格式的销售订单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_sale_quotations ~222

查询销售报价单（SAL_Quotation）列表。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定客户: "FCUSTID.FNumber='C001'" - 未失效: "FExpiryDate>='2026-01-01'" 推荐 field_keys（默认已包含关键字段）： FID,FBillNo,FDate,FDocumentStatus,FCUSTID.FName,FSalerId.FName,FExpiryDate 注（本环境为二开定制，与标准字段不同）： - 销售员字段为 FSalerId（非标准 FSalesmanId），写 FSalesmanId 会 500 - 主表无 FTotalAmount（金额在分录 FQUOTATIONFIN 内），如需金额请用 kingdee_query_bills 指定分录字段，或用 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_sales_outstock ~287

查询销售出库单（发货单）。对应金蝶 ApiDoc 销售管理域「销售出库」模块，FormId: SAL_OUTSTOCK。用于查询已发货/出库的明细，支持按客户、仓库组织、日期、单据状态筛选。 ⚠️ 字段 Key 警示（真机实测，2026-08-07）：本环境客户字段的元数据 Key 是 **FCustomerID**（大写 ID 后缀），并非 SAL_SaleOrder 常见的 FCustId，也不是 kingdee_list_forms 推荐的 FCustId。直接传 FCustId 会报「元数据中标识为FCustId的字段不存在」。字段 Key 一律以 kingdee_get_fields 元数据为准。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定客户: "FCustomerID.FNumber='C001'" - 日期区间: "FDate>='2026-05-01' and FDate<='2026-05-31'" 推荐 field_keys（已按本环境元数据校验可用）： FID,FBillNo,FDate,FDocumentStatus,FCustomerID.FName,FStockOrgId.FName

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_sequence ~102

查询金蝶系统中的编码规则（SequenceRule）列表。常用 filter_string： - 指定单据类型: "FObjectType='PUR_PurchaseOrder'" - 指定编码规则: "FSequenceRuleId.FNumber='SEQ001'" 推荐 field_keys： FSequenceRuleId,FName,FNumber,FObjectType,FDescription,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_stock_bills ~115

查询出入库相关单据。 form_id 常用取值： - STK_InStock: 采购入库单 - SAL_OUTSTOCK: 销售出库单 - STK_MisDelivery: 其他出库单 - STK_Miscellaneous: 其他入库单 - STK_TransferDirect: 直接调拨单 Returns: str: JSON 格式的出入库单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_stock_in ~325

查询采购入库单。对应金蝶 ApiDoc 库存管理域「采购入库」模块，FormId: STK_InStock。用于查询已完成/在途的采购入库单及其供应商信息，支持按供应商、仓库、日期、单据状态筛选。 ⚠️ 字段 Key 警示（真机实测，范探源已验证）：本单据业务伙伴是**供应商**，字段 Key 用 **FSupplierId**（注意与销售类单据的 FCustId / FCustomerID 不同，采购入库单的客户字段并不存在）。误用 FCustId 会报「字段不存在」。字段 Key 一律以 kingdee_get_fields 元数据为准。 ⚠️ 动作范围说明：标准保存/提交/审核动作已由通用 kingdee_save_bill / kingdee_submit_bills / kingdee_audit_bills 等按 FormId 参数化覆盖，本工具仅做查询，不负责写操作。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定供应商: "FSupplierId.FNumber='V001'" - 日期区间: "FDate>='2026-05-01' and FDate<='2026-05-31'" 推荐 field_keys（已按本环境元数据校验可用）： FID,FBillNo,FDate,FDocumentStatus,FSupplierId.FName

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_stock_transfer_apply ~153

查询调拨申请单（STK_TransferApply）列表。调拨申请单用于申请仓库之间物料的转移，经审核后可下推生成调拨单。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定调出仓库: "FSendStockId.FNumber='WH01'" - 指定调入仓库: "FReceiveStockId.FNumber='WH02'" 推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FSendStockId.FName,FReceiveStockId.FName Returns: str: JSON 格式的调拨申请单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_supplier_quotes ~156

查洵供应商报价单（SVM_QuoteBill）列表。供应商报价单是供应商对询价单的响应，包含物料价格信息。可用于比价分析，选择最优供应商。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定供应商: "FSupplierId.FNumber='S001'" - 指定物料: "FMaterialId.FNumber='MAT001'" 推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FSupplierId.FName,FMaterialId.FName,FPrice,FQuantity Returns: str: JSON 格式的报价单列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_system_config ~91

查询金蝶系统中的系统配置参数。常用 filter_string： - 指定配置项: "FConfigKey='MaxUploadSize'" - 指定分类: "FCategory='System'" 推荐 field_keys： FConfigId,FConfigKey,FConfigValue,FDescription,FCategory,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_transfer_apply ~246

查询调拨申请单（STK_TransferApply）列表。调拨申请单是调拨业务的起点，可下推生成直接调拨单或分步式调拨单。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定日期范围: "FBillDate>='2024-01-01' and FBillDate<='2024-12-31'" - 指定调出仓库: "FOutStockId.FNumber='WH01'" - 指定调入仓库: "FInStockId.FNumber='WH02'" - 未关闭: "FCloseStatus='A' and FBusinessClose='A'" 推荐 field_keys（默认已包含关键字段）： FID,FBillNo,FBillDate,FDocumentStatus,FStockOrgId.FName, FOutStockId.FName,FInStockId.FName,FTransferType, 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_transfer_direct ~237

查询直接调拨单（STK_TransferDirect）列表。直接调拨单用于一步完成调拨业务，同时更新调出仓和调入仓库存。常用 filter_string： - 已审核: "FDocumentStatus='C'" - 指定日期范围: "FBillDate>='2024-01-01' and FBillDate<='2024-12-31'" - 指定调出仓库: "FOutStockId.FNumber='WH01'" - 指定调入仓库: "FInStockId.FNumber='WH02'" - 未关闭: "FCloseStatus='A' and FBusinessClose='A'" 推荐 field_keys（默认已包含关键字段）： FID,FBillNo,FBillDate,FDocumentStatus,FStockOrgId.FName, FOutStockId.FName,FInStockId.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_transfer_pending_detail ~227

查询分步式调出未调入明细表（STK_TransferPendingDetail）。用于查看分步式调拨流程中，已调出但未调入的单据明细。常用 filter_string： - 指定调出日期范围: "FOutDate>='2024-01-01' and FOutDate<='2024-12-31'" - 指定物料: "FMaterialId.FNumber='MAT001'" - 指定调出仓库: "FOutStockId.FNumber='WH01'" 推荐 field_keys（默认已包含关键字段）： FID,FBillNo,FOutDate,FInDate,FDocumentStatus,FStockOrgId.FName, FOutStockId.FName,FInStockId.FName,FMaterialId.FNumber,FMaterialId.FName, FUnitId.FName,FOutQty,FInQty,FPendingQty Returns: str: JSON 格式的分步式调出未调入明细列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_user ~104

查询金蝶系统中的用户列表。常用 filter_string： - 指定用户名: "FUserID.FNumber='user001'" - 在岗状态: "FIsActive=1" - 指定部门: "FDepartment.FNumber='D001'" 推荐 field_keys： FUserID,FName,FNumber,FDepartment.FName,FIsActive,FCreateDate Returns: str: JSON 格式的用户列表

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_query_workflow_status ~50

查询单据的审批流状态。返回单据当前的审批状态和单据详情。 Returns: str: JSON 格式的审批状态信息

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_refresh_metadata ~75

强制重新从金蝶拉取指定表单的元数据（忽略内存/磁盘缓存），用于表单结构变更后刷新。返回是否成功及字段数量。刷新后 kingdee_validate_bill / kingdee_save_bill 将使用最新字段定义。

Input Output Examples

Name	Type	Req	Description
form_id	string	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_save_asset ~57

新增或修改固定资产（FA_FAGet）。固定资产新建后状态为"草稿"，需提交+审核后才生效。修改已审核资产需要反审核后才能操作。

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_save_bill ~219

新建或修改金蝶单据（采购订单、销售订单等）。 - 新建：model 中不传 FID - 修改：model 中必须传 FID，并设置 is_delete_entry=false 防止分录被删 - 自动纠错：如字段名拼写错误（如 FSalesOrgId→FSaleOrgId），会自动修正新建采购订单 model 示例： { "FDate": "2024-01-15", "FSupplierId": {"FNumber": "S001"}, "FPurchaseDeptId": {"FNumber": "D001"}, "FPOOrderEntry": [ {"FMaterialId": {"FNumber": "MAT001"}, "FQty": 100, "FPrice": 10.5, "FUnitID": {"FNumber": "PCS"}} ] } Returns: str: JSON，含新建单据的 FID 和单据编号 FBillNo

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_save_cost_adjustment ~129

新建或修改成本调整单（STK_CostAdjust）。 model 示例： { "FDate": "2024-01-15", "FCostOrgId": {"FNumber": "100"}, "FAdjustType": "1", "FCostAdjustEntry": [ {"FMaterialId": {"FNumber": "MAT001"}, "FAdjustQty": 100, "FAdjustPrice": 10.5} ] } Returns: str: JSON，含 FID 和 FBillNo

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_save_production_order ~116

新建或修改生产订单（PRD_MO）。新建示例： { "FDate": "2024-01-15", "FMaterialId": {"FNumber": "MAT001"}, "FQty": 100, "FPlanStartDate": "2024-01-20", "FPlanFinishDate": "2024-01-25" } Returns: str: JSON，含 FID 和 FBillNo

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_submit_bills ~72

提交单据（草稿 → 待审核）。返回结构化结果：success=true 时包含 next_action 字段，建议调用 kingdee_audit_bills 完成审核。 Returns: str: JSON，含 success / next_action / bill_ids 字段

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_submit_production_orders ~48

提交生产订单（PRD_MO）至审核队列。 Returns: str: JSON，含 success / next_action / bill_ids

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_unaudit_bills ~73

反审核单据（已审核 → 待审核）。反审核后可重新修改和提交。返回结构化结果：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_unclose_bill ~326

整单反关闭单据（已整单关闭的单据恢复业务，opNumber 随表单而异）。 - FormId 参数化通用工具（非某单专用，理由：反关闭是标准动作应走通用工具防重复），适用于单据（销售订单、采购申请单、发货通知单等）。 - action 依据：范探源 2026-08-07 三重证据查证 + QA 严过关真机实测——反关闭 opNumber 因表单而异（如 SAL_SaleOrder=YLUnBillClose、PUR_Requisition=Unclose、 PUR_PurchaseOrder=BillUnClose、SAL_DELIVERYNOTICE=UncloseBill），无法静态固定，需真机确认。 - 端点/格式：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_upload_attachment ~133

按 WebAPI V6.0 上传一块附件并绑定已存在的单据（表头或分录）。直接传 Base64，不读取服务器本地文件。单块最多 4 MiB。多块上传须按顺序调用，保持单据/分录/文件名一致，后续块传首次返回的 file_id，只有最后一块 is_last=true。上传完成不触发单据提交或审核。 success=true 且 next_action=null 才表示全部上传完成；失败或结果未知时不要自动重传。

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_usage_report ~97

查看 MCP 使用统计报告，包括工具调用频率、成功率、耗时分布等。此工具分析已记录的使用日志，帮助了解： - 哪些工具被高频使用 - 哪些工具失败率较高 - API 调用耗时分布 - 使用时段分布 Returns: str: 使用报告（支持 text/markdown/json 格式）

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_usage_stats ~70

获取当前会话的使用统计摘要。返回当前进程内聚合的统计数据： - 工具使用次数 - 成功/失败次数 - 累计耗时 - 错误类型统计 Returns: str: 统计数据的 JSON 格式

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_validate_bill ~173

保存前校验单据模型（不真正保存），秒级反馈结构是否正确，避免反复试错。返回： - ok: 是否通过（无缺失必填、无结构问题） - is_new: 是否新建（model 无 FID） - auto_fixes: 将被自动更名的字段 [{"from","to","location"}]（如 FCustId→FCUSTID） - missing_required: 缺失的顶层必填字段 - entry_issues: 分录中缺失的必填子字段 / 结构异常 - suggestions: 修正建议清单典型用法：先用本工具校验 -> 按 suggestions 修正 -> 再调用 kingdee_save_bill，一次成功。

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_view_bill ~110

根据单据内码 FID 获取单据完整详情（含所有分录字段）。 mode=summary（默认）：关联字段只保留 Id / Number / Name，大幅缩减体积，适合参照旧单建新单。完整数据动辄 10 万字符，summary 通常在 1 万以内。 mode=full：返回原始 JSON。 Returns: str: JSON 格式的单据数据

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_view_production_order ~73

查看生产订单（PRD_MO）完整详情。必填参数： - form_id: "PRD_MO" - bill_id: 单据 FID 或 bill_no: 单据编号 Returns: str: JSON 格式的生产订单完整数据

Input Output Examples

Name	Type	Req	Description
params	–	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

kingdee_void_bills ~285

作废单据（opNumber=Cancel，非 Invalid！全库无 Invalid 常量）。 - FormId 参数化通用工具（非某单专用，理由：作废是标准动作应走通用工具防重复），仅适用于单据（如 SAL_SaleOrder / PUR_PurchaseOrder / STK_InStock 等）。 - action 依据：范探源 2026-08-07 三重证据查证——作废 = Cancel，旧文档误作 Invalid（OperationNumberConst.cs 反编译确认全库无 Invalid 常量），勿引用。 - 端点/格式：ExecuteOperation，opNumber=Cancel 放**顶层**（与 formid 平级）， data 只放业务参数 {"Ids":"..."} 或 {"Numbers":[...]}（QA 严过关真机实测格式）。 - 传参：bill_ids（FID 列表，优先）或 bill_nos（单据编号列表），至少一个。 - 二开单据自定义作废动作时，可显式传 operation 覆盖默认 Cancel。 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.

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