Skip to main content
Glama
mermaidonline-mcp

mermaidonline-mcp

by j-river

Related Servers

Alternatives to mermaidonline-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to list, read, create, update, and delete Mermaid diagrams and collections via the Mermaid REST API over stdio or stateless Streamable HTTP.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Deterministic 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 locally
      5
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    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).

    Naming Consistency5/5

    Both names follow the same verb_noun pattern: encode_mermaid_share / decode_mermaid_share. The shared suffix makes the pairing obvious and predictable.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues