$ loading_
Let AI control Cocos Creator for faster scene, node, and asset editing.
This MCP tool is described as a local integration that directly controls the Cocos Creator editor via MCP, with no stated API keys or remote endpoints. The main concerns are local code execution and project/asset access, but since it is open source under MIT, it is better classified as caution rather than high risk.
The material explicitly states that no keys or environment variables are required, and there is no indication that users must provide API keys, account tokens, or other sensitive credentials; based on the available material, credential exposure appears limited.
The material explicitly lists no remote endpoints, and the description focuses on controlling the local Cocos Creator editor via MCP; there is no factual indication that user data is sent to external services.
The system checks confirm executes-code capability, and the described features include direct control of the game editor, scene management, node manipulation, component attachment, and asset management, indicating significant local operational privileges. This kind of local execution/control is common for MCP tools, but it warrants caution due to the possibility of unintended or abusive project modifications.
Based on its stated functions, it likely needs read/write access to scenes, nodes, components, and asset files within Cocos projects. The available material does not show system-wide data access beyond its stated purpose, but its ability to modify project assets still calls for least-privilege use and testing in a non-production project first.
Positive signals include an auditable open-source repository and an MIT license; however, the source is a third-party registry, community adoption is listed as 0 stars, maintenance status is unknown, and the audit material is sparse. Supply-chain trust is therefore moderate and should be treated cautiously rather than as highly trusted.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Cocos MCP Server" yet — see the docs or source repo.
Using Cocos MCP Server, create a new scene named "Level_01" in the current project, add a background node, a player node, and three enemy nodes, and arrange them evenly from left to right.
A new saved scene with the basic node layout is created.
Check the Player node in the current scene. If it does not have Sprite, RigidBody2D, and BoxCollider2D components, add them automatically and rename the node to Hero.
The tool reports the component changes and updates the node name.
Using Cocos MCP Server, organize the assets directory by moving image assets into a textures folder, prefabs into a prefabs folder, and then list all changes made.
Assets are reorganized by type, with a clear list of all file changes.
Automate local Cocos Creator workflows for project creation, scene editing, and WeChat builds.
Control Cocos Creator 2.x to turn designs into UI scenes and prefabs.
Let AI agents control Cocos Creator for scenes, assets, UI, and animation
Generate Cocos Creator-ready game assets, audio, and UI resources with AI.
Connect to a local Cocos Creator MCP server for development automation.
Let AI manipulate Godot projects, scenes, nodes, and editor workflows.