cysUML
Related Servers
Alternatives to cysUML
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to generate and validate 30+ UML and other diagram types (Mermaid, D2, Graphviz, BPMN, C4, and more) through the Model Context Protocol, returning rendered SVG, PNG, PDF, JPEG, or base64 output via Kroki, PlantUML, and Mermaid backends.4Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to generate UML diagrams from text descriptions using PlantUML, supporting multiple output formats (PNG, SVG, PDF), syntax validation, and diagram source extraction.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to generate professional UML diagrams (class, use case, activity, sequence) from natural language descriptions, producing editable .drawio files compatible with diagrams.net.7109 npmISC
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to render, validate and convert diagrams-as-code — Mermaid, PlantUML, C4, Graphviz, D2, Structurizr, BPMN and Excalidraw — into images with shareable links, using either the public or a self-hosted Kroki service.MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to list, read, create, update, delete, and render PlantUML and Mermaid diagrams, and check them against the actual codebase to detect architecture drift.15108 npm1MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to generate and structurally validate 30+ diagram types—UML (class, sequence, activity, state, component, and more), Mermaid, D2, Graphviz, TikZ, ERD, BPMN, and C4—via Kroki, PlantUML, and Mermaid.ink, returning rendered SVG/PNG/PDF/JPEG as URLs, base64 payloads, or saved files through tools like generate_uml and generate_uml_batch.5MIT
TDQS
Scored across 8 tools
Each of the eight tools maps to exactly one UML diagram type (activity, class, package, component, deployment, use case, state, sequence), and the descriptions reinforce the boundary — e.g. sequence explicitly takes no coordinates while the others do. Minor fuzzy edges exist because package/component/deployment diagrams all accept classes and packages, but the primary use case for each remains clearly separable.
All eight tools follow the identical draw_<diagram_type>_diagram pattern with no deviations, camel-free snake_case throughout. An agent can predict the full tool set from the naming scheme alone.
Eight tools sit squarely in the well-scoped 3-15 range, and each one earns its place by covering a distinct diagram type rather than duplicating functionality. There are no obvious utility or wrapper tools padding the list.
The core UML behavioral and structural diagrams are covered, and each tool is self-contained (renders, validates, saves input file and PNG), so there are no lifecycle dead ends. Gaps remain for object, timing, communication, composite structure, and profile diagrams, which an agent cannot produce with this surface but can often approximate with class/state diagrams.