DiagramZu
Related Servers
Alternatives to DiagramZu
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for AI Diagram Maker — generate software engineering diagrams from natural language, code, ASCII diagram, images, or Mermaid. Inline diagram rendering using MCP apps UI and diagram URL in responses. Works with Cursor, Claude Desktop, Claude Code, and any MCP-compatible AI.5134 npm10MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI to create, edit, and manage Mermaid diagrams via MCP, with real-time preview in a browser-based editor.3-
- AlicenseNot gradedqualityBmaintenanceGives AI agents a live, persistent diagram canvas they can draw on, inspect via screenshots, and refine element by element, then export as editable .excalidraw files to commit alongside code. Supports architecture diagrams and flowcharts through a CLI, MCP tools, or REST API.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with a local Mermaid diagram editor via MCP, allowing them to get and set diagrams programmatically.13Apache 2.0
- AlicenseBqualityCmaintenanceMCP server that enables AI assistants to create, parse, render, and validate Draw.io diagrams programmatically.1427 PyPI2MIT
- AlicenseBqualityDmaintenance❤️ Generate mermaid diagram and chart with AI MCP dynamically.11,025 npm652TypeScriptMIT
TDQS
Scored across 19 tools
Each of the 19 tools targets a distinct resource (space, folder, page, diagram, version, comment, deck) plus action, and descriptions clearly demarcate boundaries such as list_pages vs get_page vs update_page, or list_versions vs get_version. There is no apparent overlap.
Consistent verb_noun pattern throughout (list_folders, create_page, update_diagram, get_deck, add_comment, analyze_diagram), with only the single-word analyze_diagram as a reasonable verb.
19 tools is on the high side but fairly scoped across eight resources: spaces, folders, pages, diagrams, versions, comments, and decks. It is neither thin nor extreme.
Broad coverage across the core domain (CRUD for pages, diagrams, decks; reads for versions, comments), though folders are read-only and deleting diagrams/decks/comments is absent. These gaps are workable since some operations are intentionally human-only.