CocosMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cocos_project_connectA | 兼容显式连接入口;普通工程工具可直接传 workspacePath 或 projectPath 自动连接。此入口使用绝对工程路径,复用或启动工程后端,不启动编辑器或登录,返回工程与实例标识。 |
| cocos_project_disconnectC | 仅释放当前客户端连接,不停止其他会话或运行中的构建 |
| cocos_connection_statusB | 查看统一客户端已连接工程的后端身份、兼容性和编辑器状态,不返回凭据 |
| cocos_projectsA | 统一客户端列出当前已连接工程;单工程服务列出启动时注册的工程 |
| cocos_instancesA | 列出指定工程已打开的 Creator 实例,不返回认证凭据 |
| cocos_capability_searchC | 搜索操作目录;先查询再执行长尾功能 |
| cocos_capability_describeB | 获取精确参数 Schema、版本范围、副作用、当前源码验证状态及历史证据 |
| cocos_coverageB | 查看全部 54 个模块的范围验收、能力与独立服务工具计数及历史证据;partial 不代表没有可用操作 |
| cocos_capability_executeA | 创建资源前必须调用 asset.location,复用已有类型目录;后续使用结果的 assetLocation.url,禁止假定 assets 根路径。整理已有资源先 asset.organize.plan,审查引用后用相同范围及 planHash 调用 asset.organize.apply。按能力详情的 Schema 执行。修改前建议传 expectedRevision 和稳定 operationId。执行器不会执行任意 eval。 |
| cocos_assets_organize_planB | 按资源类型规划整理,优先已有目录;返回源/目标、UUID、冲突与跳过原因。默认仅 assets 根目录,agent 审查路径引用后再执行。 |
| cocos_assets_organize_applyB | 执行已审查计划;必须保留预览范围和 planHash。通过 AssetDB 移动保留 UUID,遇到变化拒绝,部分失败返回恢复记录。 |
| cocos_workflow_planB | 批量校验能力参数、版本、风险和副作用;规划不会修改工程 |
| cocos_workflow_executeA | 按顺序执行已规划能力;默认遇到失败即停止,并返回已完成步骤和补偿提示 |
| cocos_workflow_statusC | 查询持久化工作流的步骤进度、失败位置和最终结果 |
| cocos_operation_queryB | 超时或断线后查询 operationId,避免重复执行修改 |
| cocos_runtime_instancesB | 列出已连接的开发运行实例 |
| cocos_build_startB | 使用 Creator CLI 构建已注册工程并返回任务 ID;构建需要本机 GUI 和已安装的平台工具 |
| cocos_build_statusB | 查询构建任务状态、产物和日志路径 |
| cocos_build_listB | 列出工程的构建任务 |
| cocos_build_logsC | 分页读取构建日志 |
| cocos_build_artifactsA | 检查已成功任务的完整文件集、入口和 SHA-256;不代表可安装或运行,不执行产物 |
| cocos_build_cancelC | 取消正在执行的构建任务 |
| cocos_build_recoverA | 仅在用户确认原构建已经停止后使用。保留未知结果与产物,只解除任务占用;记录 PID 仍存活时拒绝,不杀进程。 |
| cocos_scene_queryC | 读取当前场景信息和修改状态 |
| cocos_scene_snapshotC | 生成可重放的当前场景序列化快照 |
| cocos_scene_diffC | 将当前场景与基线快照进行结构化差异比较 |
| cocos_scene_hierarchyD | 分页读取场景层级 |
| cocos_scene_openC | 打开已有场景;有未保存修改时拒绝切换 |
| cocos_scene_saveD | 保存当前场景并查询修改状态 |
| cocos_node_queryC | 读取节点及组件属性 |
| cocos_node_createC | 创建节点并返回实际节点信息 |
| cocos_node_setC | 编辑节点属性并读回验证 |
| cocos_component_addD | 添加内置或项目脚本组件 |
| cocos_component_setC | 修改组件属性和引用并读回验证 |
| cocos_asset_queryC | 查询资源;支持类型和路径过滤 |
| cocos_asset_importD | 导入工程目录内的文件 |
| cocos_prefab_instantiateD | 实例化预制体到场景 |
| cocos_ui_planC | 静态 UI 默认入口:规划可编辑场景节点,检查版本、引用和名称冲突,返回 planHash |
| cocos_ui_buildC | 静态 UI 默认通过已规划文档创建编辑器节点,返回 UUID 映射;随后 scene.save 或 prefab.create 并读回验证。脚本只负责交互与动态内容;部分失败使用局部补偿 |
| cocos_scene_validateC | 检查缺失组件与无效对象引用 |
| cocos_runtime_captureD | 捕获当前游戏 Canvas 图像 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| cocos-edit-workflow | 定位工程、读取场景、修改、保存并读回验证 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| coverage | 全部提案模块的覆盖状态 |
| /app |
TDQS
Scored across 41 tools
Many tools are distinct, but cocos_capability_execute overlaps with dedicated asset organize/import tools and with workflow execution; scene_query/hierarchy/node_query and ui_build vs node_create also require careful reading. Descriptions help, but several boundaries are not immediately obvious.
All tools use a cocos_ prefix and snake_case with mostly domain-led patterns such as cocos_build_start and cocos_scene_save. Minor inconsistencies exist, like singular cocos_asset_import versus plural cocos_assets_organize_plan and noun-only tools such as cocos_projects and cocos_instances.
41 tools is heavy for an agent and exceeds the typical well-scoped range; despite the broad Cocos Creator domain, the explicit build/scene/asset/connection/workflow tools plus the generic capability layer create significant surface area. Some consolidation could reduce cognitive load.
Coverage is broad across project connection, assets, scenes, nodes, components, prefab instantiation, builds, runtime capture, UI, and workflows. Missing explicit delete/remove operations for nodes, components, and assets, plus no obvious scene/prefab creation tool, are notable gaps, but the generic capability executor/search/describe can likely handle long-tail operations.