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

    • 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
      4 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

    • dgv

      ShAInyXYZ
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables planning and maintaining system architecture as typed, linted, live diagrams stored as files in the repo, with MCP tools for cataloging, creating, editing, linting, exporting, and viewing diagrams locally.
      7
      MIT

    • diag-weaver

      wldxiaobai
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to edit diagram/graph structures on a live draw.io canvas and manage local versions via snapshots, restore, and export without embedding a separate LLM or polluting the workspace.
      7
      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

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources