A
licenseB
qualityB
maintenanceMCP server that enables AI assistants to create, parse, render, and validate Draw.io diagrams programmatically.
14
58 PyPI
1
MIT
DrawFather
by its-imad
Related Servers
Alternatives to DrawFather
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that lets agents draw 18 diagram types from JSON (no SVG, no headless browser)219 npm10MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents programmatic control over a live tldraw canvas, enabling diagram creation through natural language.1MIT
- AlicenseAqualityAmaintenanceMCP server that exposes ArchSmith's diagram rendering and validation as tools, along with schema and registry resources, enabling AI agents to generate consistent SVG architecture diagrams from validated JSON descriptions.57Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to programmatically create and manage flowcharts, ERDs, and swimlane diagrams. It provides tools for manipulating diagram structures, performing auto-layouts, and exporting to Mermaid or Markdown formats.10 npmMIT
- AlicenseNot gradedqualityAmaintenanceA local-first whiteboard MCP server that enables AI agents to create, inspect, and update canvas diagrams and shapes collaboratively via 13 semantic tools.4MIT
TDQS
B3.4/5.0
Scored across 23 tools
Disambiguation3/5
The four edit-style tools (edit_drawing, update_drawing, patch_drawing, edit_creative) overlap significantly; descriptions do attempt to differentiate them (patch for small label/style, update for full element upserts, edit for atomic operations), which helps but still requires careful reading. The three compose_* tools are separable by diagram domain, and check/repair/preview/export are distinct. Overall boundaries exist but are blurry in the mutation cluster.
Naming Consistency4/5
Most tools follow a predictable snake_case verb_noun pattern (compose_*, create_drawing, edit_*, get_*, list_*, import_drawing, export_*, preview_drawing, check_drawing, repair_drawing, migrate_drawing). A few deviate: 'project_diagrams' (noun_verb) and 'drawing_history' (noun_noun), which break the pattern slightly. Still readable and largely consistent.
Tool Count3/5
23 tools is on the heavy side for the stated scope; several (compose_drawing, compose_technical, compose_creative and the four editors) suggest consolidation is possible. It is defensible given the breadth of diagram types, interchange formats, and repair/history workflows, but it sits in the heavy band rather than a tight, well-scoped set.
Completeness4/5
Coverage is broad: create, read, edit, patch, import, export, preview, check, repair, migrate, history, and project management are all present, which is strong lifecycle coverage for a diagramming engine. However there is no explicit delete/rename tool for drawings, a minor gap an agent would have to work around via history or overwrite.
Maintenance
ActivityMaintained
ResponsivenessNo issues