What features does PlayCanvas MCP server provide?

Q: What features does PlayCanvas MCP server provide?

Entity management: LLM-driven operations to list, create, delete, duplicate, and modify entities; manage reparenting and components, including script component scripts.. Asset management: LLM-driven tasks for assets: list_assets, create_assets, delete_assets, instantiate_template_assets, set_script_text, script_parse, and set_material_diffuse.. Scene management: Query and modify scene settings to automate scene configuration and tuning.. Store integration: Store-related actions: store_search, store_get, and store_download to obtain assets from the PlayCanvas ecosystem.. Editor extension integration: Connect to the PlayCanvas Editor via the PlayCanvas Editor MCP Extension in the Chrome extension, interfacing through the configured port.. Run and configuration: Install dependencies and run the MCP Server (tsx server.ts) on port 52000; Windows/macOS config examples show how to wire commands.. Reliability and usage notes: Driven by Claude Desktop or Cursor; includes one-editor-at-a-time constraint and guidance to enable auto-run mode with caution; Claude Pro recommended.

PlayCanvas MCP Server 2025: Features & Setup Guide

Overview

An MCP Server for automating the PlayCanvas Editor using an LLM. This server exposes a curated set of tools that let an LLM manipulate PlayCanvas projects inside the Editor by issuing high-level commands. Core capabilities include Entity management (list, create, delete, duplicate, modify entities; reparenting; add/remove components; add script component scripts), Asset management (list, create, delete, instantiate templates, set script text, script_parse, set_material_diffuse), Scene management (query and modify scene settings), and Store operations (store_search, store_get, store_download). The server is designed to be driven by Claude Desktop or Cursor, with guidance to use Claude Pro due to chat context limits. Running instructions cover npm install, starting the server via tsx server.ts, and port 52000; Windows and macOS MCP Config JSON examples show how to wire the port and command. The PlayCanvas Editor connects to the MCP Server via a Chrome extension called PlayCanvas Editor MCP Extension, with a one-editor-at-a-time constraint. The docs also note auto-run mode in Cursor for hands-off operation and provide steps to connect the extension to the correct port. This MCP server aims to streamline iterative development and automate repetitive editor tasks through natural language or structured prompts.

Features

Entity management

LLM-driven operations to list, create, delete, duplicate, and modify entities; manage reparenting and components, including script component scripts.

Asset management

LLM-driven tasks for assets: list_assets, create_assets, delete_assets, instantiate_template_assets, set_script_text, script_parse, and set_material_diffuse.

Scene management

Query and modify scene settings to automate scene configuration and tuning.

Store integration

Store-related actions: store_search, store_get, and store_download to obtain assets from the PlayCanvas ecosystem.

Editor extension integration

Connect to the PlayCanvas Editor via the PlayCanvas Editor MCP Extension in the Chrome extension, interfacing through the configured port.

Run and configuration

Install dependencies and run the MCP Server (tsx server.ts) on port 52000; Windows/macOS config examples show how to wire commands.

Reliability and usage notes

Driven by Claude Desktop or Cursor; includes one-editor-at-a-time constraint and guidance to enable auto-run mode with caution; Claude Pro recommended.