Skip to main content
Glama
k26k26

drawio-mcp

by k26k26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to drawio-mcp

No user-submitted related servers found.

    Related Servers

    • drawio

      wangcangxing
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables generating diagrams from JSON specifications, exporting them as PNG/SVG/PDF offline, and controlling a running desktop editor via CDP for live edits, XML retrieval, and screenshots.
      MIT

    • draw.io MCP Server

      edoardopareti
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables creating, importing and incrementally editing draw.io diagrams through structured tools that manage nodes, edges and groups, then render validated .drawio files. It keeps diagram state across turns, supports automatic layout and undo, and runs locally over stdio or HTTP so any MCP client can drive it.
      Apache 2.0

    • diagram-mcp

      JVmano
      A
      license
      A
      quality
      C
      maintenance
      Renders diagram-as-code to PNG files on your disk, and also provides text-art previews and syntax validation, all locally without a browser or network.
      4
      2 npm
      MIT

    • drawio-desktop-mcp

      ArdaUzun
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to create and edit diagrams in the draw.io desktop app through the Model Context Protocol.
      Apache 2.0
    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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clear and distinct role: informational, create, inspect, validate, and update. There is no meaningful overlap between the tools, and the descriptions make it easy for an agent to select the right one.

    Naming Consistency4/5

    Four of the five tools follow a consistent verb_noun pattern: create_diagram, inspect_diagram, validate_diagram, and update_diagram. server_info breaks the pattern by using a noun_noun form without a verb, which is a minor deviation.

    Tool Count5/5

    Five tools is a well-scoped size for a diagram-focused MCP server. Each tool contributes a necessary part of the workflow without unnecessary bloat or redundancy.

    Completeness4/5

    The core create-read-update-validate lifecycle is well covered for draw.io XML manipulation. Missing capabilities like deleting nodes/edges or inspecting more than the first page are notable but not critical gaps for common diagram workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources