Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.hj1003862396/draw-flow-mcp-server

NPM · @IO.GITHUB.HJ1003862396/DRAW-FLOW-MCP-SERVER · SCANNED AUG 3

MCP server for Next AI Draw.io - AI-powered diagram generation with real-time browser preview

+13 this week 64 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (126 of 130), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (126 of 130), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1008 tokens (~201/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @io.github.hj1003862396/draw-flow-mcp-server

# add to Claude Code
claude mcp add hj1003862396-draw-flow-mcp-server -- npx -y @io.github.hj1003862396/draw-flow-mcp-server
# add to Codex CLI
codex mcp add hj1003862396-draw-flow-mcp-server -- npx -y @io.github.hj1003862396/draw-flow-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hj1003862396-draw-flow-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@io.github.hj1003862396/draw-flow-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hj1003862396-draw-flow-mcp-server --command npx --arg -y --arg @io.github.hj1003862396/draw-flow-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  hj1003862396-draw-flow-mcp-server:
    command: "npx"
    args: ["-y", "@io.github.hj1003862396/draw-flow-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "hj1003862396-draw-flow-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@io.github.hj1003862396/draw-flow-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +44
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • License: unverified → pass functional
    • Schema quality: unverified → 100 functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → good functional
    • Tool coverage: unverified → 100 functional
    • Licence: Apache-2.0 functional
  • 2 Aug 26 −5
    • Malware scan: unverified → pass security
    • Tool coverage: 100 → unverified functional
    • Schema quality: 100 → unverified functional
  • 31 Jul 26 −26
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 51

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@io.github.hj1003862396/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 126 packages

126 packages in the resolved dependency tree · 126 deprecated · 35 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~1,008 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
create_new_diagram ~488

Create a NEW diagram from mxGraphModel XML. Use this when creating a diagram from scratch or replacing the current diagram entirely. CRITICAL: You MUST provide the 'xml' argument in EVERY call. Do NOT call this tool without xml. When to use this tool: - Creating a new diagram from scratch - Replacing the current diagram with a completely different one - Major structural changes that require regenerating the diagram When to use edit_diagram instead: - Small modifications to existing diagram - Adding/removing individual elements - Changing labels, colors, or positions XML FORMAT - Full mxGraphModel structure: <mxGraphModel> <root> <mxCell id="0"/> <mxCell id="1" parent="0"/> <mxCell id="2" value="Shape" style="rounded=1;" vertex="1" parent="1"> <mxGeometry x="100" y="100" width="120" height="60" as="geometry"/> </mxCell> </root> </mxGraphModel> LAYOUT CONSTRAINTS: - Keep all elements within x=0-800, y=0-600 (single page viewport) - Start from margins (x=40, y=40), keep elements grouped closely - Use unique IDs starting from "2" (0 and 1 are reserved) - Set parent="1" for top-level shapes - Space shapes 150-200px apart for clear edge routing EDGE ROUTING RULES: - Never let multiple edges share the same path - use different exitY/entryY values - For bidirectional connections (A↔B), use OPPOSITE sides - Always specify exitX, exitY, entryX, entryY explicitly in edge style - Route edges AROUND obstacles using waypoints (add 20-30px clearance) - Use natural connection points based on flow (not corners) COMMON STYLES: - Shapes: rounded=1; fillColor=#hex; strokeColor=#hex - Edges: endArrow=classic; edgeStyle=orthogonalEdgeStyle; curved=1 - Text: fontSize=14; fontStyle=1 (bold); align=center

NameTypeReqDescription
xmlstringyesREQUIRED: The complete mxGraphModel XML. Must always be provided.

No output schema declared.

No examples provided.

edit_diagram ~381

Edit the current diagram by ID-based operations (update/add/delete cells). ⚠️ REQUIRED: You MUST call get_diagram BEFORE this tool! This fetches the latest state from the browser including any manual user edits. Skipping get_diagram WILL cause user's changes to be LOST. Workflow: 1. Call get_diagram to see current cell IDs and structure 2. Use the returned XML to construct your edit operations 3. Call edit_diagram with your operations Operations: - add: Add a new cell. Provide cell_id (new unique id) and new_xml. - update: Replace an existing cell by its id. Provide cell_id and complete new_xml. - delete: Remove a cell by its id. Only cell_id is needed. For add/update, new_xml must be a complete mxCell element including mxGeometry. Example - Add a rectangle: {"operations": [{"operation": "add", "cell_id": "rect-1", "new_xml": "<mxCell id=\"rect-1\" value=\"Hello\" style=\"rounded=0;\" vertex=\"1\" parent=\"1\"><mxGeometry x=\"100\" y=\"100\" width=\"120\" height=\"60\" as=\"geometry\"/></mxCell>"}]} Example - Update a cell: {"operations": [{"operation": "update", "cell_id": "3", "new_xml": "<mxCell id=\"3\" value=\"New Label\" style=\"rounded=1;\" vertex=\"1\" parent=\"1\"><mxGeometry x=\"100\" y=\"100\" width=\"120\" height=\"60\" as=\"geometry\"/></mxCell>"}]} Example - Delete a cell: {"operations": [{"operation": "delete", "cell_id": "rect-1"}]}

NameTypeReqDescription
operationsarrayyesArray of operations to apply

No output schema declared.

No examples provided.

export_diagram ~41

Export the current diagram to a .drawio file.

NameTypeReqDescription
pathstringyesFile path to save the diagram (e.g., ./diagram.drawio)

No output schema declared.

No examples provided.

get_diagram ~53

Get the current diagram XML (fetches latest from browser, including user's manual edits). Call this BEFORE edit_diagram if you need to update or delete existing elements, so you can see the current cell IDs and structure.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

start_session ~45

Start a new diagram session and open the browser for real-time preview. Starts an embedded server and opens a browser window with draw.io. The browser will show diagram updates as they happen.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.