Editor Mcp Server

██████╗ ██╗      █████╗ ██╗   ██╗ ██████╗ █████╗ ███╗   ██╗██╗   ██╗ █████╗ ███████╗
██╔══██╗██║     ██╔══██╗╚██╗ ██╔╝██╔════╝██╔══██╗████╗  ██║██║   ██║██╔══██╗██╔════╝
██████╔╝██║     ███████║ ╚████╔╝ ██║     ███████║██╔██╗ ██║██║   ██║███████║███████╗
██╔═══╝ ██║     ██╔══██║  ╚██╔╝  ██║     ██╔══██║██║╚██╗██║╚██╗ ██╔╝██╔══██║╚════██║
██║     ███████╗██║  ██║   ██║   ╚██████╗██║  ██║██║ ╚████║ ╚████╔╝ ██║  ██║███████║
╚═╝     ╚══════╝╚═╝  ╚═╝   ╚═╝    ╚═════╝╚═╝  ╚═╝╚═╝  ╚═══╝  ╚═══╝  ╚═╝  ╚═╝╚══════╝

███╗   ███╗ ██████╗██████╗        ███████╗███████╗██████╗ ██╗   ██╗███████╗██████╗ 
████╗ ████║██╔════╝██╔══██╗       ██╔════╝██╔════╝██╔══██╗██║   ██║██╔════╝██╔══██╗
██╔████╔██║██║     ██████╔╝       ███████╗█████╗  ██████╔╝██║   ██║█████╗  ██████╔╝
██║╚██╔╝██║██║     ██╔═══╝        ╚════██║██╔══╝  ██╔══██╗╚██╗ ██╔╝██╔══╝  ██╔══██╗
██║ ╚═╝ ██║╚██████╗██║            ███████║███████╗██║  ██║ ╚████╔╝ ███████╗██║  ██║
╚═╝     ╚═╝ ╚═════╝╚═╝            ╚══════╝╚══════╝╚═╝  ╚═╝  ╚═══╝  ╚══════╝╚═╝  ╚═╝

An MCP Server for automating the PlayCanvas Editor using an LLM.

The MCP client is built into the PlayCanvas Editor — no browser extension is needed. Install the server into your MCP client of choice (Claude Code, Codex, Claude Desktop, Cursor, …) and connect the Editor to it.

Available Tools

• Entity
  • list_entities
  • resolve_entities
  • create_entities
  • delete_entities
  • duplicate_entities
  • modify_entities
  • reparent_entity
  • add_components
  • remove_components
  • add_script_component_script
  • attach_script
• Asset
  • list_assets
  • create_assets
  • delete_assets
  • instantiate_template_assets
  • set_script_text
  • script_parse
  • set_material_diffuse
  • set_material_properties
• Scene
  • query_scene_settings
  • modify_scene_settings
• Store
  • store_search
  • store_get
  • store_download
• Viewport
  • capture_viewport
  • focus_viewport
• Runtime (live Launch instance)
  • launch_start
  • launch_stop
  • capture_runtime
  • read_runtime_logs
  • inject_input

Runtime Tools

The runtime tools drive a real Launch instance (the editor's Launch button) so you can verify that a scene actually runs, not just how it looks at edit time:

• launch_start opens https://launch.playcanvas.com/<sceneId>?debug=true in a new window. The editor hands the MCP port to the launch page, which connects back to the MCP server as the "runtime" peer. launch_start returns { url, sceneId, ready }.
• capture_runtime screenshots the running app (scripts/physics/animation active).
• read_runtime_logs returns the app's console output + uncaught exceptions/rejections (newest first, paginated; defaults to warnings + errors).
• inject_input dispatches keyboard / mouse / touch events to the running app (e.g. hold W for 500ms, click at a canvas coordinate, tap the screen), so you can drive end-to-end interactions and then verify with capture_runtime.
• launch_stop closes the launch window.

Notes:

• Allow pop-ups for the editor origin, otherwise launch_start cannot open the window.
• The launch page uses your existing PlayCanvas login session (same browser), so no extra auth step is needed.

Response Format

Every tool returns a single, consistent envelope so agents can pattern-match on a stable shape:

{
  "data": <result> | null,   // business payload; an empty set is [], never an error
  "meta": {
    "tool": "entities:list",
    "status": "ok" | "error",
    "message": "...",          // present only on error; actionable, with a recovery hint
    // list tools also include pagination metadata:
    "total": 120, "count": 50, "hasMore": true, "nextCursor": "50"
  }


... [View full README on GitHub](https://github.com/playcanvas/editor-mcp-server#readme)