MCP Server Mermaid
MCP Mermaid

AI MCPを使用して mermaid ダイアグラムやチャートを動的に生成します。また、以下も利用可能です:
mcp-server-chart:チャート、グラフ、マップの生成用。
Infographic:
Timeline、Comparison、List、Processなどのインフォグラフィック生成用。🖼️ figure.ling.pub/gallery:mcp-mermaid やその他のツールで作成されたAI生成ダイアグラムや図を閲覧・共有できます。
✨ 特徴
Mermaidのすべての機能と構文を完全にサポート。backgroundColorとthemeの設定をサポートしており、大規模AIモデルがリッチなスタイル設定を出力可能。base64、svg、mermaid、file、およびリモートフレンドリーなsvg_url、png_url形式へのエクスポートをサポート。モデルが正しい構文とグラフィックを複数回出力できるようにMermaidの検証機能も備えています。outputType: "file"を使用すると、AIエージェント用にPNGダイアグラムをディスクへ自動保存したり、URLモードを使用して公開されている mermaid.ink リンク経由でダイアグラムを共有したりできます。
Related MCP server: Mermaid-MCP
🤖 使用方法
Claude、VSCode、Cline、Cherry Studio などの Desktop APP で使用するには、以下のMCPサーバー設定を追加してください。Macシステムの場合:
{
"mcpServers": {
"mcp-mermaid": {
"command": "npx",
"args": [
"-y",
"mcp-mermaid"
]
}
}
}Windowsシステムの場合:
{
"mcpServers": {
"mcp-mermaid": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"mcp-mermaid"
]
}
}
}また、HTTPやSSEプロトコルを使用して、aliyun、modelscope、glama.ai、smithery.ai などでも利用可能です。
アクセスポイント:
SSE:
http://localhost:3033/sseStreamable:
http://localhost:1122/mcp
利用可能なDockerタグ:
susuperli/mcp-mermaid:latest- 最新の安定版すべての利用可能なタグは Docker Hub で確認してください。
🚰 SSE または Streamable トランスポートでの実行
オプション 1: グローバルインストール
パッケージをグローバルにインストールします:
npm install -g mcp-mermaid好みのトランスポートオプションでサーバーを実行します:
# For SSE transport (default endpoint: /sse)
mcp-mermaid -t sse
# For Streamable transport with custom endpoint
mcp-mermaid -t streamableオプション 2: ローカル開発
ソースコードをローカルで作業している場合:
# 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アクセスポイント
その後、以下の場所からサーバーにアクセスできます:
SSE トランスポート:
http://localhost:3033/sseStreamable トランスポート:
http://localhost:1122/mcp(ローカル) またはhttp://localhost:3033/mcp(グローバル)
🎮 CLI オプション
MCPサーバー実行時に以下のCLIオプションも使用できます。コマンドオプションは -h を付けてCLIを実行してください。
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🔨 開発
依存関係をインストールします:
npm installサーバーをビルドします:
npm run buildMCPサーバーの起動
MCP Inspector を使用する場合 (デバッグ用):
npm run start異なるトランスポートプロトコルを使用する場合:
# SSE transport (Server-Sent Events)
npm run start:sse
# Streamable HTTP transport
npm run start:streamable直接ノードコマンドを使用する場合:
# 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 の使用方法
Docker で MCP Mermaid を実行します:
# 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📄 ライセンス
MIT@hustcc.
Available Tools
1 toolgenerate_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.
| Name | Required | Description | Default |
|---|---|---|---|
| mermaid | Yes | The mermaid diagram syntax used to be generated, such as, graph TD; A-->B; A-->C; B-->D; C-->D;. | |
| theme | No | Theme for the diagram (optional). Default is 'default'. | default |
| backgroundColor | No | Background color for the diagram (optional). Default is 'white'. | white |
| outputType | No | 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. | base64 |
TDQS
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.
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.
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.
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.
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.
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 tool update
v1.0.0- Changed
generate_mermaid_diagram3 fields changed- changed
Input schema / properties / outputType / defaultPrevious value: -"png"New value: +"base64" - changed
Input schema / properties / outputType / descriptionPrevious 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." - changed
Input schema / properties / outputType / enumPrevious value: -[ - "png", - "svg", - "mermaid" -]New value: +[ + "base64", + "svg", + "mermaid", + "file", + "svg_url", + "png_url" +]
1 tool update
- First observed
generate_mermaid_diagram
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clear and stands alone.
Since there is only one tool, naming consistency is not applicable, but the single name follows a clear descriptive pattern.
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.
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
Related MCP Connectors
Create and manage Mermaid.js flowcharts and diagrams with AI agents via MCP.
Generate org charts, MCD/ERD data models, and C4 architecture diagrams — pilot OrgGen AI via MCP.
Render, verify, describe, and safely edit Mermaid diagrams through MCP.
Create workflow, sequence, architecture, and mind map diagrams via AI assistants.
Related MCP Servers
- TypeScriptMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that converts text inputs into visualized flowcharts, enabling AI clients to generate high-quality Mermaid diagrams directly from natural language descriptions or structured text.12MIT
- FlicenseNot gradedqualityFmaintenanceNarasimhaponnada/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-
- AlicenseNot gradedqualityDmaintenanceEnables 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 npm1MIT