Phaser Editor MCP Server
OfficialProvides specialized tools for managing and inspecting Spine skeletal animations within the editor, including the ability to list skeletons and atlases, retrieve skeleton-specific metadata such as animations and skins, and access skin images.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Phaser Editor MCP Server List all scenes and available textures in the project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server for Phaser Editor v5
This Model Context Protocol (MCP) server provides the tools to connect an LLM with Phaser Editor v5. It is designed to work seamlessly with Phaser Editor's IDE features, allowing developers to create and manage game scenes efficiently.
Installation
This server is available as an NPM package and you can use it in the configuration of MCP hosts like Cursor, Claude Desktop, GitHub Copilot, etc...
This is an example of a configuration file for Cursor:
{
"mcpServers": {
"phaser-editor": {
"command": "npx",
"args": ["@phaserjs/editor-mcp-server"]
}
}
}This servers connects with a running instance of the Phaser Editor v5 desktop application. All changes on the project are made through the Phaser Editor running instance.
Related MCP server: glade-mcp
Coding
All tools provided by this server are specifically tailored to work with Phaser Editor features, such as the Scene Editor, Asset Pack Editor, and others. These tools are not intended for direct modification of your project's source code. However, when used alongside code editors like Cursor, the server enables simultaneous interaction with both Phaser Editor's custom files and the project's source code—creating a powerful, integrated development workflow.
We recommend starting with one of the Phaser Editor project templates, which are preconfigured for seamless integration with Cursor. These templates include all necessary configurations and the rules for the LLMs to understand how to interact with Phaser Editor's custom files and the project's source code.
Using Training Levels to Enhance LLM-Based Content Generation
Large Language Models (LLMs) excel at generating new content when provided with high-quality, contextual examples. This is especially effective for game level generation. To take full advantage of this capability, it's a good practice to create training levels that clearly express the concepts and elements you want the model to replicate.
Why Training Levels Matter
Training levels serve as concrete examples that define the structure and logic of your game. These examples help the LLM understand the components involved and how they interact, enabling it to generate new levels that align with your design.
For example, if you're working with tilemap-based levels, you can create a TrainingLevel scene that includes the key objects used in your game. To improve clarity and semantic understanding:
Use one layer per object.
Name each layer with a descriptive identifier, such as
pipe,cloud, ormountain.
This organization helps the LLM detect patterns and apply them to new content generation tasks.
Visual Tools Help—but Context is Key
The MCP server provides tools to inspect texture images and generate scene "screenshots." While these visuals are helpful, they may not always be sufficient for the LLM to fully grasp the game's context and logic.
That's why creating structured and well-labeled training levels is essential. These levels provide a richer, more actionable context that enhances the model's ability to generate accurate and relevant game content.
Tools Overview
This project provides a comprehensive set of tools for managing scenes, assets, tilemaps, animations, and more within the Phaser Editor environment. Below is a summary of all available tools, grouped by their main functionalities.
IDE Tools
ide-get-all-scenes-in-project: Lists all scenes in the project.
ide-get-active-scene: Gets the currently focused scene in the editor.
ide-open-scene: Opens a scene in the editor.
ide-create-new-scene: Creates a new scene file.
ide-save-scene: Saves the editor state of a scene.
Assets Tools
assets-get-available-textures: Lists all available textures in the project.
assets-get-texture-binary: Gets the binary data of a texture.
assets-get-available-bitmapfonts: Lists all available bitmap fonts.
assets-get-bitmapfont-image: Gets the PNG image/texture of a bitmap font.
assets-get-spritesheet-image: Gets the PNG image/texture of a spritesheet.
assets-get-texture-content-bounding-box: Gets the bounding box of a texture's content.
assets-get-available-animations: Lists all available sprite animations.
assets-get-available-spine-skeletons: Lists all Spine skeletons in the project.
assets-get-available-spine-atlases: Lists all Spine atlases in the project.
assets-get-spine-skeleton-info: Gets info (animations and skins) for a Spine skeleton.
assets-get-spine-skin-image: Gets the PNG image of a Spine skin.
assets-get-available-tilemaps: Lists all available Tiled tilemap files.
assets-get-tilemap-data: Gets the data of a Tiled tilemap file.
Scene Tools
scene-clear-scene: Clears the current scene.
scene-get-scene-dimension: Gets the dimensions of the current scene.
scene-get-screenshot: Gets a screenshot of the scene.
scene-get-scene-data: Gets all objects in the current scene, including their properties.
scene-move-game-object-in-render-list: Sorts objects in the current scene.
scene-delete-game-objects: Deletes specified game objects from the scene.
scene-move-game-objects-to-parent: Moves objects to a specified parent.
scene-pack-objects-in-container: Groups objects in a container.
scene-delete-plain-objects: Deletes specified plain objects from the scene.
scene-add-game-objects: Adds multiple new game objects to the scene.
scene-update-game-objects: Updates multiple game objects in the scene.
scene-add-plain-objects: Adds multiple new plain objects to the scene.
scene-update-plain-objects: Updates multiple plain objects in the scene.
Editable Tilemap Tools
scene-add-editable-tilemap: Adds a new editable tilemap to the scene. Editable tilemaps are fully modifiable and represented as plain objects.
scene-add-tileset-to-editable-tilemap: Adds a tileset to an editable tilemap and updates tile IDs in all layers.
scene-delete-tileset-from-editable-tilemap: Removes a tileset from an editable tilemap and updates tile IDs in all layers.
scene-add-editable-tilemap-layer: Adds a new layer to an editable tilemap and the scene.
scene-resize-editable-tilemap-layer: Resizes an editable tilemap layer's data.
scene-write-editable-tilemap-layer-data: Updates part of the tile data in a layer for efficient changes.
scene-fill-editable-tilemap-layer-data: Fills a region of a layer with a single tile ID.
scene-get-editable-tilemap-layer-selection-data: Retrieves selected tile data from a layer as a 2D array.
Available Tools
61 toolsassets-add-google-font-to-asset-packA
Add a Google Font configuration to the given asset pack. This is required if you want to use the font in a scene text.
Inputs: key (required), family (required), assetPackFileName (required), url.
assets-get-available-animationsA
Get all available sprite animations in the project.
Inputs: no named parameters.
assets-get-available-asset-packsA
Get all available asset packs in the project. An asset pack is a collection of assets, like images, audio files, and other resources that can be used in the game. The asset pack contains information like the key of the assets, the url to the file, and other parameters.
Inputs: no named parameters.
assets-get-available-bitmapfontsA
Get all available bitmap fonts in the project.
Inputs: no named parameters.
assets-get-available-spine-atlasesA
Get the all the Spine atlases in the project.
Inputs: no named parameters.
assets-get-available-spine-skeletonsA
Get the all the Spine skeletons in the project. It only returns the key of the skeleton.
Inputs: no named parameters.
assets-get-available-texturesA
Get all available textures in the project. It includes the name of the texture and the size.
Inputs: no named parameters.
assets-get-available-tilemapsA
Search for the available Tiled tilemap files in the asset packs and return the list of tilemap keys. A Tiled tilemap file contains the data of a tilemap. It is used by the scene editor to create the Tilemap and TilemapLayer objects. These maps are created by the third party tool Tiled. Like the other assets in the asset packs, Phaser Editor uses the tilemap key to identify the tilemap.
Inputs: no named parameters.
assets-get-bitmapfont-imageA
Get the PNG image/texture of the given bitmap font.
Inputs: key (required).
assets-get-google-font-familiesB
Gets the Google Fonts list of families. It connects to Google API and get the list. This method doesn't provide the fonts available in the project. To see the fonts in the project, check the fonts in the asset packs.
Inputs: filter.
assets-get-google-font-infoA
Gets the Google Fonts info for a given font family.
Inputs: family (required).
assets-get-spine-skeleton-infoA
Get the skeleton info (animations and skins) of the given Spine skeleton key. To build the info of a skeleton it requires also the Spine atlas key. The user can select a different atlas key, but it is common that the user also define a 'preview' atlas key for each skeleton. You can use it if it exists or ask for a different atlas key to the user.
Inputs: dataKey (required), atlasKey (required).
assets-get-spine-skin-imageB
Get the PNG image of the given Spine skin. You can use this tool to get a better understanding of the appearance of a Spine skeleton with a given skin. The image may be scaled or not. You can the skeleton data to get more info about the size of a skeleton.
Inputs: dataKey (required), atlasKey (required), skinName (required), animationName (required).
assets-get-spritesheet-imageC
Get the PNG image/texture of the given spritesheet. You can use this tool to get a better understanding of the position of tiles/frames.
Inputs: key (required).
assets-get-texture-binaryD
Get the size of the texture. If you need to get the real size of the object inside the texture (without the transparent margin), then you can use the assets-get-texture-content-bounding-box tool.
Inputs: texture.
assets-get-texture-content-bounding-boxA
Get the bounding box of the content of the given texture. Many textures has transparent padding but we need the exact offset and size of the content/object of the texture to place them in the right positions in the scene. Like when placing different objects one next to the other, with touching edges. If you need to know the size of the whole image, use the assets-get-texture-size tool.
Inputs: texture.
assets-get-texture-sizeD
Get the binary data of a texture.
Inputs: texture.
assets-get-tilemap-dataA
Get the data of a Tiled tilemap file. It returns the data of the tilemap, including the layers, tilesets, and objects. The data is used by the scene editor to create the Tilemap and TilemapLayer objects.
Inputs: key (required).
get-system-instructionsA
Get the system instructions. This is fully required for the LLM to know how to build the arguments of this MCP server tools. Tools like scene-add-game-objects, scene-update-game-objects, scene-add-game-object-filters, scene-update-game-object-filters, scene-add-plain-objects, and scene-update-plain-objects requires that the LLM get the system instructions first to know the tool arguments structure.
Inputs: no named parameters.
ide-create-new-prefab-sceneA
Create a new special scene that is a prefab. A prefab is a scene with a single game object (the prefab object) and its children. You can create a prefab instance and add it to a scene or another prefab. That's the idea of prefabs, create reusable objects. It is very common to create a prefab for every entity of the game, like the player, the different enemies, non-player characters, platforms, collectibles and many more. A prefab scene is compiled as a subclass of a game object, not as a Phaser.Scene. You can think about a prefab as a custom game object class. Even, you can create a prefab that is variant of another prefab. This means, a prefab that inherits another prefab. To create a prefab variant, just use another prefab instance as root of the prefab scene, as prefab object. This tool only creates an empty prefab scene, you must add the prefab object to the scene, immediately. The goal of a prefab is to instantiate and add it to other scenes.
Inputs: name (required).
ide-create-new-sceneA
Create a new scene file. This tool only creates a new scene. If the user wants to show the scene in the game then the user has to add the scene first to the game instance.
Inputs: name (required).
ide-get-active-sceneB
Get the scene has the focus in the editorÍ. The active scene is the one the user is working at the moment. It may be happen there isn't an active scene.
Inputs: no named parameters.
ide-get-all-prefabs-in-projectA
Get all prefabs in the project.
Inputs: no named parameters.
ide-get-all-scenes-in-projectB
Get all scenes in the project.
Inputs: no named parameters.
ide-get-prefab-inheritanceB
Get an array of all the prefabs that are part of the inheritance of the given prefab. A prefab can inherit another prefab. We call it a prefab variant. If the result is an empty array it means the given prefab is not a variant any other prefab.
Inputs: prefabId (required).
ide-open-sceneC
Open the scene in the editor.
Inputs: sceneId (required).
ide-save-sceneB
Save the the editor of the given scene. When the scene is saved, the editor generates its code. Use this tool to sync the scene with the code it represents. It is important to keep both the scene content and the scene's code file in sync if you are working in both files at the same time. Also, it is very important that you save prefab scenes after changing them, so the changes can be propagated in all the scenes that contains the instances of the prefab.
Inputs: sceneId (required).
scene-add-editable-tilemapB
Add an editable tilemap to the scene. An editable tilemap is different to a Tiled map because all the data can be edited by the user in the scene editor. However, it follows many of the concepts of Tiled. The editable tilemap is also a plain object so you can manipulate it using most of the plain object tools.
Inputs: label (required), width (required), height (required), sceneId (required), +3 more.
scene-add-editable-tilemap-layerB
Add an editable tilemap layer to an editable tilemap. Because the complexity of the editable tilemaps, we provide a couple of dedicated tools. An editable tilemap is different to a Tiled map because all the data can be edited by the user in the scene editor. This method adds a layer to the tilemap data but also it adds an EditableLayer game object to the scene.
Inputs: layer (required), sceneId (required), tilemapId (required).
scene-add-game-object-filtersC
Add multiple filters to parent game objects in the scene
Inputs: objects (required), sceneId (required).
scene-add-game-objectsA
Add multiple new game objects to the scene. If you are adding prefab instances, then you should include the "unlock" property which contains an array of the name of the properties you are setting to the object. By default, are properties are locked in a prefab instance, so you need to unlock them before setting them, otherwise, the prefab instance will get the values defined originally in the prefab scene.
Inputs: objects (required), sceneId (required).
scene-add-object-listB
Create an Object List, which is an array with the ids of game objects. The user can use this array to group objects for a purpose. One of the most common purpose of objects lists are grouping the objects to be part of an arcade physics colliders.
Inputs: lists (required), sceneId (required).
scene-add-plain-objectsC
Add multiple new plain objects to the scene.
Inputs: objects (required), sceneId (required).
scene-add-tileset-to-editable-tilemapA
Add a tileset to an editable tilemap. This will add the tileset to the tilemap data, but it will not add the tileset asset itself. It also will update the ID of the tiles of every layer in the map.
Inputs: sceneId (required), tileset (required), tilemapId (required).
scene-clear-sceneC
Clear the current scene.
Inputs: sceneId (required).
scene-declare-prefab-propertyC
Create a new user property for the given prefab.
Inputs: name (required), type (required), label (required), sceneId (required), +4 more.
scene-delete-game-object-filtersB
Delete the given filters from the scene.
Inputs: sceneId (required), filterIds (required).
scene-delete-game-objectsB
Delete the given game objects from the scene.
Inputs: sceneId (required), objectIds (required).
scene-delete-plain-objectsC
Delete the given plain objects from the scene. Plain objects are Tilemap, Key, Collider...
Inputs: sceneId (required), objectIds (required).
scene-delete-prefab-propertyB
Delete a user property from the given prefab.
Inputs: name (required), sceneId (required).
scene-delete-tileset-from-editable-tilemapA
Delete a tileset from an editable tilemap. This will remove the tileset from the tilemap data, but it will not delete the tileset asset itself. It also will update the ID of the tiles of every layer in the map.
Inputs: sceneId (required), tilemapId (required), tilesetName (required).
scene-disable-arcade-physics-bodyB
Removes the Arcade physics body from the given game objects.
Inputs: ids (required), sceneId (required).
scene-enable-arcade-physics-bodyA
Adds an Arcade physics body to the given game objects. To set the physics body properties you first have to create the body with this tool.
Inputs: sceneId (required), updates (required).
scene-fill-editable-tilemap-layer-dataA
Fill a region of the tile data of an editable tilemap layer with a single tile ID. This is useful to do things like clear the layer (fill the full layer with a -1 tile), or to paint backgrounds, filling the layer with the background tile, or filling just a part of the layer like for making a floor, or any other level element.
Inputs: x (required), y (required), width (required), height (required), +3 more.
scene-get-editable-tilemap-layer-selection-dataA
Get the selected tile data of an editable tilemap layer. It returns a 2D array with the tile IDs. The selection is always a rectangular region of the tilemap layer.
Inputs: sceneId (required).
scene-get-nested-prefabs-instancesA
Get all the nested prefab instances of the given prefab instance. A prefab instance can have other prefab instances as children that are exposed as nested prefab instances. This tool returns all the nested prefab instances, not the direct children. You can use this tool to get the info of the nested prefab instances and perform operations like updating the nested prefabs or, in case they are containers-like objects, add objects to them. You cannot delete a nested prefab instance. A nested prefab instance also have a prefabId that points to an object inside the root prefab. You can modify a nested prefab instance just like any other prefab instance, you have to provide the id, the values of the properties, and update the unlock field. Each nested prefab instance contains its own data.
Inputs: id (required), sceneId (required).
scene-get-objects-dataC
Get the data of the given objects
Inputs: sceneId (required), objectIds (required).
scene-get-scene-dataA
Get all objects in the current scene, including their properties.
Inputs: sceneId (required).
scene-get-scene-dimensionC
Get the dimensions of the current scene.
Inputs: sceneId (required).
scene-get-screenshotC
Get a screenshot of the scene.
Inputs: x (required), y (required), width (required), height (required), +1 more.
scene-move-game-object-in-render-listC
Sort objects in the current scene.
Inputs: move (required), sceneId (required), objectIds (required).
scene-move-game-objects-to-parentC
Move the given objects to the given parent.
Inputs: sceneId (required), objectIds (required), parentId.
scene-pack-objects-in-containerA
Create a container to group the given objects. The container and objects are positioned so the container size is minimal.
Inputs: sceneId (required), objectIds (required).
scene-remove-object-listB
Remove an Object List from the scene.
Inputs: listIds (required), sceneId (required).
scene-resize-editable-tilemap-layerA
Resize an editable tilemap layer. This will resize the layer data, but it will not resize the layer game object itself. It also will update the ID of the tiles of every layer in the map.
Inputs: width (required), height (required), layerId (required), sceneId (required).
scene-update-game-object-filter-listC
Update the list where the filter is placed. A filter could be on the internal or external filter list. The internal filters are rendered in the game object space. The external filters are rendered in the camera space.
Inputs: sceneId (required), filterId (required), internal (required).
scene-update-game-object-filtersD
Add multiple filters to parent game objects in the scene
Inputs: objects (required), sceneId (required).
scene-update-game-objectsA
Update multiple game objects in the scene. If you are updating prefab instances, then you should include the "unlock" property which contains an array of the name of the properties you are setting to the object. By default, are properties are locked in a prefab instance, so you need to unlock them before setting them, otherwise, the prefab instance will get the values defined originally in the prefab scene. It is important that you be smart when setting the unlock property, because its value will override the unlock state of the object. This means, if you are going to update a property but want to keep the values of the other properties unlocked in the prefab instance then you have to include them in your update arguments.
Inputs: objects (required), sceneId (required).
scene-update-object-listC
Update an Object List, which is an array with the ids of game objects.
Inputs: id (required), sceneId (required), objectIds (required), label, +1 more.
scene-update-plain-objectsC
Update multiple plain objects in the scene.
Inputs: objects (required), sceneId (required).
scene-write-editable-tilemap-layer-dataA
Write part of the tile data of an editable tilemap layer. This is useful to update a layer's data without having to send the whole layer data again.
Inputs: x (required), y (required), data (required), layerId (required), +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 61 tools
Each tool has a clear, distinct purpose, with domain prefixes (assets, ide, scene) and specific actions. Despite the large number, there is no overlap in functionality; every tool targets a unique operation on a specific resource type.
All tool names follow the consistent pattern of <domain>_<action>_<object> in snake_case, such as 'assets-add-google-font-to-asset-pack' and 'scene-delete-game-objects'. The naming is uniform and predictable.
With 61 tools, the server is extremely heavy. This far exceeds the typical well-scoped range (3-15) and even the 'too many' threshold of 25+, making it overwhelming for an agent to navigate efficiently.
The tool set provides comprehensive coverage of the Phaser Editor domain, including asset management, scene creation/editing, prefab handling, tilemap operations, physics bodies, and object lists. All common lifecycle operations (create, read, update, delete) are present.
Maintenance
Related MCP Connectors
Let your coding agent read your GameSalad projects, and edit them live in Creator on Pro and Edu.
Pixel art for your game, from your coding agent. Generate sprites, items and tiles in your game's style (64 to 1024 px), make variants, reskins and N/E/S/W directions, then edit everything in a full pixel art editor that syncs into your project. Works with Claude, Claude Code, Cursor and ChatGPT; sign in with OAuth, no API key.
Create and edit PlayableMaker playable ads from chat and download them as projects.
Make games with AI: one MCP server that connects your agent to Unity, Unreal and Godot editors.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to control Cocos Creator game development directly within the engine, providing tools for node manipulation, asset management, scene operations, and AI-powered image generation.-

glade-mcpofficial
AlicenseNot gradedqualityBmaintenanceConnect any MCP-compatible AI client (Claude Code, Cursor, Windsurf) to Unity or Godot. 300+ granular tools, an editor aware system prompt, game design document project context, script semantic search, and skill calibration.205MIT- AlicenseBqualityBmaintenanceEnables AI assistants to automate the Godot Engine editor, including scene authoring, node transforms, tilemap editing, animation, shaders, and live GDScript execution via MCP.10030MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to launch a game engine editor, run and debug projects, capture console output, and manage scenes, nodes, sprites, and UIDs.14MIT