markdown-to-mindmap-contentLABSCO SUMMARY
One conversion, but the return type is the decision that matters.
Returning the whole HTML lets the map render inline; returning a path keeps a large document from filling the context window, which the author flags as the token-saving option and the one to prefer for anything sizeable. Pick it at launch, because it is a flag rather than a per-call argument.
What it is
A converter built on markmap-cli. It takes Markdown headings and returns either the full HTML of an interactive mindmap or the path to a file it wrote, depending on how you start it.
What you get
- Markdown converted to an interactive mindmap as HTML, previewable inside a client that renders artifacts
- The same map written to a file instead, so only the path comes back and the response stays small
- An option to hide the toolbar, and an option for an offline-capable map
- In the Docker image, two named tools: markdown-to-mindmap-content and markdown-to-mindmap-file
Requirements
Install with pip install mindmap-mcp-server, run through uvx, or use the Docker image ychen94/mindmap-converter-mcp. The python and uvx paths need Node.js present, because the conversion runs markmap-cli. The return shape is fixed at launch with the --return-type flag, set to either html or filePath. On Windows the Docker route is the one the author recommends; the file route needs a directory mounted into the container.
Setup effort
One command — uvx mindmap-mcp-server --return-type html
USE CASES
01
Seeing the shape of a long document
Hand over the Markdown outline and get a mindmap back in the reply, rendered where the client supports it.
02
Mapping something too big to inline
Start with the file return type so the map is written to disk and only the path comes back - then open it in a browser.
03
Running it where npx misbehaves
Use the Docker image with an output folder mounted, which is the path the author recommends on Windows.
2 tools
Listed in project docs. Your client may show a different list.
markdown-to-mindmap-fileBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- uvx on PATH
- Node.js — the uvx and python routes run markmap-cli
Where it runs
All 3 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx mindmap-mcp-server --return-type htmlMCP Clients
Claude Desktop — uvx
CLAUDE DESKTOP — UVX · JSON
{
"mcpServers": {
"mindmap": {
"command": "uvx",
"args": [
"mindmap-mcp-server",
"--return-type",
"filePath"
]
}
}
}Claude Desktop — Python
CLAUDE DESKTOP — PYTHON · JSON
{
"mcpServers": {
"mindmap": {
"command": "python",
"args": [
"<YOUR_PATH_TO_MINDMAP_MCP_SERVER>/server.py",
"--return-type",
"html"
]
}
}
}This route runs the server file from a copy of the repository, not the installed package: git clone https://github.com/YuChenSSR/mindmap-mcp-server.git. <YOUR_PATH_TO_MINDMAP_MCP_SERVER>/server.py is the full path to mindmap_mcp_server/server.py inside that clone. The python it runs needs Python 3.10 or later with the mcp package (pyproject.toml: mcp>=1.2.0), and Node.js must be installed. Use --return-type filePath instead of html to get a saved file back.
Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"mindmap-converter": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-v",
"<YOUR_PATH_TO_OUTPUT_FOLDER>:/output",
"ychen94/mindmap-converter-mcp:latest"
]
}
}
}
