Cocos Creator 2.x MCP Install: packages Folder & Cursor Setup
Cocos Creator 2.x MCP Pro install: unzip to packages, restart, activate, start MCP Server, verify in Cursor—not the 3.x package.
- cocos
- cocos-creator
- mcp
- cursor
- tutorial
- cocos-mcp
- ai
What This Guide Covers
Follow these five steps to connect Cocos Creator 2.x MCP (VberAI Pro) to a local Creator 2.x project so Cursor (or another MCP-capable AI IDE—same idea) can operate, preview, and debug the editor—not just edit scripts on disk.
When you finish, you should be able to:
- Unzip the plugin into the project
packagesfolder - Restart Creator, then activate with a VberAI account or email + activation code
- Start the local Cocos MCP Server
- Use Quick configure → Auto configure to register the server in Cursor and confirm the connection
Product page: VberAI Cocos MCP 2.x
This article uses Cursor as the example. Claude Code, Windsurf, Cline, and other MCP clients follow a similar flow.
Prerequisites
| Item | Notes |
|---|---|
| Cocos Creator | 2.4.x+ / other 2.x projects (do not mix with the 3.x package) |
| Plugin package | Cocos Creator 2.x MCP Pro archive from the official site |
| Activation | VberAI account + password, or email + activation code |
| AI IDE | Cursor recommended; other MCP clients also work |
| Local network | The MCP bridge usually runs on 127.0.0.1—do not expose the port publicly |
Step 1: Download Cocos Creator 2.x MCP
Download the Pro build from the VberAI site:
Download page: https://www.vberai.com/game-engines/cocos2x?ch=CQZLC2FG
Suggested flow:
- Open the page and download Cocos MCP 2.x Pro with your account permissions
- Save the archive locally and prepare to extract it
- Confirm the project is Creator 2.x—do not mix with the 3.x MCP package
OSS vs Pro differences and billing follow the current site copy.
Step 2: Install the Plugin (Into packages)
Unlike 3.x (Extension Manager → Import Extension), 2.x installs by placing files in the project:
- Extract the archive on your machine
- Move the extracted plugin folder into the
packagesdirectory at the Cocos Creator project root- If
packagesdoes not exist yet, create it first
- If
- Confirm the layout is
packages/<plugin-name>/and not nested one extra unzip level
Do not configure yet: restart Creator so the extension loads correctly (next step).
Step 3: Activate cocos-mcp-server
- Fully restart Cocos Creator and open the project that contains the plugin
- Menu: Extension → MCP Server
- On the activation screen, use either:
- VberAI account + password
- Email + activation code
- After activation succeeds, open the MCP Server settings page (next step)
Without activation, the server usually will not start. Confirm your plan or code matches the current Pro build.

Step 4: Start cocos-mcp-server
- After activation, open MCP Server settings
- Adjust as needed:
- Port: use the panel default or your local convention
- Language: match your UI preference
- Startup: use panel options (for example auto-start with the editor, if available)
- Click Start service
- When the panel shows Running, Cocos MCP Server is up
You now have a local MCP bridge. Next, hand it to your AI IDE.

Step 5: One-Click AI IDE Setup (Cursor Example)
- Open Tool manager
- Review tools exposed by Cocos MCP Server
- Enable only what you want the AI to use
- Open Quick configure
- Choose your IDE (for example Cursor)
- Click Auto configure
- Confirm the UI shows a configured state
- Open Cursor
- In the MCP / tools list you should see cocos-creator (or the name shown in the panel) connected
- If it is missing, click Reload (or the equivalent MCP reload) in Cursor and check again
Other IDEs follow the same path—just pick a different client under Quick configure.

Quick verification after connecting
In Cursor, start with a read-only check, for example:
List the root nodes of the scene currently open in Cocos Creator.
If the reply matches the editor hierarchy, the bridge works. Then try a small write (create a temporary node and delete it) to confirm permissions and tool selection.
FAQ
Files are in packages, but there is no Extension → MCP Server menu?
Confirm you fully restarted Creator (not just a scene reload). Check the folder sits at packages/<plugin-name>/ without an extra zip nesting. Confirm you downloaded the 2.x package, not 3.x.
Activation keeps failing?
Confirm Pro entitlements, or that the activation code is valid and tied to the correct email. Check the account center on the site, then retry in the panel.
I clicked Start service but never see Running?
Confirm the port is free and localhost is not blocked. Make sure Step 3 completed successfully.
Cursor does not show cocos-creator?
In Creator, confirm the server is still Running, run Quick configure → Auto configure again, then reload MCP in Cursor. If it still fails, check that Cursor’s MCP config includes the local bridge address.
Next Steps
- Use natural language for a scene query or a small edit to learn the tool boundaries
- Commit before large changes; keep the bridge on localhost only
- For design-to-engine UI, pair with VberAI Studio, then iterate in-editor with MCP
For Creator 3.x, follow the Cocos Creator 3.x MCP install guide—do not mix packages. Compare all engines: Godot vs Unity vs Cocos MCP. Hub: AI game development tools 2026.
Keep reading
More guides you might like
VberAI Studio: Game sprite image puzzle vs. video frame splitting, how to integrate with Unity / Godot / Cocos
VberAI Studio generates action video, splits sequence frames on canvas, and delivers to Unity, Godot, and Cocos. Compare GPT Image sprite sheets and open-source DIY pipelines: which saves time, when to use Studio.
- vberai
- ai-studio
- sprite-frames
- sequence-frames
Mobile HUD Information Hierarchy: What to Show in Combat, Lobby, and Modals
HUD visibility and priority by game state; how it ties to Safe Area, floating text layers, and modal stacking—spec tables plus Play and device acceptance steps.
- game-ui-design
- game-dev-ai
- ui-to-engine
- hud
Pre-Launch UI Checks: What to Verify Before Ship
After Prefab and logic are in place: final UI pass on device, locales, Release builds, and event skins—extends design handoff and engine MCP acceptance with fix paths.
- game-ui-design
- game-dev-ai
- ui-to-engine
- ui-localization