mcp-mermaidjs-to-image
Related Servers
Alternatives to mcp-mermaidjs-to-image
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to generate and render Mermaid diagrams (flowcharts, sequence diagrams, etc.) as PNG/SVG images with local file saving and HTTP access URLs. Supports batch processing and intelligent caching for efficient diagram creation.168 npm1MIT
- AlicenseAqualityBmaintenanceEnables agents to turn short specs, Mermaid, or CSV data into laid-out SVG diagrams and charts, and to validate and audit the result for overlapping labels, arrows through boxes, and spilling text before showing it to anyone. Exposes render, describe, validate, audit, export, and infer tools so drawings can be generated, checked, and converted to formats like PNG, PDF, draw.io, and Excalidraw.947 PyPIMIT
- AlicenseAqualityCmaintenanceLets agents construct Mermaid diagrams from structured JSON IR and render them as PNG or SVG.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables the dynamic generation of various software development diagrams, such as flowcharts, sequence diagrams, and architecture diagrams, using Mermaid syntax. It includes tools for diagram validation and provides instructions for exporting results to multiple formats including SVG and PNG.-
- AlicenseNot gradedqualityDmaintenanceEnables agents to search official Mermaid diagram syntax documentation and validate Mermaid diagram code before presenting it to users, ensuring syntactically correct flowcharts, sequence diagrams, class diagrams, and other Mermaid visualizations.MIT
- 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
TDQS
Scored across 4 tools
The four tools split cleanly into two discovery tools (catalog vs. per-type syntax) and two rendering tools (inline source vs. file input), and each description states its input/output mode explicitly. render_mermaid_to_png vs. render_mermaid_file is the only near-pair, and the inline-vs-disk distinction is unambiguous.
All names follow a consistent verb_noun snake_case pattern (get_supported_diagrams, get_diagram_syntax_guide, render_mermaid_to_png, render_mermaid_file). The two get_ tools are discovery and the two render_ tools are execution, reinforcing the pattern semantically.
Four tools is well within a tight, focused scope for a single-purpose rendering server: two are needed because diagram syntax knowledge must be looked up before rendering, and two cover the two legitimate input modes. No tool looks redundant or missing at this size.
The lifecycle — discover supported types, fetch syntax rules, render from string or file — is covered end to end, with validation feedback on bad diagram_type. Minor gaps remain around output options (e.g. SVG/PDF or theme/size control) that agents could otherwise want, but the core workflow has no dead ends.