Skip to main content
Glama

Why CocosMCP?

Work with scenes, nodes, components, assets, and runtime objects through structured MCP tools. CocosMCP runs locally, requires no CocosMCP account, and imposes no tool-call quotas. Your AI client's own requirements and limits still apply.

The repository includes separate Creator 2.x and 3.x extensions, a standalone MCP service, a capability catalog, and a development runtime bridge. Registered operations span 54 functional modules; registration, implementation, and verification are reported separately, so coverage is not a claim that every feature is complete.

See the Creator 2.4.15 implementation and acceptance record (Chinese) for the independent test project, native coverage, and remaining limitations.

Related MCP server: Cocos Creator MCP Server

MCP feature overview

A compact overview of implemented MCP entry points. Exact version support, prerequisites, and verification levels are documented in the version table below and the feature reference.

Editor & assets

Runtime & interaction

Workflows & diagnostics

ScenesCreate, open, save, inspect hierarchy

Object inspectionHierarchy, properties, object handles

Projects & instancesProjects, editors, runtime sessions

NodesCreate, duplicate, reparent, delete, transform

Runtime controlsPause, resume, inspect state

Capability discoverySearch, schemas, versions, coverage

ComponentsFind types, add, configure, reset

Controls & inputControl actions, mouse, keyboard, touch

Workflow orchestrationValidate plans, sequence steps, bind results

Asset operationsQuery, import, save, move, resolve UUIDs

Animation & actionsPlayback, track sampling, Tweens (2.x)

Preview & capturesStart/stop, screenshots, viewport checks

Asset organizationLocate folders, preview plans, apply moves

Skeleton animationSpine playback/skins, DragonBones (2.x)

Logs & diagnosticsBridge, preview, native console (3.x)

PrefabsCreate, instantiate, apply, revert

Maps & physicsRead/edit tiles, raycasts, contact queries

Performance samplingFrame times, P99, budgets, render metrics

UI compositionDeclarative creation, updates, layout/events

Cameras & renderingCoordinate conversion, visibility, diagnostics

Build jobsStart, status, logs, list, cancel

Materials & ShadersProperties, macros, backups, native compile (3.x)

Media & particlesAudio/video playback, basic particle controls

Artifact checksBuild files, sizes, content hashes

Clips & templatesEdit clips/keyframes, component templates (3.x)

Runtime assetsLoad, preload, release references, inspect Bundles

Recovery queriesOperation results, workflow progress, build records

Scene & reference checksSnapshot diffs, missing components, dependencies

Events & tasksSubscriptions, bounded sampling, poll/cancel tasks

Visual & layout checksUI geometry, bounds, Shader preview comparisons

Find entry points with cocos_capability_search / cocos_capability_describe, then call them through cocos_capability_execute. Workflows and builds also provide dedicated MCP tools.

Supported features by Creator version

The exact adaptation baselines are Creator 2.4.15 and Creator 3.8.8. This table describes implemented scope. Native evidence covers specific fixtures and parameters; it does not certify every feature, platform, or the entire engine. Other 2.x / 3.x versions do not inherit this support automatically.

Feature

Creator 2.4.15

Creator 3.8.8

Editor & assets

Scenes, nodes, components, Prefabs, undo/redo, AssetDB, organization, dependencies/users

Comparable core editing, plus native console queries and version-matched editor messages

UI & references

Declarative creation/updates, structural plans, scene/saved-file reference audits and deletion guards

Declarative creation/updates and layout/event checks; 2.x-specific structural/audit endpoints are not shared automatically

Controls & preview

Five semantic control adapters with real drag/click/text event tests; windows, captures, logs and sizing

Windows, captures, logs, mouse/keyboard/touch and viewport checks; native menu interaction records

Animation & actions

curveData editing/recovery; bounded sequential/parallel/repeated Tweens with cancellation and lifecycle checks

Native tracks, animation controls and animation-graph inspection; excludes 2.x-specific Tween task endpoints

Skeletons

Spine/DragonBones structure, cache boundaries, event tasks, real-time mixing and cleanup with native records

Spine playback/queues/skins/attachments and track sampling; does not inherit the 2.x cache/event/mixing evidence

Maps & physics

Orthogonal/isometric Tilemaps, ordinary collisions, body forces, joint inspection and Box contact tracing/cleanup

Tilemap and physics query/contact tools, subject to backend checks; separate native 3D CCT route records

Camera & rendering

2D/3D coordinates, masks, 2D Graphics/Mask offscreen pixels and owned GPU-object deletion

Geometry/arrays/render settings, Shader RenderTexture previews, debug drawing, sorting, probes and IK

Shaders & materials

Effect source/backups, material properties/macros and runtime override recovery; no 3.x compiler

Native Effect compilation, dependency fingerprints, material instances, macro variants and preview comparisons

Resource lifecycle

Load/release, Bundle inspection, snapshots/diffs and multi-scene trends

Load/release and Bundle inspection; the 2.x snapshot/trend endpoints are not declared for 3.x

Gameplay templates

2.x templates are not delivered yet

13 editable templates, including controllers, cameras, virtual lists, dialogue and pools; not all gameplay paths accepted

Media & diagnostics

Basic audio/video/particle controls and UI/Label/atlas/Graphics diagnostics

Media, particles and performance/render diagnostics; platform experience and GPU performance need separate evidence

Workflows & builds

Local workflows and CLI jobs; recorded game-build environment failures remain

Local workflows, CLI jobs and artifact checks; signing, devices, SDKs and publication require separate acceptance

As of 2026-10-08, the catalog contains 315 capability entries across 54 modules. Creator 2.4.15 wires up to 123 editor + 106 runtime endpoints, with another 11 handled or composed in the application layer; 276 entries apply to major version 3. These are not current availability, native pass counts, or the default tool-list length. That historical snapshot passed 333 tests. This batch was installed and tested in isolated projects for both versions; production game projects were not updated.

Still incomplete: additional 2.4.15 joints, Prefab differences/repair, image/font/atlas quality workflows, loading traces, TMX persistence, 2.x templates, material pipeline controls, focus/grid, single stepping/Scheduler, and other tracked work. The 2.4.15 game build still has recorded exportSimpleProject and FBX converter failures; building the plugin does not prove game export succeeds. The 3.8.8 post-processing and skinning paths also retain explicit limitations.

See the version support matrix, 2.4.15 adaptation record, and full acceptance tracker for details and evidence (Chinese).

Preview reliability and acceptance (2026-10-08)

CP-001 through CP-013 are implemented: complete runtime bundles, scene/frame identity, focus before input, landscape/view restoration, loaded-byte refresh evidence, layered readiness, sanitized auditing, semantic clicks, acceptance recipes, guarded fixtures, and lifecycle regression. An earlier source snapshot passed 14 synthetic native checks per version. That historical snapshot passed 333 automated tests and 14/14 native checks on Creator 2; Creator 3 passed 12/14, with hidden-window input outcome unknown and the recipe failing its success assertion. This is not a full native pass for the current source. Launchers reuse local credentials and existing sessions rather than creating a fresh login environment for every run.

Creator 2 scene loaded-byte proof may still be unknown. External Chrome MCP integration, physical devices, GPU memory, and real matchmaking/payment flows remain unverified. See the preview acceptance guide for examples, reproduction steps, and evidence boundaries (Chinese).

Capabilities

  • Local MCP transports: stdio and authenticated Streamable HTTP.

  • Dockable control center: project and editor instance information, capabilities, bridge logs, runtime state, and bridge start/stop controls. The panel supports Simplified Chinese and English, defaults to Chinese, and saves the preference per project. Logs retain their original text and support copying errors.

  • Inspectable changes: scene.snapshot and scene.diff provide baselines and recursive added, removed, and changed path records for nodes, components, properties, and arrays.

  • Recoverable status: workflow status and build-job indexes persist under the target project's .codex-work/cache/cocos-mcp/. A build still running at service restart is marked as failed with unknown state instead of permanently blocking the project.

  • Operation tracking: explicit operationId values support in-process idempotent reuse; query completed results with cocos_operation_query. Audit logs record operation metadata only.

  • Source discovery: generate editor-message/type candidates from Creator source or ASAR, or an engine-capabilities.json catalog from engine source. Candidates remain source-only until separately verified.

Version support is operation-specific. Inspect creator2Operations, creator3Operations, and each capability's verification evidence before use; unsupported versions are rejected before execution. See the feature reference and Shader guide.

Download and offline installation

Send the prompt below to an AI assistant with network, local filesystem, terminal, and desktop access. You do not need to download files, locate paths, or fill in configuration first. The assistant discovers the target from your workspace and local environment, then downloads, installs, starts, and verifies the connection. This route needs network access; manual offline ZIP instructions follow.

Download CocosMCP from GitHub, install it, and connect this AI client to my Cocos Creator project.
Repository: https://github.com/iEfoam/CocosMcp
Releases: https://github.com/iEfoam/CocosMcp/releases

Prioritize convenience. Handle discovery, downloads, installation, configuration, startup and verification yourself.
Do not ask me to download files, fill in paths, copy tokens, run commands or click through a tutorial.
Use your available tools to perform the installation, rather than just describing steps.

1. Identify the target project, exact Creator version/path, OS/architecture, current AI client and MCP configuration
   from the workspace, open Creator project and client context. Prefer the current project; do not modify other projects.
   Ask a brief question only if the target remains genuinely ambiguous.
2. Query this repository's GitHub Releases, using the API and pagination when needed. Do not guess download URLs.
   Prefer a stable release with complete installation assets; otherwise use the latest complete development prerelease
   and report that choice. Download the matching Creator-major ZIP, SHA256SUMS and release-manifest.json
   from the same release into the project's .codex-work/downloads/. Verify hashes, versions and package identity.
   Do not install if verification fails.
3. Discover and verify a standalone Node.js 24+. If missing, download an appropriate current Node 24.x LTS
   distribution from the official Node.js site for this OS/architecture, verify it and preferably extract it
   under the project's .codex-work/. Avoid changing system Node or requiring manual installation;
   request necessary system authorization only when required.
4. Preserve .gitignore rules and ensure .codex-work/ is ignored. Stage/extract inside the project and reject escaping paths.
   Stop this extension's own MCP service and unload/reload the target extension using available tools.
   Never force-close an editor with unsaved work. Back up the old extension under .codex-work/build/extension-backups/.
   Install Creator 2 into packages/cocos-mcp-creator2/ with package name cocos-mcp-creator2;
   install Creator 3 into extensions/cocos-mcp-creator3/ with package name cocos-mcp-creator3.
   Place package.json directly in the extension root. Do not modify game assets/scripts/scenes or other extensions.
5. Configure the unified client and authorize this exact project. For local builds, use the existing CLI install command,
   not manual file copying. The installer writes nodeExecutable and clientInstallation into service-config.json and
   bootstraps a missing client when a complete client bundle is present. Missing bundles, corrupt configuration or
   authorization failures must fail installation; pending is not success. Do not broaden allowedRoots.
   Verify authorization.state=authorized and the target project's “Unified stdio” panel shows “This project is authorized”
   and “Revoke project authorization”.
   Use the bundled service; do not clone source or install npm/pnpm dependencies.
6. Use desktop/editor tools to open the project, load the extension and start MCP from its control center.
   Read the actual HTTP endpoint and local Bearer token yourself. Back up and merge this AI client's Streamable HTTP
   configuration, preserving other connections. Never print the token in chat or commit it to Git.
   Do not guess ports or configuration formats. Reload the connection using the client's supported mechanism;
   prefer project-scoped settings.
7. Actually call cocos_projects and cocos_instances to verify the intended project and editor instance.
   Finish with the installed version, project, verification result and backup location.
   If permissions, client capabilities or unsaved work block automation, complete independent steps first,
   then report only the concrete blocker and minimum required authorization. Do not hand the entire installation
   back to me or claim an unverified connection succeeded.

Manual download and offline installation

Prebuilt packages require no source checkout, pnpm installation, or compilation. Choose a version on GitHub Releases, then download the matching ZIP and SHA256SUMS from Assets. You can transfer these files to an offline computer. Pre-release entries are development builds: select them manually; the stable updater does not automatically install them.

Release asset

Purpose

cocos-mcp-creator2.zip / cocos-mcp-creator3.zip

Choose a ZIP for manual installation, matching Creator 2 / 3

SHA256SUMS / release-manifest.json

File checksums; versions, build IDs, and source fingerprint

*.full.json / cocos-mcp-creator{2,3}.json

Full / required-runtime updater bundles; legacy seven-file Creator 2 updaters need a full upgrade; not directly installable editor packages

GitHub-generated Source code archives

Repository source; follow Quick start below to build it

Install a ZIP manually

  1. Have the matching Cocos Creator and Node.js 24+ installed locally. The adaptation baselines are 2.4.15 / 3.8.8. Do not install both major-version packages into one project.

  2. Compare the ZIP's SHA-256 with its entry in the same release's SHA256SUMS, using a local tool such as shasum -a 256 <ZIP-path> on macOS/Linux or Get-FileHash <ZIP-path> -Algorithm SHA256 in PowerShell. Before upgrading, stop this project's MCP service, close Creator, and back up its existing extension under .codex-work/build/extension-backups/.

  3. Extract the ZIP contents into the matching directory below. package.json must be directly inside that directory, without an extra enclosing folder. Do not put the extension in assets/.

Creator

Installation directory within the project

2.x

<project>/packages/cocos-mcp-creator2/

3.x

<project>/extensions/cocos-mcp-creator3/

  1. Create service-config.json alongside the extension's package.json. Check node --version, then use node -p "process.execPath" to find the absolute Node executable path. Insert that path below; escape Windows backslashes as required by JSON:

{
  "nodeExecutable": "/absolute/path/to/node"
}

Release ZIPs intentionally omit this machine-specific file. Use a separately installed Node.js 24+, not Creator's embedded Node. The offline ZIP installation does not need a source buildRoot.

  1. Open the project, confirm the extension is loaded in the extension manager, and choose CocosMCP → Open Control Center → Start MCP Service. This also starts the editor bridge. Game preview and runtime integration remain separate steps.

  2. Select a connection mode in the control center and copy its configuration (a generic JSON template; adapt it to your client):

    • Local stdio (recommended): the client launches the extension's bundled dist/stdio.mjs with Node.js. No MCP port, source checkout or pnpm installation is needed. Stop any HTTP service for the same project before switching.

    • Streamable HTTP: start the service from the panel. The first assigned port is saved and reused after restart; an occupied port produces an error instead of a silent port change. The configuration includes the Bearer token from <project>/.codex-work/cache/cocos-mcp/mcp-http-token; keep it private. The panel recognizes client-owned services and leaves their lifecycle to the client. Multiple clients can share HTTP. Call cocos_projects and cocos_instances to verify the project and editor instance.

“Offline” means plugin installation needs no dependency downloads; it does not guarantee that your AI model runs offline. Online update checks may fail without a network connection. The offline package also includes stdio. HTTP reconnection behavior must be verified for your actual client. To roll back, stop the service, close Creator, and replace the extension directory with its backup.

Quick start

For multiple game projects, use the unified stdio client. Configure Codex once, then pass the session workspacePath directly to project tools for automatic connection. Explicit projectPath/projectId and cocos_project_connect remain supported; ambiguous authorized targets require selection. Independent sessions share one backend per project. After pnpm check, run pnpm client:install, or install the standalone offline client ZIP.

1. Install and build

Use Node.js 24+, pnpm 11 (the repository pins the exact version in package.json), and an existing Cocos Creator project.

pnpm install
pnpm check

pnpm check runs type checking → build → tests → build; the final build embeds matching test evidence. Project configuration keeps build and test output under .codex-work/.

2. Install the editor extension

Use your own project and editor paths. This example targets Creator 3.8.8 on macOS:

pnpm start install \
  --project /path/to/my-cocos-project \
  --creator /Applications/Cocos/Creator/3.8.8/CocosCreator.app

Editor

Extension location in the target project

Creator 2.x

packages/cocos-mcp-creator2/

Creator 3.x

extensions/cocos-mcp-creator3/

The installer backs up an existing extension of the same name. Open the project in Creator, load the extension, and use CocosMCP → Open Control Center (打开控制中心). The menu order is About CocosMCP → Open Control Center → Check for Updates. About and updates have dedicated views; bridge start/stop controls live inside the control center. The MCP service discovers protected instance descriptors and routes requests by project, editor version, and instance ID.

