PlayCanvas Editor MCP Server
Official PlayCanvas Editor MCP server: 130 tools for scenes, entities, scripts, assets and runtime checks with screenshots
- 151 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent edits scenes, entities and assets of the open project and can reset a branch or apply a merge
- The server listens on local port 52000 and stops any other process on that port
- Runtime tools launch the game and send input
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/playcanvas-editor-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent edits scenes, entities and assets of the open project and can reset a branch or apply a merge
- The server listens on local port 52000 and stops any other process on that port
- Runtime tools launch the game and send input
This is third-party code. Review the repository files before installing.
What it does
The PlayCanvas Editor MCP Server lets AI agents drive the PlayCanvas Editor and check that scenes actually run. The MCP client is built into the Editor itself, so no browser extension is needed. The server listens on 127.0.0.1:52000 and works with the project open in the Editor. There are 130 tools. Projects (list, create, edit description, open in the Editor), entities (reads, search, schema-safe batch edits, hierarchy, components), scripts (text reads and writes, attach, attributes), assets (reads, create, streamed upload and download up to 512 MiB, reimport), templates, animation, processing (lightmaps, atlases, cubemaps, compressed variants), scenes, settings, viewport, the editor (selection, logs, undo), builds, the Store, runtime and VCS (branches, checkpoints, merges). Runtime tools launch the game, take screenshots, read logs and state and send keyboard, mouse and touch input. Projects cannot be deleted. The server has no telemetry: the only outbound request is made by download_build to the archive URL the Editor reports.
Who it is for. Game and 3D app developers on PlayCanvas who want to hand Editor routine to an agent and verify the result by running it.
Good fit when
- A spinning cube with a rotate script must be added to a scene and verified by screenshot
- Entities and components need a batch edit by schema
- Assets must be uploaded, reimported and lightmaps processed
- A project is managed by branches and checkpoints and the agent should create them
Not a fit when
- You need to drive several Editors at once: the tools work with one connected Editor
- You need to delete a project: the server cannot
- You need minimal context: the 130 tool definitions take about 43,000 tokens unless tool search is on
Example request
Add a spinning cube with a rotate script to the current scene, launch it and capture a screenshot of the running app to confirm it turnsMCP
- Transport
- stdio
- Authentication
- not required
Limitations
Node.js 22.18 or newer is required. Add the server once per agent: two servers take turns owning the Editor port, and the server stops any other process holding port 52000. In the Editor click the MCP button below Publish and then CONNECT, and Chrome must grant the Apps on device permission. Runtime tools open a Launch window, so allow pop-ups. Tool search in Claude Code cuts the starting context to about a thousand tokens.
How to disable. For Claude Code run claude mcp remove playcanvas. For other clients delete the playcanvas entry from the MCP configuration.
FAQ
How do I connect the server to Claude Code?
Run claude mcp add playcanvas -- npx -y @playcanvas/editor-mcp-server. Then open the project in the PlayCanvas Editor, click the MCP button below Publish and CONNECT. Node.js 22.18 or newer is required.
Which port does the server use and how do I change it?
Port 52000 by default. To change it, pass --port number to the server and set the same port in the Editor.
How much context do the tools take?
The 130 tool definitions weigh about 43,000 tokens. Claude Code MCP tool search is on by default and loads only names at start, about a thousand tokens.
Does the server collect telemetry?
No. The server listens locally, touches files only for upload and download, and makes one outbound request: download_build fetches the archive URL the Editor reports.
What do the runtime tools do?
They launch the game in a Launch window, take screenshots, read logs and live state and send keyboard, mouse and touch input. This lets the agent verify that the scene works.
Discussion
No questions or reviews yet.
Related
MCP serversA Cocos Creator extension with a built-in MCP server: the agent builds UI, edits scenes and takes editor screenshots
Cocos Creator MCP Server
Cocos Creator MCP Server Plugin
An MCP server as a Cocos Creator editor extension: the agent controls scenes, nodes, components, prefabs and project assets
An MCP server inside the Unity Editor: the agent builds scenes and scripts, enters play mode and checks the game with screenshots
A Unity package: the Editor serves MCP over HTTP itself, and agents and the command line drive scenes, assets and builds
MCP for the Godot editor: an agent edits scenes, runs the game, freezes time and verifies its own work by playtest
A Cocos Creator 2.4.x plugin with a local server so an agent edits scenes, prefabs and assets and builds the project over MCP
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| PlayCanvas Editor MCP Server (this card) | yes | not required | 151 | |
| Godot MCP Toolkit | no | not required | 128 | drives the Godot editor in place of PlayCanvas |
| MCP Unity | no | not required | 2,018 | drives the Unity editor in place of PlayCanvas |
| GodotPrompter | no | 956 | a plugin with Godot prompts |
README in short
The README begins by saying the MCP server automates the PlayCanvas Editor and verifies scenes run. It then covers installation for Claude Code, Claude Desktop, Cursor and Codex, connecting in the Editor, an example prompt, a table of tool categories, context cost, data and network notes and contributor commands.