Let Claude drive your Cocos Creator editor

What it does

This is a Cocos Creator 3.8+ plugin that exposes the entire game editor through the Model Context Protocol. Install it, and Claude, Cursor, or any MCP client can manipulate scenes, nodes, components, prefabs, assets, and build pipelines via HTTP — no manual clicking required. The author claims it covers roughly 99% of editor operations with 50 consolidated tools.

The interesting bit

The real grind here is prefab serialization. Cocos Creator’s internal format uses {"__id__": x} references, UUIDs, and fragile ordering rules. The plugin reverse-engineered this enough that AI-generated prefabs now load without the usual Cannot read properties of undefined or placeHolder.initDefault is not a function explosions. That’s the kind of boring, valuable work that makes automated editing actually usable.

Key highlights

• 50 core tools with unified “category_action” naming and switchable action codes, down from an earlier 150+ tool sprawl
• Prefab lifecycle fully supported: create, instantiate, sync, and edit with correct internal/external reference handling
• Tested with Claude CLI, Claude Desktop, and Cursor; theoretically works with any MCP-compatible client
• Runs as an HTTP server inside the editor, not a separate process
• Tool management panel with per-tool enable/disable and persistent config

Caveats

• The “158 tools” documentation links are marked “待补充” (pending) in both English and Chinese
• GitHub lags behind the Cocos Store release; v1.5.0 is store-only as of the README date
• Removing components requires passing internal cid type fields, not human-readable class names — an extra lookup step

Verdict

Worth a look if you’re building Cocos Creator games and want an AI pair programmer that can actually touch the engine. Skip it if you’re on a pre-3.8 Cocos version or allergic to editor plugins that phone home to localhost.