Skip to main content
Glama

MCP Mermaid build npm Version npm License Trust Score

Generieren Sie mermaid-Diagramme und -Charts dynamisch mit AI MCP. Sie können auch Folgendes verwenden:

  • mcp-server-chart zum Generieren von Charts, Graphen und Karten.

  • Infographic zum Generieren von Infografiken, wie z. B. Timeline, Comparison, List, Process usw.

  • 🖼️ figure.ling.pub/gallery zum Durchsuchen und Teilen von KI-generierten Diagrammen und Abbildungen, die mit mcp-mermaid und anderen Tools erstellt wurden.

✨ Funktionen

  • Volle Unterstützung aller Funktionen und der Syntax von Mermaid.

  • Unterstützung der Konfiguration von backgroundColor und theme, wodurch große KI-Modelle reichhaltige Stilkonfigurationen ausgeben können.

  • Unterstützung des Exports in die Formate base64, svg, mermaid, file sowie remote-freundliche svg_url- und png_url-Formate, mit Validierung für Mermaid, um die korrekte Syntax- und Grafikausgabe des Modells über mehrere Runden hinweg zu erleichtern. Verwenden Sie outputType: "file", um PNG-Diagramme automatisch für KI-Agenten auf der Festplatte zu speichern, oder die URL-Modi, um Diagramme über öffentliche mermaid.ink-Links zu teilen.

Related MCP server: Mermaid-MCP

🤖 Verwendung

Um es mit einer Desktop-App wie Claude, VSCode, Cline, Cherry Studio usw. zu verwenden, fügen Sie die unten stehende MCP-Server-Konfiguration hinzu. Auf dem Mac-System:

{
  "mcpServers": {
    "mcp-mermaid": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-mermaid"
      ]
    }
  }
}

Auf dem Windows-System:

{
  "mcpServers": {
    "mcp-mermaid": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "mcp-mermaid"
      ]
    }
  }
}

Sie können es auch auf Aliyun, Modelscope, Glama.ai, Smithery.ai oder anderen mit HTTP- oder SSE-Protokoll verwenden.

Zugriffspunkte:

  • SSE: http://localhost:3033/sse

  • Streamable: http://localhost:1122/mcp

Verfügbare Docker-Tags:

  • susuperli/mcp-mermaid:latest - Neueste stabile Version

  • Alle verfügbaren Tags finden Sie unter Docker Hub

🚰 Ausführung mit SSE- oder Streamable-Transport

Option 1: Globale Installation

Installieren Sie das Paket global:

npm install -g mcp-mermaid

Starten Sie den Server mit der von Ihnen bevorzugten Transportoption:

# For SSE transport (default endpoint: /sse)
mcp-mermaid -t sse

# For Streamable transport with custom endpoint
mcp-mermaid -t streamable

Option 2: Lokale Entwicklung

Wenn Sie lokal mit dem Quellcode arbeiten:

# Clone and setup
git clone https://github.com/hustcc/mcp-mermaid.git
cd mcp-mermaid
npm install
npm run build

# Run with npm scripts
npm run start:sse        # SSE transport on port 3033
npm run start:streamable # Streamable transport on port 1122

Zugriffspunkte

Anschließend können Sie auf den Server zugreifen unter:

  • SSE-Transport: http://localhost:3033/sse

  • Streamable-Transport: http://localhost:1122/mcp (lokal) oder http://localhost:3033/mcp (global)

🎮 CLI-Optionen

Sie können auch die folgenden CLI-Optionen verwenden, wenn Sie den MCP-Server ausführen. Befehlsoptionen erhalten Sie durch Ausführen der CLI mit -h.

MCP Mermaid CLI

Options:
  --transport, -t  Specify the transport protocol: "stdio", "sse", or "streamable" (default: "stdio")
  --port, -p       Specify the port for SSE or streamable transport (default: 3033)
  --endpoint, -e   Specify the endpoint for the transport:
                    - For SSE: default is "/sse"
                    - For streamable: default is "/mcp"
  --help, -h       Show this help message

🔨 Entwicklung

Abhängigkeiten installieren:

npm install

Server bauen:

npm run build

Starten des MCP-Servers

Verwendung des MCP-Inspektors (zum Debuggen):

npm run start

Verwendung verschiedener Transportprotokolle:

# SSE transport (Server-Sent Events)
npm run start:sse

# Streamable HTTP transport
npm run start:streamable

Direkte Node-Befehle:

# SSE transport on port 3033
node build/index.js --transport sse --port 3033

# Streamable HTTP transport on port 1122
node build/index.js --transport streamable --port 1122

# STDIO transport (for MCP client integration)
node build/index.js --transport stdio

🐳 Docker-Verwendung

Führen Sie MCP Mermaid mit Docker aus:

# Pull the image
docker pull susuperli/mcp-mermaid:latest

# Run with SSE transport (default)
docker run -p 3033:3033 susuperli/mcp-mermaid:latest --transport sse

# Run with streamable transport
docker run -p 1122:1122 susuperli/mcp-mermaid:latest --transport streamable --port 1122

📄 Lizenz

MIT@hustcc.

Available Tools

1 tool
generate_mermaid_diagramBInspect

Generate mermaid diagram and chart with mermaid syntax dynamically. Mermaid is a JavaScript based diagramming and charting tool that uses Markdown-inspired text definitions and a renderer to create and modify complex diagrams. The main purpose of Mermaid is to help documentation catch up with development.

ParametersJSON Schema
NameRequiredDescriptionDefault
mermaidYesThe mermaid diagram syntax used to be generated, such as, graph TD; A-->B; A-->C; B-->D; C-->D;.
themeNoTheme for the diagram (optional). Default is 'default'.default
backgroundColorNoBackground color for the diagram (optional). Default is 'white'.white
outputTypeNoThe output type of the diagram. Can be 'base64', 'svg', 'mermaid', 'file', 'svg_url', or 'png_url'. Default is 'base64'. 'base64' returns PNG image as base64 encoded string. 'file' saves the PNG image to disk. The *_url options return public mermaid.ink links for remote-friendly sharing.base64

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fails to disclose behavioral traits such as side effects, performance, or limitations. It only broadly states dynamic generation without specifics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences, but the second sentence focuses on Mermaid's general purpose rather than the tool's specific behavior. No filler words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description does not explain the output format or how to use the returned data. With no output schema, relying on the outputType parameter is insufficient for complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the parameters are already well-documented. The description adds no additional meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: generating mermaid diagrams and charts dynamically. It explains what Mermaid is, providing context for the tool's functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool or when not to use it. There are no alternatives mentioned, and the description lacks explicit usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • Changedgenerate_mermaid_diagram3 fields changed
      • changedInput schema / properties / outputType / default
        Previous value: -"png"New value: +"base64"
      • changedInput schema / properties / outputType / description
        Previous value: -"The output type of the diagram. Can be 'png', 'svg' or 'mermaid'. Default is 'png'."New value: +"The output type of the diagram. Can be 'base64', 'svg', 'mermaid', 'file', 'svg_url', or 'png_url'. Default is 'base64'. 'base64' returns PNG image as base64 encoded string. 'file' saves the PNG image to disk. The *_url options return public mermaid.ink links for remote-friendly sharing."
      • changedInput schema / properties / outputType / enum
        Previous value: -[
        -  "png",
        -  "svg",
        -  "mermaid"
        -]New value: +[
        +  "base64",
        +  "svg",
        +  "mermaid",
        +  "file",
        +  "svg_url",
        +  "png_url"
        +]
  2. 1 tool update
    • First observedgenerate_mermaid_diagram

TDQS

B3.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is clear and stands alone.

Naming Consistency5/5

Since there is only one tool, naming consistency is not applicable, but the single name follows a clear descriptive pattern.

Tool Count3/5

A single tool for generating Mermaid diagrams is minimal. While it covers the core functionality, the scope feels thin (1 tool) compared to typical MCP servers that handle diagramming workflows.

Completeness3/5

The tool covers the primary task of generating diagrams, but lacks auxiliary operations such as validation, styling, or export options that would enhance completeness for a diagramming server.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Related MCP Connectors

Related MCP Servers

  • F
    license
    Not graded
    quality
    F
    maintenance
    Narasimhaponnada/mermaid-mcp - AI-powered Mermaid diagram generation with 22+ diagram types including flowcharts, sequence diagrams, class diagrams, ER diagrams, architecture diagrams, state machines, and more. Features 50+ pre-built templates, advanced layout engines, SVG/PNG/PDF exports.
    53
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables automatic generation of UML class diagrams and entity-relationship diagrams from natural language descriptions or structured JSON data. It integrates with MCP agents to create visual representations of code structures and system designs without manual Mermaid coding.
    8 npm
    1
    MIT