pixel-composer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PXC_DIR | No | Pixel Composer install folder | |
| PXC_DATA_DIR | No | Pixel Composer data directory (default %LOCALAPPDATA%\PixelComposer) | |
| PXC_TERMINAL_PORT | No | Port of the app's built-in Remote Terminal WebSocket server | 22400 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_projectB | Open a .pxc in Pixel Composer, launching the app if needed (a window will appear). |
| inspect_projectB | List nodes with their type, stored input values (by index) and connections. Reads the file, not the app. |
| set_inputB | Set a node input's static value in the .pxc file (node = id, iname or name). Reloads it in the app when it is the open project, so a following export uses the new value. |
| exportB | Run every Export node of the open project and wait until the output files stop changing. |
| run_commandB | Send a raw console command (e.g. 'set ', or any GML function name with space-separated args). Returns app log lines printed meanwhile (empty when attached). |
| statusA | Connection mode (launched/attached/stopped), open project and recent app log. |
| closeA | Quit Pixel Composer if this server launched it. |
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 7 tools
Most tools have clearly distinct purposes: open_project launches the app, inspect_project reads the file, set_input mutates a node value, export runs export nodes, status reports connection, close quits. The only overlapping pair is set_input vs run_command, since a raw console command could also modify values, but the descriptions clarify that set_input targets node inputs specifically.
Most names follow a verb_noun pattern (open_project, inspect_project, set_input, run_command), with minor deviations where export, status, and close are bare verbs/nouns. The convention is still predictable and readable throughout.
Seven tools is well-scoped for a Pixel Composer control server, covering lifecycle (open/close/status), inspection, mutation, and export without padding. Each tool earns its place.
Lifecycle, inspection, mutation, and export are all covered, and run_command provides an escape hatch for anything missing (node creation, connections, GML calls). Some first-class operations like creating nodes or editing connections are absent, but the console fallback mitigates this.