Cocos MCP Server

Self-evolving MCP for Cocos Creator — multi-instance bridges, Agent Skills, stdio server, extension, and Cursor setup. The cocos mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

MCP (stdio) + Creator extension bridge. Drive in-editor scripts and asset workflows from Cursor and other MCP clients.

Its toolset

Everything the assistant can do here goes through one of these:

• Stage — Tools
• Default — cocosmcp_exec
• Promoted — cocosmcp_r_{name}
• Value — Capability
• Creator — 1. Fully quit and restart Creator; open the target project 2. Extension → Extension Manager → Project → enable cocos-meta-mcp 3. Console
• Cursor — Setup writes %USERPROFILE%.cursor\mcp.json (Windows). In Cursor MCP settings, confirm connected (after config changes, disable then re-enable

Adding it to your client

cocos-meta-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Cocos's toolset — Stage, Default, Promoted and 3 more — is a fair guide to whether it matches your workflow. It is maintained by shinji_matou; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cocos mcp server does with a few real requests.