diagram-mcp
Related Servers
Alternatives to diagram-mcp
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
- AlicenseCqualityDmaintenanceEnables AI models to create and manage various types of diagrams (flowcharts, UML, network diagrams, etc.) via the Model Context Protocol.2658 npm6ISC
- AlicenseAqualityBmaintenanceA Model Context Protocol server that converts Mermaid diagram code into various image formats (PNG, JPG, SVG, PDF) with theme customization options for AI clients.39MIT
- FlicenseNot gradedqualityDmaintenanceEnables users to create and interact with hand-drawn sketches and architecture diagrams directly within chat interfaces using Excalidraw. It leverages the Model Context Protocol to provide interactive HTML visualizations with smooth viewport control and fullscreen editing capabilities.-
- AlicenseNot gradedqualityDmaintenanceConverts files (PDF, images, audio, DOCX, XLSX, PPTX) and web content (YouTube transcripts, Bing search, general pages) to Markdown via the Model Context Protocol.Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI agents to generate PDFs from Markdown or URLs, extract text, merge documents, and perform text conversions via the Model Context Protocol.81MIT
TDQS
Scored across 2 tools
The two tools serve clearly distinct purposes: one renders Mermaid diagrams, the other renders Plotly charts. There is no overlap in functionality, so an agent can easily select the correct tool based on the desired output type.
Both tools follow a consistent 'render_' prefix naming pattern, clearly indicating their action and distinguishing them by the library they support (mermaid vs plotly). This makes the naming predictable and easy to understand.
With only two tools, the count is on the lower side but appropriate for a server focused on rendering two distinct visualization libraries. Each tool is justified by the different input formats and rendering engines, so the count feels reasonable for the scope.
The server covers the core functionality for rendering diagrams from two popular libraries. While it could include additional libraries or a generic render tool, the current set is sufficient for its stated purpose and has no obvious gaps in the rendering workflows.