Pixelorama MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PIXELORAMA_MCP_PORT | No | The port the Pixelorama extension listens on (default is 7651). Set this for the server to change it, and set PORT inside the extension's Main.gd to match. | 7651 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_projectA | Describe the project open in Pixelorama: size, frames, layers and the current cel. |
| new_projectB | Create a new, empty project in a new tab and switch to it. |
| open_fileA | Open a .pxo project or an image (png, jpg, webp, bmp, tga) in a new tab. |
| draw_pixelsA | Draw pixels from a character grid. Each string in rows is one row of pixels; each character is looked up in palette. Characters that are not in the palette (such as '.') leave the pixel unchanged, so map a character to "transparent" to erase. Example: palette {"o": "#e8a33d", "d": "#7a4a12"}, rows [".oo.", "oddo", ".oo."]. The whole call is one undo step in Pixelorama. |
| fill_rectA | Fill a rectangle with one color. Leave out the position and size to fill the whole canvas. |
| clear_celB | Erase every pixel of one cel (a layer in a frame). |
| read_pixelsB | Read pixels of one cel as a character grid with a palette, in the same format draw_pixels takes. '.' is transparent. At most 16384 pixels per call. |
| get_imageA | Show a frame with all visible layers blended, scaled up with nearest-neighbour so pixels stay sharp. |
| add_layerB | Add a pixel layer. By default it goes on top of all layers. |
| add_frameA | Add an empty frame. By default it goes after the last frame. |
| select_celC | Make a frame/layer the current one in Pixelorama. |
| save_projectA | Save the current project as a .pxo file. Without a path it saves to where it was last saved. |
| export_pngA | Export the current frame, or all frames as a horizontal sprite sheet, to a PNG file. Layers are blended the same way Pixelorama shows them. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool maps to a distinct action (draw, read, fill, clear, export, select), and descriptions clarify boundaries well. The only mild overlap is get_project (metadata description) versus get_image (rendered preview), but their descriptions make the distinction clear.
All 13 tools use a consistent snake_case verb_noun pattern (get_project, add_layer, draw_pixels, export_png, save_project). No mixing of conventions or vague single-word names.
13 tools sits squarely in the ideal 3-15 range and each one covers a distinct editing or project operation. Nothing feels padded or missing from a count perspective.
Project lifecycle (new/open/save/export) and drawing/reading are well covered, but the surface is create-only for structure: add_layer and add_frame exist with no delete_layer or remove_frame, and there is no layer/frame reordering, visibility, or undo control. Agents will hit dead ends when they need to remove or reorder content.