How jinzcdev/markmap-mcp-server works
Project type and purpose
• This is a small, standalone Node.js/TypeScript CLI “server” implementing the Model Context Protocol (MCP). Its sole responsibility is to convert Markdown input into interactive mind maps (via markmap) and return MCP-compatible responses (JSON over stdio). It can also write the output to disk and optionally launch a browser preview.
File structure
• Top level:
• .github / .husky / CI & git hooks
• Dockerfile, smithery.yaml (packaging/publishing)
• src/…: TypeScript source subdivided into:
– common/registry-base.ts: base classes for a tool registry
– mcp/tools/: MCP tool implementations & registry
– markmap/createMarkmap.ts: core conversion logic
– utils/logger.ts: logging utility
– index.ts: CLI entry point
• tests/: vitest unit tests for the markmap service
• Config files: package.json, tsconfig.json, eslint.config.js, prettier.config.js, vitest.config.ts.
README for additional insights
• The README confirms it implements MCP over stdio, registers a tool named markdown-to-mindmap, reads Markdown, calls markmap under the hood, writes files to an output directory (--output or MARKMAP_DIR), then returns JSON with a link to the generated file, and can open the map in the browser.