editor

This MCP server provides tooling to connect an LLM to Phaser Editor v5, enabling conversational assistance and automation within the editor's workflow. The server exposes a suite of tools grouped by functionality (IDE, Assets, Scene, and Editable Tilemap operations) that let the model inspect, modify, and manage scenes, assets, tilemaps, and related editor state without directly editing source code. It is designed to work with Phaser Editor's Scene Editor, Asset Pack Editor, and related features, and pairs with MCP hosts like Cursor or Claude Desktop to enable AI-assisted development workflows. To use it, configure your MCP host to launch the server via the recommended npm/npx package (as shown in the example) and point your prompts to the available commands (for example, ide-get-all-scenes-in-project, assets-get-available-textures, scene-get-scene-data, etc.). By invoking these tools, the model can query the current project state, fetch assets, inspect scenes, and perform editor actions in a controlled, auditable way. The tools are tailored to Phaser Editor’s data structures and workflows, so the model benefits from consistent schemas when reading and writing scene and asset information.

Prerequisites:

• Node.js and npm installed on your system (Node.js 14+ is recommended).
• Access to an MCP host (e.g., Cursor, Claude Desktop) that can reference npm/npx-based MCP servers.

Installation steps:

1. Install Node.js and npm from https://nodejs.org/ (confirm with node -v and npm -v).
2. Install or use the MCP server package via npx in your MCP host configuration. The official configuration example uses the phaser editor MCP server package name:

Example configuration (shown in README): { "mcpServers": { "phaser-editor": { "command": "npx", "args": ["@phaserjs/editor-mcp-server"] } } }

3. In your MCP host, reference the phaser-editor server entry as shown above. This will launch the MCP server that integrates with Phaser Editor v5 when the host connects to your project.
4. Ensure Phaser Editor v5 is running (the server interacts with a running Phaser Editor instance). If your host requires a ready signal, start the Phaser Editor app before enabling the MCP server.
5. Test basic commands from the MCP host UI to verify connectivity (for example, ide-get-all-scenes-in-project, scene-get-scene-data).

Notes:

• The package name to install is @phaserjs/editor-mcp-server and it is used via npx in the host configuration.
• No global install is strictly required if your host supports npm/npx execution per the example configuration.

Tips and considerations:

• The server tools are designed to work with Phaser Editor features (Scene Editor, Asset Pack Editor, etc.) and are not meant to directly modify your source code outside the editor context.
• Use Training Levels to help the model learn project structure by adding well-labeled training scenes (e.g., per-object layers with descriptive names).
• When testing, ensure Phaser Editor is running so the MCP server can communicate with its internal data structures (scenes, textures, tilemaps).
• If you encounter issues, verify the MCP host configuration matches the example: using npx to invoke @phaserjs/editor-mcp-server and exposing the phaser-editor server under mcpServers.
• Some commands can be expensive or return large payloads (e.g., listing all assets or scenes); consider paginating or filtering results if supported by your host.
• Environment variables or auth settings are generally managed by the host; if the server requires access tokens for certain assets, configure those in the host environment as needed.