Skip to main content
Glama
iEfoam

CocosMCP

by iEfoam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to CocosMCP

No user-submitted related servers found.

    Related Servers

    • cocos-mcp-community

      chang0022
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to inspect and operate the Cocos Creator project currently open, including scenes, nodes, assets, animations, and editor workflows via MCP.
      MIT

    • Cocos Creator MCP Server

      557888-pixel
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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.
      -

    • cocos-mcp

      az198071123
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets 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.
      13 npm
      MIT

    • cocos-mcp-server

      caravanglory
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables 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.
      17 npm
      40
      MIT

    • DC-COCO-MCP

      dudachun
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to control Cocos Creator editor projects, scenes, nodes, components, assets, Prefabs, building, and diagnostics via the MCP protocol.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 35 tools

    Disambiguation5/5

    每个工具都有明确的目标资源与操作，尽管数量多但描述清晰区分，如实例与运行时实例、场景与节点等边界明确。几乎不存在重叠或模糊的工具。

    Naming Consistency4/5

    所有工具统一以cocos_为前缀，并采用“域_动作”或“动作_域”的混合模式，如cocos_build_cancel、cocos_scene_query。少数工具如cocos_projects、cocos_instances省略了动词，但整体风格一致，可视为list的简写。

    Tool Count4/5

    35个工具数量偏多，但覆盖构建、场景、节点、组件、资源、工作流等多个独立领域，每个工具都有明确用途，没有冗余。对于Cocos开发这样复杂的域，数量合理。

    Completeness3/5

    覆盖了构建、场景操作、节点与组件操作、资源导入与查询、UI构建、场景验证等核心流程，但缺少删除节点/组件、创建新场景、删除资源等操作，存在明显缺口，agent可能无法完成完整的生命周期管理。

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources