Skip to main content
Glama

Related Servers

Alternatives to cocos-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for Cocos Creator 3.8+ that enables AI assistants to interact with the editor via 50+ tools for scene, node, component, prefab, asset, and project management.
      15 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server plugin for Cocos Creator 3.8+ that enables AI assistants to control the editor via standardized protocol, offering 50 tools for scene, node, component, prefab, asset, project, and debugging operations.
      15 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Cocos Creator that enables AI tools to automate scene editing, resource management, and project operations via HTTP and stdio interfaces.
      11 npm
      226
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server plugin for Cocos Creator 3.8+ that enables AI assistants to control the editor through 50 tools covering scenes, nodes, components, prefabs, assets, projects, debugging, and more.
      15 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for local Cocos Creator 3.8 automation, enabling coding agents to create projects, edit scenes, and build WeChat Mini Games directly on a developer machine.
      19
      2
      MIT

    TDQS

    C2.9/5.0

    Scored across 184 tools

    Disambiguation2/5

    The tool set has significant overlap and ambiguity, with many tools performing similar functions or having unclear boundaries. For example, there are multiple tools for adding components (cocos_add_component, cocos_add_rigidbody2d, cocos_add_box_collider2d, etc.) and many specialized tools that could be confused with more general ones (e.g., cocos_add_button_with_label vs cocos_add_button plus cocos_add_label). The descriptions help, but the sheer number of overlapping tools makes disambiguation difficult.

    Naming Consistency5/5

    Tool names follow a highly consistent snake_case pattern with a clear 'cocos_' prefix and descriptive verb_noun structure throughout. Examples include cocos_add_script, cocos_create_scene, cocos_set_property, and cocos_scaffold_game_loop. There are no deviations in naming conventions, making the set predictable and readable.

    Tool Count1/5

    With 184 tools, the count is extremely high for any server's purpose, indicating severe bloat and lack of focus. This many tools will overwhelm agents and make selection challenging, as many tools could be consolidated or removed without losing functionality. The scope appears to cover every possible Cocos Creator operation, but such comprehensiveness comes at the cost of usability.

    Completeness5/5

    The tool set provides exhaustive coverage of the Cocos Creator domain, including asset management, scene editing, physics, UI, animation, build processes, and testing. There are no obvious gaps; tools support full CRUD operations, lifecycle management, and integration with external systems like AI generation and preview interaction. The surface is complete for game development workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues