design-canvas-mcp
Related Servers
Alternatives to design-canvas-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables an AI agent to read and write a product's design screens on a shared, versioned canvas: creating and editing HTML screens and shared parts, taking screenshots, linking flows, posting comments and annotations, and opening or approving proposals. Every drawing is returned with its screenshot so the agent can see what it produced, letting screens persist and evolve across chats instead of starting from zero.1MIT- FlicenseNot gradedqualityCmaintenanceEnables remote agents to control tldraw Desktop's Canvas API, manage documents, scripts, assets, and take screenshots.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to programmatically control a live Excalidraw canvas through element-level CRUD operations and real-time synchronization. It allows agents to iteratively build, inspect, and refine diagrams while providing visual feedback via screenshots and scene descriptions.3,112 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to programmatically control a live Excalidraw canvas with element-level CRUD operations and real-time synchronization. It supports iterative diagramming through scene descriptions, screenshots, and advanced layout tools for collaborative AI-human workflows.3,112 npm2MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to read and edit a spatial canvas board of notes, tasks and ideas through the running desktop app, creating, updating, linking, grouping and arranging nodes, importing files, focusing the view and undoing changes so edits appear instantly and stay reversible.2510 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to draw on a self-hosted canvas by creating and editing frames, text, shapes, images, and SVGs with auto-layout, then inspecting, exporting, and sharing the results. Also supports live viewing of agent edits, pinned comments, screenshots, and revision history so people and agents can collaborate on boards.824 npm1MIT
TDQS
Scored across 4 tools
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.
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.
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.
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.