Drawbridge Network Diagrams
Server Details
Routed, editable network diagrams from CDP/LLDP output, CSV or Graphviz DOT, as draw.io files
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
The five tools map to clear lifecycle stages (validate -> create -> describe -> edit -> export) and descriptions explicitly tell the agent when to prefer edit_diagram over create_diagram. However, the boundaries blur between create_diagram and export (both accept the same `kind` list, including drawio/svg/png/csv) and between describe and export with `kind=describe.json`, which produce essentially the same structured read-back.
All names are lowercase snake_case verb-led names, with create_diagram and edit_diagram following a verb_noun pattern while describe, export and validate are bare verbs. The verbs are unambiguous and predictable, so the deviation is cosmetic rather than confusing.
Five tools is tightly scoped for a diagram-generation server: one per action (validate, create, read, edit, render). Nothing feels padded, and nothing overlaps purely for redundancy.
The surface covers the full lifecycle: pre-flight validation, creation from many source formats, read-back/audit, incremental editing that preserves human-placed layout, and multi-format export. No obvious dead ends for the domain (there is no meaningful 'delete diagram' operation since files are written by the caller).
Available Tools
5 toolscreate_diagramAInspect
Generate a routed, laid-out network diagram from topology text (Graphviz DOT, Mermaid, CSV, CDP/LLDP neighbour output from most switch vendors, a FortiLink topology dump, Containerlab, Meraki or UniFi JSON, or an Ansible inventory — every format is listed in the drawbridge://guide resource) and export it. Drawbridge decides where the lines go; you decide what connects to what. HOW TO GET A PRECISE RESULT: device output the user pasted IS the source — pass it unchanged, never rewritten as DOT. When you write DOT yourself: set kind= on EVERY device so it draws as the real thing rather than a neutral box (firewall, waf, ips, vpn-gateway, proxy, nac, router, switch, l3-switch, load-balancer, wifi-ap, wlc, … — full list in the drawbridge://guide resource). Put speed= on every cable ("10G", "1G"), and link= where the cable MEANS something (ipsec, trunk, lag, wan, mgmt, wireless, conduit, fieldbus, ha). Never set pos=, width= or height=: Drawbridge lays out and routes — placing devices yourself is what makes a diagram look generated. READ THE notes IN THE RESULT AND FIX YOUR SOURCE: they name each line that was skipped or adjusted, and an unrecognised kind silently becomes a plain box otherwise. Iterate until the notes are empty. CHOOSING kind: drawio when the user will open or edit the drawing (this is usually what they want, and it is the only one they can change); svg to embed in a document or a page; png to show inline in a chat; describe.json to READ a drawing back and reason about it; csv / netbox.csv for a cable schedule and netbox-devices.csv for the hardware; dot to hand the topology on; clab.yml to turn the design into a Containerlab topology you can deploy. Results carry name: a suggested basename for this diagram. Write every file for one diagram into its own directory named after it — /.drawio, /.svg, /.cables.csv — so two diagrams never share a directory.
Inputs: source (required), kind, name, theme.
describeBInspect
Read a Drawbridge/draw.io network diagram and return its contents as structured JSON: devices, links, pages, layers and groups — for auditing or querying an existing drawing. Results carry name: a suggested basename for this diagram. Write every file for one diagram into its own directory named after it — /.drawio, /.svg, /.cables.csv — so two diagrams never share a directory.
Inputs: document (required).
edit_diagramAInspect
CHANGE AN EXISTING DIAGRAM instead of regenerating it: add, update and remove devices and links in a .drawio document and get the edited document back. This is the tool for "add a switch to this drawing" — create_diagram would redraw the whole page and throw away every position a human placed by hand. Call describe first to get the ids, then name them here. Everything you do not name keeps its exact position. Do NOT set x/y on a new device: Drawbridge places what you add below the existing drawing, which is the whole point of using this rather than editing the XML. Say what a new device belongs UNDER with near, naming a device already in the drawing: it lands straight below that one, in free space, so use it on every device you are about to cable to something. Put cables in an aggregate with bundle on add_edge or update_edge — its name, "ae1": cables given one name share one ring, and a ring of that name already drawn is joined. A cable already in another ring is added to this one; to move it, send bundle "" first and then the new name, in the same call. Set kind on every device you add or it draws as a plain box, and read the notes in the result — a mistyped id skips that one op and says so rather than failing the batch. The result names the ids it minted, in op order. Every id in an op must already exist when you send it — an op cannot name something an earlier op in the same call created, so adding a device and cabling it is two calls: add it, read the ids, then wire them. It writes nothing: save the returned document yourself, as it is — a cable or a position you write into the XML by hand skips the routing and the checks this tool makes. Results carry name: a suggested basename for this diagram. Write every file for one diagram into its own directory named after it — /.drawio, /.svg, /.cables.csv — so two diagrams never share a directory.
Inputs: ops (required), document (required), kind, name, +1 more.
exportAInspect
Render a Drawbridge/draw.io network diagram to an output format (svg, png, drawio, dot, csv, netbox.csv, netbox-devices.csv, describe.json, clab.yml). Returns the exported content. CHOOSING kind: drawio when the user will open or edit the drawing (this is usually what they want, and it is the only one they can change); svg to embed in a document or a page; png to show inline in a chat; describe.json to READ a drawing back and reason about it; csv / netbox.csv for a cable schedule and netbox-devices.csv for the hardware; dot to hand the topology on; clab.yml to turn the design into a Containerlab topology you can deploy. Results carry name: a suggested basename for this diagram. Write every file for one diagram into its own directory named after it — /.drawio, /.svg, /.cables.csv — so two diagrams never share a directory.
Inputs: document (required), kind, name, theme.
validateAInspect
CHECK TOPOLOGY TEXT BEFORE DRAWING IT: reads the same source create_diagram would and reports what it found — the format it detected, how many devices and links it would draw, and every line it would skip or adjust, with the line number and the reason. An unknown kind= names the nearest real one. Nothing is laid out, routed or rendered, so it is far cheaper than a draw: call it, fix what it names, then call create_diagram once. Results carry name: a suggested basename for this diagram. Write every file for one diagram into its own directory named after it — /.drawio, /.svg, /.cables.csv — so two diagrams never share a directory.
Inputs: source (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
OSPF and IS-IS topology, paths, failure impact, change events, MPLS TE and BGP from Topolograph
Interactive diagrams you can collapse, regroup and focus: architecture, dependencies, org charts
Flowcharts, UML/ER diagrams, mind maps, infographics and SOPs as editable, presentable boards
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to start from a seed host, traverse CDP/LLDP neighbor evidence and device information over SSH, and produce an editable Draw.io topology diagram plus supporting evidence for engineer review. It supports explicit host/CIDR scoping, bounded depth and device counts, strict host-key checks, and a read-only command policy, with an offline simulated demo.MIT
- AlicenseAqualityDmaintenanceVisual network topology editor with AI agent integration via MCP. One-click SSH + web-service access from any node, nmap/CSV import, smart auto-layout, multi-sheet, local-first. Open-source successor to netViz (CA Technologies 1990-2012)4459 npm4MIT
- AlicenseAqualityBmaintenanceEnables building Huawei eNSP topologies offline and configuring lab devices through their console ports, including batch command/config delivery, config comparison, and rule-based lab verification. Also exports topologies to Mermaid, draw.io, and CSV and generates command-trace reports.191MIT
- AlicenseNot gradedqualityBmaintenanceLocal zero-dependency Draw.io MCP server in Go — 14 typed tools for diagram create/edit/preview/export over stdio with live browser preview, on-demand drawing guides, 25+ bundled vendor shape libraries, and auto-save.1Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.