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.
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.
- 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
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.
One command — uvx mindmap-mcp-server --return-type html