In-depth architectural comparison of the Openzim Mcp and Markmap Mcp Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Openzim Mcp
Knowledge & Memory · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Markmap Mcp Server
Knowledge & Memory · Local stdio
Quality: 71/100 (Great) | Auth: No auth required
Verdict Summary: Choose Openzim Mcp if you need specialized Knowledge & Memory tools running via a local process. Choose Markmap Mcp Server if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Openzim Mcp when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: OPENZIM_MCP_TRANSPORT, OPENZIM_MCP_HOST, OPENZIM_MCP_AUTH_TOKEN.
Primary tools included: Supports ZIM archives from Kiwix Library, Advanced 8-tool schema plus Simple natural-language query mode, Archive-type presets for optimized retrieval per source.
Modern, secure MCP server for accessing ZIM format knowledge bases offline. Enables AI models to search and navigate Wikipedia, educational content, and other compressed knowledge archives with smart retrieval, caching, and comprehensive API.
An MCP server built on markmap that converts Markdown to interactive mind maps. Supports multi-format exports (PNG/JPG/SVG), live browser preview, one-click Markdown copy, and dynamic visualization features.
Category & Scope
Tools & Capabilities Breakdown
Openzim Mcp Tools (6)
Supports ZIM archives from Kiwix Library
Advanced 8-tool schema plus Simple natural-language query mode
Archive-type presets for optimized retrieval per source
Inbound link discovery and link graph extraction
Streamable HTTP and stdio transport modes
Caching and pagination for responsive queries
Markmap Mcp Server Tools (4)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Openzim Mcp is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Markmap Mcp Server belongs to Knowledge & Memory using local stdio subprocess. Select Openzim Mcp when you need capabilities focused on knowledge & memory and Markmap Mcp Server when you require tools for knowledge & memory.
Convert structured Markdown (headings # and nested lists -) into an interactive mind map HTML file, with optional server-side PNG/JPG/SVG export.
Use when the user wants a visual mind map/outline of structured content (architecture, plans, notes, hierarchies), or asks to visualize / mindmap / diagram. Do not use for flat unstructured text (restructure first), or to list/read existing outputs (use list_mindmaps / get_mindmap).
Behavior:
- WRITES files under the configured output dir. HTML is always written; image formats write an extra file. Reusing filename overwrites.
- html is fast (<1s). png/svg/jpg launch headless Chromium via Playwright (5–15s; requires: npm install playwright && npx playwright install chromium).
- Local only — no external APIs or third-party keys. Open mode=never: The server never opens the browser.
- Offline=false (server config).
Response:
- JSON {"htmlFilePath":"<path>","filePath":"<path>"} — htmlFilePath is always the HTML source; filePath is the primary artifact (HTML or image).
- Return mode=path: Paths JSON only — no inline content.
- Errors: isError:true with {"error","message"}.
list_mindmaps
List markmap* files (html/png/jpg/jpeg/svg) in the output directory, newest first. Read-only — no side effects. Missing/empty dirs return {"files":[]}.
Returns: {"outputDir","files":[{"name","filePath","size","mtimeMs","mtime"}]} (mtime is ISO 8601).
Use before get_mindmap to discover paths, or before cleanup_mindmaps to preview targets. Not for generating new mind maps (use markdown_to_mindmap).
get_mindmap
Retrieve a generated mind map file by absolute path. Read-only — no side effects. Only paths inside the configured output directory are allowed (path traversal denied).
Returns JSON {"filePath","mimeType","size"}. For text/html or image/svg+xml under 200KB, also appends a text content block. PNG/JPG return metadata only (no image block) — re-export via markdown_to_mindmap with format=png|jpg if the agent needs pixels.
On error: isError:true with {"error":"Failed to retrieve mind map","message"}.
Use list_mindmaps first to obtain a valid filePath. Prefer this over regenerating when the file already exists.
cleanup_mindmaps
Permanently delete markmap* files from the output directory. DESTRUCTIVE and irreversible when dryRun is false.
dryRun defaults to false — omitting it WILL delete. Always call once with dryRun=true to preview, then again with dryRun=false to commit. Prefer list_mindmaps beforehand.
Returns {"deleted":["<path>",...],"kept":<n>}; dryRun responses also include dryRun:true and do not delete.
Use instead of manual file deletion when pruning old generated mind maps.