pixel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXPORT_DIR | No | Directory for exported PNGs (defaults to current working directory) |
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 |
|---|---|
| create_canvasA | Create a new named canvas with given dimensions. If a canvas with this name exists, it is replaced. |
| list_canvasesA | List all active canvases with their dimensions. |
| set_pixelB | Set a single pixel on the canvas. |
| get_pixelB | Get the color of a single pixel. |
| fill_rectB | Fill a rectangle with a solid color. |
| draw_lineA | Draw a line between two points using Bresenham's algorithm. |
| clearB | Clear the entire canvas to a color (default: transparent). |
| export_pngB | Export a canvas to a PNG file. |
| undoC | Undo the last drawing operation on a canvas. |
| redoA | Redo the last undone operation on a canvas. |
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 10 tools
Each tool targets a distinct canvas operation: creation, listing, pixel access, shape drawing, clearing, export, and history control. There is no meaningful overlap or ambiguity between tool purposes.
Most tools follow a clear verb_noun pattern like create_canvas, set_pixel, and export_png. A few names like clear, undo, and redo omit an object, but they are still conventional and readable.
Ten tools is a well-scoped size for a pixel-art canvas server. Each tool covers a necessary part of the drawing workflow without unnecessary bloat or missing essentials.
The core canvas lifecycle is covered: create, list, draw, manipulate pixels, export, and undo/redo. A notable minor gap is the lack of an explicit delete_canvas operation, especially since canvases are described as 'active'.