3. Check the connection and start MCP

# Inspect the environment, editor instances, and module coverage.
pnpm start doctor --project /path/to/my-cocos-project

# Start stdio transport for an MCP client.
pnpm start serve --project /path/to/my-cocos-project

# Or start local Streamable HTTP: allocate once and reuse the saved port.
pnpm start serve --project /path/to/my-cocos-project --transport http

HTTP binds only to 127.0.0.1, requires a Bearer token, and rejects non-local Host/Origin values. The token is stored in the target project's .codex-work/cache/cocos-mcp/mcp-http-token.

For client configuration and troubleshooting, see the user guide (Chinese).

Plan a workflow

Pass a sequence like this to cocos_workflow_plan, replacing the scene URL with an existing scene in your project (.scene for Creator 3, .fire for Creator 2):

{
  "projectId": "<project-id>",
  "steps": [
    { "capabilityId": "scene.open", "params": { "uuid": "db://assets/main.scene" } },
    { "capabilityId": "node.create", "params": { "name": "LoginPanel" } },
    { "capabilityId": "scene.save", "params": {} }
  ]
}

Planning checks parameters, versions, risks, and side effects. Use cocos_workflow_execute after the plan is valid and any required authorization is in place. Execution stops on failure by default and returns completed steps and compensation hints. There is no universal rollback: use each capability's rollback guidance. Query persisted progress with cocos_workflow_status after a service restart.

Steps support paramRefs for earlier results, runtimeRef for explicit preview session binding, and read-only waitFor conditions. Workflow IDs cannot be replayed. Keyboard input defaults to canvas focus; frame profiling reports warmup, P99, render dimensions and optional P95 budgets. Frame timeouts include game/Director pause states and never automatically resume the game. See the reliability and performance guide (Chinese).

Verification and safety

The verification field describes the evidence behind a capability:

Level

Evidence

source-only

Discovered from source, declarations, or ASAR analysis only

unverified

Registered without completed automated verification

contract-tested

Parameter and protocol contract tests passed

adapter-tested

Mock editor/runtime adapter tests passed

editor-verified

Verified in a real Creator editor project

runtime-verified

Verified in a real development runtime

device-verified

Verified on the target device or platform

cocos_coverage reports registered, implemented, planned, and verified counts separately. Automated checks cover schemas, path safety, the capability catalog, and runtime policies. Passing pnpm check does not establish complete Creator 2.4.15/3.8.8 editor, device, platform SDK, or GPU acceptance; those require corresponding real-environment checks.

The runtime bridge is restricted to loopback connections and development builds. Property paths, method paths, and argument counts are validated; dangerous host entry points are rejected. Project-code execution and arbitrary editor-message calls require the explicit startup flag --allow-project-code.

Before creating assets, query asset.location and reuse the returned directory. For asset organization, review asset.organize.plan and apply it with the same parameters and planHash; existing asset moves must use AssetDB to preserve metadata. See asset organization.

Development

# Rebuild the service, extensions, and runtime bridges.
pnpm build

# Discover Creator editor-message and type candidates.
pnpm start catalog --project /path/to/project --creator /Applications/Cocos/Creator/3.8.8/CocosCreator.app

# Analyze engine source and generate engine-capabilities.json.
pnpm start catalog --project /path/to/project --engine /path/to/cocos-engine

Build output:

.codex-work/build/
├── server/cli.mjs
├── extensions/creator2/
├── extensions/creator3/
└── runtime/

Documentation

The detailed guides below are currently written in Chinese. Both README editions cover the same version support and setup flow. Local reports under .codex-work/ are ignored by Git; linked guides provide reproduction scripts and evidence boundaries.

Guide

Contents

Version support · Creator 2 acceptance

Exact-version feature matrix, native evidence and remaining scope

User guide

Installation, startup, client configuration, and examples

Feature reference

Capabilities by domain and version limits

2D development · Delivery & verification

SpriteFrame, animation, UI, physics, Spine, Tilemap, and 13 editable gameplay templates for Creator 3.8.8

Implementation & acceptance

Architecture, version differences, safety, and real-environment checks

Scene production & preview

Creator 3.8.8 geometry, arrays, rendering, preview windows, and screenshots

Shader development

Native Effect compilation, materials, and validation boundaries

Asset organization

Directory reuse, organization plans, and guarded asset moves

Preview acceptance · Reliability · External connector

CP-001–013, session reuse, real input, recipes/fixtures, refresh proof and reproduction

Proposal · Roadmap

Project scope and phased implementation

Verification checklist · Implementation notes

Completion evidence, added capabilities, and examples

License

First-party code is licensed under MIT. Cocos Creator, the engine, Spine, DragonBones, platform SDKs, and other third-party dependencies remain subject to their respective licenses.

For the current build, see the generated .codex-work/build/verification-summary.md (under profiles/dev/ for development builds). It separates source applicability, test counts, version-specific native evidence, and module scope acceptance. Dated figures above are historical. See build profiles.

Available Tools

41 tools
cocos_asset_import导入工程目录内的文件D
Destructive

导入工程目录内的文件

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_asset_query查询资源;支持类型和路径过滤C
Read-only

查询资源;支持类型和路径过滤

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_assets_organize_apply执行项目资源整理B

执行已审查计划;必须保留预览范围和 planHash。通过 AssetDB 移动保留 UUID,遇到变化拒绝,部分失败返回恢复记录。

Inputs: planHash (required), projectId (required), urls, scopeUrl, +5 more.

cocos_assets_organize_plan项目资源整理预览B
Read-only

按资源类型规划整理,优先已有目录;返回源/目标、UUID、冲突与跳过原因。默认仅 assets 根目录,agent 审查路径引用后再执行。

Inputs: projectId (required), urls, scopeUrl, recursive, +4 more.

cocos_build_artifacts核对构建产物A
Read-only

检查已成功任务的完整文件集、入口和 SHA-256;不代表可安装或运行,不执行产物

Inputs: jobId (required), projectId (required), entryPaths (required).

cocos_build_cancel取消构建C
Destructive

取消正在执行的构建任务

Inputs: jobId (required), projectId (required).

cocos_build_list构建任务B
Read-only

列出工程的构建任务

Inputs: projectId (required).

cocos_build_logs构建日志C
Read-only

分页读取构建日志

Inputs: jobId (required), projectId (required), limit, offset.

cocos_build_recover恢复未知构建占用A
Destructive

仅在用户确认原构建已经停止后使用。保留未知结果与产物,只解除任务占用;记录 PID 仍存活时拒绝,不杀进程。

Inputs: jobId (required), projectId (required), confirmedStopped (required).

cocos_build_start启动 Creator 构建B
Destructive

使用 Creator CLI 构建已注册工程并返回任务 ID;构建需要本机 GUI 和已安装的平台工具

Inputs: platform (required), projectId (required), creatorPath (required), options, +1 more.

cocos_build_status构建状态B
Read-only

查询构建任务状态、产物和日志路径

Inputs: jobId (required), projectId (required).

cocos_capability_describe能力详情B
Read-only

获取精确参数 Schema、版本范围、副作用、当前源码验证状态及历史证据

Inputs: capabilityId (required), projectId.

cocos_capability_execute执行已注册能力A
Destructive

创建资源前必须调用 asset.location,复用已有类型目录;后续使用结果的 assetLocation.url,禁止假定 assets 根路径。整理已有资源先 asset.organize.plan,审查引用后用相同范围及 planHash 调用 asset.organize.apply。按能力详情的 Schema 执行。修改前建议传 expectedRevision 和稳定 operationId。执行器不会执行任意 eval。

Inputs: projectId (required), capabilityId (required), params, instanceId, +3 more.

cocos_component_add添加内置或项目脚本组件D
Destructive

添加内置或项目脚本组件

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_component_set修改组件属性和引用并读回验证C
Destructive

修改组件属性和引用并读回验证

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_connection_status工程连接状态B
Read-only

查看统一客户端已连接工程的后端身份、兼容性和编辑器状态,不返回凭据

Inputs: projectId.

cocos_coverage功能覆盖清单B
Read-only

查看全部 54 个模块的范围验收、能力与独立服务工具计数及历史证据;partial 不代表没有可用操作

Inputs: projectId.

cocos_instances编辑器实例A
Read-only

列出指定工程已打开的 Creator 实例,不返回认证凭据

Inputs: projectId (required).

cocos_node_create创建节点并返回实际节点信息C
Destructive

创建节点并返回实际节点信息

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_node_query读取节点及组件属性C
Read-only

读取节点及组件属性

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_node_set编辑节点属性并读回验证C
Destructive

编辑节点属性并读回验证

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_operation_query查询操作结果B
Read-only

超时或断线后查询 operationId,避免重复执行修改

Inputs: projectId (required), operationId (required), instanceId.

cocos_prefab_instantiate实例化预制体到场景D
Destructive

实例化预制体到场景

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_project_connect连接 Creator 工程A

兼容显式连接入口;普通工程工具可直接传 workspacePath 或 projectPath 自动连接。此入口使用绝对工程路径,复用或启动工程后端,不启动编辑器或登录,返回工程与实例标识。

Inputs: projectPath (required), instanceId.

cocos_project_disconnect断开工程连接C

仅释放当前客户端连接,不停止其他会话或运行中的构建

Inputs: projectId (required).

cocos_projects工程列表A
Read-only

统一客户端列出当前已连接工程;单工程服务列出启动时注册的工程

Inputs: no named parameters.

cocos_runtime_capture捕获当前游戏 Canvas 图像D
Read-only

捕获当前游戏 Canvas 图像

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_runtime_instances运行时实例B
Read-only

列出已连接的开发运行实例

Inputs: projectId (required).

cocos_scene_diff将当前场景与基线快照进行结构化差异比较C
Read-only

将当前场景与基线快照进行结构化差异比较

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_scene_hierarchy分页读取场景层级D
Read-only

分页读取场景层级

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_scene_open打开已有场景;有未保存修改时拒绝切换C
Destructive

打开已有场景;有未保存修改时拒绝切换

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_scene_query读取当前场景信息和修改状态C
Read-only

读取当前场景信息和修改状态

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_scene_save保存当前场景并查询修改状态D
Destructive

保存当前场景并查询修改状态

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_scene_snapshot生成可重放的当前场景序列化快照C
Read-only

生成可重放的当前场景序列化快照

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_scene_validate检查缺失组件与无效对象引用C
Read-only

检查缺失组件与无效对象引用

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_ui_build静态 UI 默认通过已规划文档创建编辑器节点,返回 UUID 映射;随后 scene.save 或 prefab.create 并读回验证。脚本只负责交互与动态内容;部分失败使用局部补偿C
Destructive

静态 UI 默认通过已规划文档创建编辑器节点,返回 UUID 映射;随后 scene.save 或 prefab.create 并读回验证。脚本只负责交互与动态内容;部分失败使用局部补偿

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_ui_plan静态 UI 默认入口:规划可编辑场景节点,检查版本、引用和名称冲突,返回 planHashC
Read-only

静态 UI 默认入口:规划可编辑场景节点,检查版本、引用和名称冲突,返回 planHash

Inputs: params (required), projectId (required), instanceId, operationId, +2 more.

cocos_workflow_execute执行工作流A
Destructive

按顺序执行已规划能力;默认遇到失败即停止,并返回已完成步骤和补偿提示

Inputs: steps (required), projectId (required), workflowId, continueOnError.

cocos_workflow_plan规划工作流B
Read-only

批量校验能力参数、版本、风险和副作用;规划不会修改工程

Inputs: steps (required), projectId (required).

cocos_workflow_status工作流状态C
Read-only

查询持久化工作流的步骤进度、失败位置和最终结果

Inputs: projectId (required), workflowId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.6/5.0

    Scored across 41 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to directly control the Cocos Creator 3.8.x editor via MCP protocol, providing over 130 tools for scene, node, component, asset, and project operations.
      44
      -
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with the Cocos Creator 3.8+ editor through standardized protocols for scene, node, component, prefab, asset, project, debugging, and server operations.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI clients to inspect and operate the Cocos Creator project currently open, including scenes, nodes, assets, animations, and editor workflows via MCP.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI assistants drive the Cocos Creator editor in-process: querying the live scene graph, reading and writing assets, starting builds, tailing logs, and capturing editor screenshots.
      22 npm
      MIT