markmap

Markmap MCP Server converts Markdown text into interactive mind maps using the Markmap engine. Once running, you can access the Markmap tool via MCP by sending Markdown input to the server and receiving a structured mind map in return. The server exposes a markdown-to-mindmap capability that takes Markdown content and outputs a JSON representation of the mind map, which can be exported as images or opened in a browser preview depending on client capabilities. Use the provided Tools section to convert Markdown to a mind map and to inspect or export the resulting structure.

To use the server, configure your MCP client to start the Markmap MCP Server as shown in the installation and usage examples. The client passes Markdown through the markdown-to-mindmap tool, which returns a JSON object containing the mindmap data and related metadata. You can toggle automatic browser previews and control the output behavior via environment variables and command-line options supported by the server.

Prerequisites:

• Node.js v20 or above
• npm (comes with Node.js) or yarn

Installation steps:

1. Install via Smithery (automatic deployment): npx -y @smithery/cli install @jinzcdev/markmap-mcp-server --client claude

2. Manual installation (npm):

   • Basic run (global install): npm install @jinzcdev/markmap-mcp-server -g npx -y @jinzcdev/markmap-mcp-server
   • Specify output directory for generated mind maps: npx -y @jinzcdev/markmap-mcp-server --output /path/to/output/directory

3. Build from source and run locally: git clone https://github.com/jinzcdev/markmap-mcp-server.git cd markmap-mcp-server npm install npm run build node build/index.js

After installation, you can configure the MCP client to load the server as described in the usage section.

Notes and tips:

• Environment variable MARKMAP_DIR controls the output directory for generated mind maps. If not set, a system temporary directory is used. When both --output and MARKMAP_DIR are provided, the command-line option takes precedence.
• The MCP configuration example uses the npx-based invocation. Adjust the command or arguments if you prefer a local install or a different packaging approach.
• If you clone and build the project locally, ensure you run npm install before npm run build. The built server is typically available at build/index.js.
• This MCP server relies on the underlying Markmap project for rendering; ensure the runtime environment can access any required rendering resources.
• For production deployments, consider pinning the package version to avoid unexpected updates.