Rephonic vs Markmap MCP Server — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Rephonic vs Markmap MCP Server
In-depth architectural comparison of the Rephonic 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
Rephonic
Data Visualization · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: No auth required
Markmap MCP Server
Data Visualization · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Rephonic if you need specialized Data Visualization tools running via a hosted cloud SSE transport. Choose Markmap MCP Server if your workspace requires Data Visualization integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Rephonic when:
You need dedicated capabilities in the Data Visualization domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Research 3M+ podcasts with audience data, contacts, episodes, transcripts, charts, and sponsors.
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.
Search for podcasts by topic, title, or publisher with advanced filters.
search_episodes
Search for episodes by keyword across titles, show notes, and transcripts.
autocomplete
Get suggested keywords and matching podcasts for a search query.
find_podcast
Resolve a Rephonic podcast from an Apple/iTunes ID, Spotify ID, YouTube channel ID, or RSS feed URL. Use this first when you already have one of those identifiers.
lookup_podcast
Look up a podcast's metadata, chart rankings, and latest episodes by its Rephonic ID.
podcast_people
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).
Rephonic is categorized under Data Visualization and uses a remote streaming HTTP/SSE transport. In contrast, Markmap MCP Server belongs to Data Visualization using local stdio subprocess. Select Rephonic when you need capabilities focused on data visualization and Markmap MCP Server when you require tools for data visualization.
Get hosts and guests of a podcast with contact details and social profiles.
podcast_demographics
Get estimated listener demographics (age, education, profession, income, location).
podcast_promotions
Get sponsors and cross-promotions from a podcast's episodes.
list_episodes
List all episodes for a podcast in chronological order.
get_episode
Look up metadata for an individual episode.
episode_transcript
Get the full transcript for an episode.
contacts
Get email contacts, contact pages, and social accounts for a podcast.
+14 more tools listed on main page
Markmap MCP Server Tools (4)
markdown_to_mindmap
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.