Skip to main content
Glama
charlieellington

design-canvas-mcp

by charlieellington
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to design-canvas-mcp

No user-submitted related servers found.

    Related Servers

    • tldraw-offline-mcp

      er1chi
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables remote agents to control tldraw Desktop's Canvas API, manage documents, scripts, assets, and take screenshots.
      1
      -

    • Excalidraw MCP Server

      kakacoding1
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables 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.
      1,611 npm
      MIT

    • Excalidraw MCP Server

      ignizia-code
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      1,611 npm
      2
      MIT

    • Excalidraw MCP Server

      0xArtex
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to create, modify, and share diagrams on a live Excalidraw canvas through MCP tools, supporting shapes, text, arrows, batch operations, and export to shareable links with images.
      1,611 npm
      8
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources