Mermaid Validator

Created By
rtuina year ago
A Model Context Protocol server that validates and renders Mermaid diagrams.
Overview

What is Mermaid Validator?

Mermaid Validator is a Model Context Protocol server that validates and renders Mermaid diagrams, enabling LLMs to ensure the correctness of diagram syntax and produce visual representations.

How to use Mermaid Validator?

To use the Mermaid Validator, configure your MCP client by adding it to your mcp servers file with the appropriate command and arguments to invoke the validator.

Key features of Mermaid Validator?

  • Validates Mermaid diagram syntax and returns rendered SVG output.
  • Integrates with the Model Context Protocol for seamless client communication.
  • Provides detailed error messages for invalid diagrams.

Use cases of Mermaid Validator?

  1. Validating and rendering flowcharts for documentation.
  2. Ensuring the correctness of UML diagrams in software design.
  3. Generating visual representations of complex data flows.

FAQ from Mermaid Validator?

  • Can Mermaid Validator handle all types of Mermaid diagrams?

Yes! It supports various diagram types defined in the Mermaid syntax.

  • Is there a limit to the complexity of diagrams?

While there is no strict limit, very complex diagrams may affect performance and rendering time.

  • How can I troubleshoot validation errors?

The validator provides detailed error messages to help identify and fix issues in the diagram syntax.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rtuin
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago