Skip to main content
Glama
charlieellington

design-canvas-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_routesA

List all routes currently displayed on the Design Canvas. Returns each route's ID, path, viewport dimensions (width × height), and canvas position.

USAGE: Call this before removing routes (you need the route ID for precise removal) or before adding routes (to avoid duplicates). Route IDs are stable — use them to reference specific frames.

add_routeA

Add a web page route to the Design Canvas. The route is loaded from the connected dev server and displayed as a live frame on the infinite canvas. Returns the route ID for future reference.

CONSTRAINTS:

  • Path must start with '/' (e.g., '/dashboard', '/settings', '/blog/[slug]')

  • Do not pass full URLs — the dev server base URL is configured in the app

  • Use standard responsive widths: 1280 desktop (default), 768 tablet, 375 mobile

  • Position (x, y) is auto-calculated if omitted — frames stack horizontally

RESPONSIVE COMPARISON: To compare layouts at different viewports, add the same path multiple times with different widths. Example: add '/dashboard' at width 1280, then add '/dashboard' again at width 375.

remove_routeA

Remove a route frame from the Design Canvas.

CONSTRAINTS:

  • Prefer removal by ID (from list_routes or add_route response) — unambiguous

  • Removal by path is supported but removes only the first match — risky when duplicate paths exist (e.g., same route at desktop + mobile widths)

  • If you need to remove a specific viewport size, call list_routes first to find the exact route ID

capture_canvasA

Capture fresh screenshots of routes on the Design Canvas. Triggers a new render (not cached), waits for pages to fully load, and returns screenshots as images. Screenshots use WebKit rendering — use for quick layout verification, not pixel-perfect cross-browser QA.

USAGE: Use after making code changes to visually verify how routes look. This is an expensive operation (several seconds) — do not call speculatively.

CONSTRAINTS:

  • Returns 3 images by default. Pass limit for more, or ids for specific routes.

  • If the canvas has many routes, pass specific route IDs to capture only what changed — this saves context space and is significantly faster

  • Route IDs are returned by list_routes and add_route

  • For precise cross-browser verification, use Playwright instead

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing, adding, removing, and capturing. There is no overlap in functionality, and the descriptions strongly reinforce the boundaries between them.

Naming Consistency5/5

All four tool names follow the same verb_noun pattern (list_routes, add_route, remove_route, capture_canvas). The naming is consistent, predictable, and easy to infer.

Tool Count5/5

With 4 tools, the set is well-scoped for the server's purpose of managing routes on a design canvas. Each tool covers a core operation without unnecessary redundancy.

Completeness4/5

The set covers the main lifecycle (list, add, remove) and adds a capture action. An update route operation is missing, but adding/removing routes can serve as a workaround, so the gap is minor.

Maintenance

ActivityInactive
ResponsivenessNo issues