Markmap MCP Server vs Metabase
A side-by-side look at the Markmap MCP Server and Metabase MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Markmap MCP Server for data visualization work as a local process; choose Metabase for data visualization. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Markmap MCP Server when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
markdown_to_mindmap, list_mindmaps, get_mindmap.
Choose Metabase when
- You need dedicated capabilities in the Data Visualization domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 68/100 · Great | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 289 | 49,815 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Markmap MCP Server | View Metabase |
Tools & capabilities
Markmap MCP Server tools 4
markdown_to_mindmapConvert 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_mindmapsList 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_mindmapRetrieve 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_mindmapsPermanently 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.
Metabase tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Markmap MCP Server
{
"mcpServers": {
"jinzcdev-markmap-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jinzcdev/markmap-mcp-server"
]
}
}
}
Metabase
No confirmed install command for Metabase yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Markmap MCP Server is categorized under Data Visualization and uses a local stdio subprocess. Metabase belongs to Data Visualization and uses an install path we have not confirmed yet. Pick Markmap MCP Server for data visualization work and Metabase for data visualization.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Metabase has no confirmed install command yet — follow its own setup instructions.
Markmap MCP Server is listed as free. Auth: no auth required. Metabase is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add jinzcdev-markmap-mcp-server and metabase as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Markmap MCP Server has a quality signal of 68/100 (Great) with 5 views, 0 installs and 289 GitHub stars. Metabase has 41/100 (Fair) with 1 views, 0 installs and 49,815 GitHub stars.