PlayCanvas Editor MCP Server
OfficialRelated Servers
Alternatives to PlayCanvas Editor MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to automate the PlayCanvas Editor directly through its built-in MCP client, covering projects, entities, scripts, assets, scenes, builds and version control. Agents can also launch the running app to capture screenshots, read logs, inspect live state and simulate input, verifying that scenes actually work.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to automate the PlayCanvas Editor through a built-in MCP client, with no browser extension needed. Provides tools for entities, scripts, assets, scenes, templates, animation, builds, store imports, viewport and editor control, plus runtime launching with screenshots, logs and input to verify that projects actually run.-
- FlicenseNot gradedqualityAmaintenanceLets AI agents drive the PlayCanvas Editor directly—creating and editing entities, scripts, assets, templates, animations, scenes, builds, and version control—and then launch the project to verify it actually runs. It also covers project management, viewport control, runtime input, logs, and screenshots, with the MCP client built into the Editor so no browser extension is needed.-
- AlicenseNot gradedqualityDmaintenanceUnity MCP Server enables LLM-based clients to automate the Unity Editor, including scene manipulation, UI testing, input simulation, and code editing.34MIT
- AlicenseDqualityDmaintenanceAn MCP server that enables LLMs to 'see' what's happening in browser-based games and applications through vectorized canvas visualization and debug information.13 npm54MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that helps novice developers deploy web applications through conversational interfaces, bridging the gap between LLMs and various hosting environments.1MIT
TDQS
Scored across 125 tools
Most tools have distinct operations and include explicit "When NOT to use" cross-references, so an agent can usually tell them apart. Minor overlap remains among entity lookup tools (search_entities vs resolve_entities vs find_entities_by_script vs list_entities), script attachment tools (attach_script vs add_entity_scripts vs add_script_component_script), and generic vs scoped settings tools (query_settings vs query_project_settings).
The dominant pattern is snake_case verb_noun (create_entities, modify_assets, list_builds), which is predictable. Exceptions like vcs_status, script_parse, launch_start, my_assets_import, and the awkward add_script_component_script break strict consistency but remain readable.
125 tools is far beyond the 50+ threshold for extreme mismatch with a single MCP server. Even for a large domain like a full game editor, this should be split into focused sub-servers or consolidated to reduce discovery and selection overhead.
The surface covers full lifecycle coverage for scenes, entities, components, assets, scripts, materials, animations, VCS branches/checkpoints/merges, builds, runtime, viewport, settings, and external asset stores. No obvious dead ends exist for the stated PlayCanvas Editor domain.