Canvas-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CANVAS_OUTPUT_DIR | No | Output directory for PNGs. Defaults to ~/.rhode/canvas/ |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| render_canvasA | Render a canvas diagram from a YAML recipe string. Supports hierarchical format (networks/factories/machines/nodes) or a simplified format (flat list of nodes with inputs/outputs). Returns the path to the rendered PNG file. |
| create_canvasA | Create a canvas diagram from a structured description. Provide a title, nodes, and connections — the tool handles layout and rendering. Returns the path to the rendered PNG and the generated YAML recipe. |
| list_templatesA | List available canvas recipe templates that can be used as starting points. |
| get_templateA | Get the YAML content of a specific template by name. |
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 4 tools
Each tool has a distinct purpose: creating a canvas from description, rendering from YAML, and managing templates. No overlap between tools.
All tool names consistently follow the verb_noun pattern with appropriate singular/plural forms (create_canvas, get_template, list_templates, render_canvas).
4 tools is well-scoped for a canvas diagramming server, covering creation, rendering, and template management without being too few or too many.
Core workflows are covered, but missing template creation/deletion and canvas retrieval by name are minor gaps that agents can work around.