$ loading_
Let AI agents control Cocos Creator for scenes, assets, UI, and animation
This MCP tool does not declare any required secrets or remote endpoints, and it is an auditable MIT-licensed open-source project with no clear high-risk red flags. The main security considerations are local code execution and read/write control over Cocos project assets/scenes, which are typical capabilities for this type of tool and should be used in a controlled project environment.
The material explicitly states that no keys or environment variables are required. No API keys, tokens, or other sensitive credentials are requested, so the credential exposure and misuse risk appears low.
The material lists no remote endpoint host, and the description does not mention cloud services, telemetry, or external API connections. Based on the available information, there is no clear data egress path.
The system flags this tool as having code-execution capability, and the description says it can control the Cocos Creator editor through 43+ tools for scene manipulation, UI creation, animation, and more. This implies it can typically drive local editor processes or perform related local actions, so it should be treated as a local execution tool and granted access carefully.
Its stated functions include asset management and scene manipulation, which typically require reading and modifying scenes, assets, and related project files within a Cocos workspace. There is no explicit sign of overbroad access beyond the stated purpose, but it should be assumed to have substantial read/write access to the project workspace.
Positive factors are that the project is open source and MIT licensed, making the source auditable and lowering risk. However, it comes from a third-party registry, shows only 0 stars, and has unknown maintenance status, so there is limited evidence of maturity or ongoing upkeep; code and dependencies should still be reviewed.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Cocos MCP" yet — see the docs or source repo.
Use Cocos MCP to create a main menu scene in the current project with a background image, Start button, Settings button, and title text, and organize the node names clearly in the hierarchy.
A well-structured main menu scene with organized UI nodes, ready for further editing in the editor.
Use Cocos MCP to scan the current project assets, sort images, prefabs, audio, and animations into standardized folders, and report the changes made.
Assets are reorganized by type, with a summary of changes for easier development and collaboration.
Using Cocos MCP, add idle and movement animations to a character node, configure animation state transitions, and describe which objects and properties were changed.
A working basic animation state setup, along with a description of the editor changes applied.
Let AI control Cocos Creator for faster scene, node, and asset editing.
Control Cocos Creator 2.x to turn designs into UI scenes and prefabs.
Automate local Cocos Creator workflows for project creation, scene editing, and WeChat builds.
Connect to a local Cocos Creator MCP server for development automation.
Generate Cocos Creator-ready game assets, audio, and UI resources with AI.
Aggregate local MCP servers into one endpoint with runtime control and hot reload.