CocosMCP
Related Servers
Alternatives to CocosMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI clients to inspect and operate the Cocos Creator project currently open, including scenes, nodes, assets, animations, and editor workflows via MCP.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to directly control the Cocos Creator 3.8+ editor, including scene and node manipulation, UI building, script attachment, validation, preview runtime logs, and screenshots.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to read and write Cocos Creator 2.x project files, create and batch-edit scenes and prefabs, run project and asset diagnostics, and launch engine Web previews where a game can be actually played — dispatching touches, reading state, capturing console output and screenshots. It also provides routing across multiple open editor projects, build targets, and a self-test that verifies each tool's return contracts.1MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with the Cocos Creator 3.8+ editor through standardized protocols for scene, node, component, prefab, asset, project, debugging, and server operations.-
- AlicenseNot gradedqualityBmaintenanceLets AI assistants drive the Cocos Creator editor in-process: querying the live scene graph, reading and writing assets, starting builds, tailing logs, and capturing editor screenshots.22 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to directly control the Cocos Creator 3.8.x editor via MCP protocol, providing over 130 tools for scene, node, component, asset, and project operations.44-
TDQS
Scored across 41 tools
Many tools are distinct, but cocos_capability_execute overlaps with dedicated asset organize/import tools and with workflow execution; scene_query/hierarchy/node_query and ui_build vs node_create also require careful reading. Descriptions help, but several boundaries are not immediately obvious.
All tools use a cocos_ prefix and snake_case with mostly domain-led patterns such as cocos_build_start and cocos_scene_save. Minor inconsistencies exist, like singular cocos_asset_import versus plural cocos_assets_organize_plan and noun-only tools such as cocos_projects and cocos_instances.
41 tools is heavy for an agent and exceeds the typical well-scoped range; despite the broad Cocos Creator domain, the explicit build/scene/asset/connection/workflow tools plus the generic capability layer create significant surface area. Some consolidation could reduce cognitive load.
Coverage is broad across project connection, assets, scenes, nodes, components, prefab instantiation, builds, runtime capture, UI, and workflows. Missing explicit delete/remove operations for nodes, components, and assets, plus no obvious scene/prefab creation tool, are notable gaps, but the generic capability executor/search/describe can likely handle long-tail operations.