A
licenseB
qualityD
maintenanceA Model Context Protocol server that converts Markdown content into interactive mindmaps, allowing AI assistants to visualize hierarchical information through either HTML content or saved files.
1
696 PyPI
240
MIT
Markmap MCP Server
by jinzcdev
Markmap MCP 服务器
Markmap MCP Server 基于模型上下文协议 (MCP)，支持一键将 Markdown 文本转换为可交互的思维导图，并基于开源项目markmap构建。生成的思维导图支持丰富的交互操作，并支持导出为多种图片格式。
特征
🌠 Markdown 转思维导图：将 Markdown 文本转换为交互式思维导图
🖼️多格式导出：支持导出为 PNG、JPG 和 SVG 图像
🔄交互操作：支持缩放、展开/折叠节点等交互功能
📋 Markdown Copy ：一键复制原始 Markdown 内容
🌐自动浏览器预览：可在浏览器中自动打开生成的思维导图的选项
Related MCP server: MindManager MCP Server
先决条件
Node.js 运行时环境
安装
通过 Smithery 安装
要通过Smithery自动为 Claude Desktop 安装 Markmap MCP 服务器：
npx -y @smithery/cli install @jinzcdev/markmap-mcp-server --client claude手动安装
# Install from npm
npm install @jinzcdev/markmap-mcp-server -g
# Basic run
npx -y @jinzcdev/markmap-mcp-server
# Specify output directory
npx -y @jinzcdev/markmap-mcp-server --output /path/to/output/directory或者，您可以克隆存储库并在本地运行：
# Clone the repository
git clone https://github.com/jinzcdev/markmap-mcp-server.git
# Navigate to the project directory
cd markmap-mcp-server
# Build project
npm install && npm run build
# Run the server
node build/index.js用法
将以下配置添加到您的 MCP 客户端配置文件中：
{
"mcpServers": {
"markmap": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@jinzcdev/markmap-mcp-server",
"--output",
"/path/to/output/directory"
]
}
}
}[！提示]
该服务支持以下环境变量：
MARKMAP_DIR：指定思维导图的输出目录（可选，默认为系统临时目录）优先注意事项：
当同时指定
--output命令行参数和MARKMAP_DIR环境变量时，命令行参数优先。
可用工具
Markdown 转思维导图
将 Markdown 文本转换为交互式思维导图。
参数：
markdown：要转换的 Markdown 内容（必需字符串）open：是否在浏览器中自动打开生成的思维导图（可选布尔值，默认为false）
返回值：
{
"content": [
{
"type": "text",
"text": "JSON_DATA_OF_MINDMAP_FILEPATH"
}
]
}执照
该项目已获得 MIT 许可。
Available Tools
1 toolmarkdown_to_mindmapB
Convert a Markdown document into an interactive mind map
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| markdown | Yes | Markdown content to convert into a mind map | |
| open | No | Whether to open the generated mind map in a browser (default: false) |
TDQS
B3.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the conversion action but fails to describe key behavioral traits such as what format the mind map output takes (e.g., file, URL, visual representation), whether the conversion is reversible, any rate limits, or error handling. This leaves significant gaps for an agent to understand how to interact with the tool effectively.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded with the core action, making it easy to parse and understand quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of a conversion tool with no annotations and no output schema, the description is incomplete. It lacks details on the output format (e.g., how the mind map is returned or accessed), potential side effects, or any prerequisites for successful conversion. This leaves the agent with insufficient context to use the tool reliably.
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?
Schema description coverage is 100%, so the input schema already documents both parameters ('markdown' and 'open') thoroughly. The description adds no additional meaning beyond what the schema provides, such as examples of Markdown content or implications of the 'open' parameter. Baseline 3 is appropriate as the schema handles the heavy lifting.
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 specific action ('Convert') and the resources involved ('Markdown document' into 'interactive mind map'), leaving no ambiguity about what the tool does. It distinguishes the transformation process explicitly, which is sufficient even without sibling tools for comparison.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when converting Markdown to a mind map, but provides no explicit guidance on when to use this tool versus alternatives (e.g., other conversion tools or manual methods). Since there are no sibling tools listed, this omission is less critical, but it still lacks proactive 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
- First observed
markdown_to_mindmap
TDQS
A3.5/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct and singular.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern (markdown_to_mindmap), establishing a consistent naming convention for the server.
Tool Count2/5
One tool is too few for a server's typical scope, as it limits functionality and may indicate an incomplete or overly narrow implementation. However, it is not as extreme as a trivial single tool, so it avoids the lowest score.
Completeness3/5
The tool provides a core conversion function, but there are notable gaps such as missing operations for editing, saving, or loading mind maps, which could hinder agent workflows. The surface is functional but not fully comprehensive.
Maintenance
ActivityStale
ResponsivenessNo issues
Related MCP Connectors
Turn outlines and hierarchical notes into interactive mind maps through a hosted remote MCP server.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Markdown-based note-taking with a hosted MCP server. Your notes serve you and your AI.
A Model Context Protocol server for Wix AI tools
Related MCP Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables LLMs to interact with MindManager mind maps, allowing retrieval of mind map structures and export to formats like Mermaid, Markdown, and JSON.1111MIT
- AlicenseDqualityCmaintenanceAn MCP server that allows LLMs to create structured Xmind mind maps with hierarchical topic structures, supporting features like notes, labels, and markers.174 npm45MIT
- FlicenseNot gradedqualityDmaintenanceA powerful Model Context Protocol server that automatically generates Mermaid diagrams from code and provides SVG beautification features.1-