英语 ·中文

一个编辑器扩展，将LLM（Claude桌面/光标或任何MCP客户端）连接到 Cocos Creator 2.4.x编辑器，让模型检查并驱动你的游戏项目：读写 节点，操作资源和场景，读取控制台，执行脚本。

这是cocos-mcp-3x（Creator 3.8.x版本）的2.4.x移植版：相同 Python MCP 服务器和 WebSocket 协议，仅在 2.4 编辑器 API 和扩展端有所不同 调用。该插件是自包含的——Python MCP服务器捆绑在./server——并且 扩展没有NPM依赖，也没有构建步骤。

基于 Cocos Creator 2.4.15 开发并验证;面向整个 2.4.x 系列（包括 2.4.9）。

它是如何运作的

• Python 端是 WebSocket server;Cocos 扩展是客户端并拨号入 通过面板上的连接按钮。
• 每个工具调用都会向扩展（main.js）发送一个JSON信封，扩展通过命令进行调度 名称：资产操作使用 Editor.assetdb;节点/场景图操作被转发到 场景脚本 scene.js（通过场景中的 cc 引擎变异活图

cocos-mcp-2x

English · 中文

An editor extension that connects an LLM (Claude Desktop / Cursor or any MCP client) to the Cocos Creator 2.4.x editor, letting the model inspect and drive your game project: read/write nodes, operate on assets and scenes, read the console, and execute scripts.

This is the 2.4.x port of cocos-mcp-3x (the Creator 3.8.x version): the same Python MCP server and WebSocket protocol, differing only in the 2.4 editor APIs the extension side calls. The plugin is self-contained — the Python MCP server is bundled at ./server — and the extension has no npm dependencies and no build step.

Developed and verified against Cocos Creator 2.4.15; targets the whole 2.4.x line (incl. 2.4.9).

How it works

MCP client (Claude / Cursor)
        │  stdio / http
        ▼
Python FastMCP server  ── server/src/main.py
        │  WebSocket bridge  127.0.0.1:6020/cocosmcp
        ▼
Cocos Creator extension ── main.js (connects in as the WS client)
        │
        ├─ Editor.assetdb / Editor.Ipc         assets, scene open/save
        └─ Editor.Scene.callSceneScript ──► scene.js (scene process, holds the cc engine runtime)

• The Python side is the WebSocket server; the Cocos extension is the client and dials in via the Connect button on the panel.
• Each tool call sends a JSON envelope to the extension (main.js), which dispatches by command name: asset operations use Editor.assetdb; node/scene-graph operations are forwarded to the scene script scene.js (which mutates the live graph through the cc engine in the scene process), then replies {id, success, data|error}.

Differences from the 3.x version

Tools provided