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-mcp-pro

      AzusaSubaru
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      1
      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.
      11 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.
      21 npm
      44
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.4/5.0

    Scored across 36 tools

    Disambiguation3/5

    Most tools are scoped by domain (build/scene/node/asset/runtime) and are individually clear, but cocos_capability_execute overlaps with dedicated asset-organize tools, and pairs like cocos_instances/cocos_runtime_instances and build_status/workflow_status require careful reading to avoid misselection.

    Naming Consistency4/5

    The cocos_<domain>_<action|noun> convention is consistent and readable, with clear verb suffixes like start/query/create/set/add. Minor deviations such as cocos_projects, cocos_build_logs, and cocos_assets vs cocos_asset prevent a perfect score.

    Tool Count2/5

    At 36 tools, the surface is above the 25+ threshold and will add measurable selection overhead for agents. Although the Cocos domain is broad, several query/status/planning helpers could be consolidated.

    Completeness3/5

    The set covers build, scene, node/component, asset, runtime, and workflow/capability well, but lacks obvious destructive/removal operations such as node removal, component removal, and asset deletion. The ui_build tool also expects a plan without a corresponding ui planning tool, leaving a workflow gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources