home / mcp / playcanvas editor mcp server

PlayCanvas Editor MCP Server

Provides an MCP interface to automate the PlayCanvas Editor via a local runtime using Claude or Cursor.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "playcanvas-editor-mcp-server": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "tsx",
        "C:\\path\\to\\editor-mcp-server\\src\\server.ts"
      ],
      "env": {
        "PORT": "52000"
      }
    }
  }
}

You can run an MCP Server to automate the PlayCanvas Editor using an LLM, enabling scripted editing capabilities, asset and scene management, and more through a single configurable endpoint.

How to use

Connect your MCP client to the local MCP Server and issue commands to manage entities, assets, scenes, and store data. The server exposes a set of tools that let you list, create, modify, and delete entities and assets, query and adjust scene settings, and perform store operations. When you initiate the server, it listens on a configured port and accepts orchestration commands from your chosen MCP client (such as Claude Desktop or Cursor). You can drive the server from an LLM-enabled workflow to automate repetitive editor tasks, implement templates, and run custom editor scripts.

How to install

Prerequisites: You need Node.js and npm installed on your machine.

1. Install required dependencies.

npm install

2. Install the Chrome extension for the PlayCanvas Editor (optional for workflow integration). Enable Developer mode in Chrome and load the unpacked extension from the extensions folder.

3. Start the MCP Server using one of the supported local MCP runners (Cursor or Claude Desktop). Follow the dedicated setup for your chosen runner to create the MCP config and launch the server.

Configuration and connection notes

The MCP Server is designed to be driven by Claude Desktop or Cursor. Claude Desktop is generally more reliable for long-running sessions, and Cursor offers convenient in-editor management. You will configure the MCP endpoint in a local JSON file that describes how to start the server and on which port it listens.

To connect the editor client to the MCP Server, open the PlayCanvas Editor in a Chrome tab, access the extension popup via the Extensions icon, and choose CONNECT with the port matching your MCP Config settings. You can connect only one PlayCanvas Editor instance at a time.

MCP Config JSON (examples)

The following configurations show how to run the local MCP server from a standard setup.

{
  "mcpServers": {
    "playcanvas": {
      "command": "npx",
      "args": [
        "tsx",
        "/path/to/mcp-editor/src/server.ts"
      ],
      "env": {
        "PORT": "52000"
      }
    }
  }
}

Multiple startup methods (per platform)

Windows and macOS start commands differ slightly but lead to the same runtime target. Use the appropriate configuration block for your environment.

// Windows
{
  "mcpServers": {
    "playcanvas": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "tsx",
        "C:\\path\\to\\mcp-editor\\src\\server.ts"
      ],
      "env": {
        "PORT": "52000"
      }
    }
  }
}
```
```json
// macOS
{
  "mcpServers": {
    "playcanvas": {
      "command": "npx",
      "args": [
        "tsx",
        "/path/to/mcp-editor/src/server.ts"
      ],
      "env": {
        "PORT": "52000"
      }
    }
  }
}

Available tools

Entity

Manipulate PlayCanvas entities with actions to list, create, delete, duplicate, modify, reparent, and assign components including script components.

Asset

Manage assets by listing, creating, deleting, instantiating templates, and updating scripts or materials.

Scene

Query and modify scene-wide settings to adjust how the editor renders and behaves.

Store

Interact with a store for searching, retrieving, and downloading assets or templates.

Viewport

Capture and focus the editor viewport for targeted actions and visual feedback.