mermaidonline-mcp
Related Servers
Alternatives to mermaidonline-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to list, read, create, update, and delete Mermaid diagrams and collections via the Mermaid REST API over stdio or stateless Streamable HTTP.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables generating, validating, repairing, and styling Draw.io XML through local stdio tools, with optional LLM-backed generation via OpenAI/Anthropic-compatible providers.366MIT
- AlicenseNot gradedqualityBmaintenanceEnables generating and locally validating Mermaid diagrams and charts from Mermaid syntax. Returns validated syntax, mermaid.ink share links, or rendered images through a locally configured renderer command.66 npmMIT
- AlicenseAqualityBmaintenanceDeterministic encode, decode, hash and convert for agents, on the same pipeline engine as the String Utility Belt web app, CLI and editor extensions: a pipeline built and checked in the browser runs unchanged from its share link. Base64/hex/URL, JWT, hashes, JSON/YAML/CSV/XML, dates and regex; tools to search, describe and run utilities or whole pipelines, and to detect input formats. Runs locally54MIT
- AlicenseAqualityCmaintenanceEnables AI hosts to generate and open Mermaid diagram links in Markdown files, providing tools for syncing, listing, and injecting diagrams via the Mermaid.ai editor.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables document conversion across Markdown, HTML, DOCX, PDF, EPUB, PPTX, LaTeX, and many other formats, with automatic Mermaid diagram rendering and stored outputs for chained conversions. Runs locally over stdio or in Docker over authenticated HTTP.Apache 2.0
TDQS
Scored across 2 tools
The two tools are exact inverses, one encoding and one decoding, with no overlap in purpose. Descriptions make the boundary explicit, including what each does and does not do (no validation, no fetching).
Both names follow the same verb_noun pattern: encode_mermaid_share / decode_mermaid_share. The shared suffix makes the pairing obvious and predictable.
Two tools is thin in absolute terms, but the encode/decode pair is genuinely all the stated scope requires. Each tool earns its place, yet there is little surface area for an agent to work with beyond a single round trip.
Encode and decode together fully cover the reversible share-token lifecycle, including URL and fragment inputs and whole-state mode. The only gap is that neither validates Mermaid syntax or renders, so an agent cannot check whether a token decodes to valid content.