Turn outlines and hierarchical notes into interactive mind maps through a hosted remote MCP server.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Render an interactive MCP app mind map when the user needs hierarchical structure shown visually instead of as prose. Use it for breaking down ideas, plans, study material, or systems into a root topic with nested branches; do not use it for tables, flowcharts, Mermaid/Graphviz diagrams, or plain text lists. Input `mindmap_markdown` must be a clean markdown tree with one `#` root heading and 2-space-indented bullet nesting. If the user gives prose, first reshape it into that hierarchy, then call this tool.
Markdown tree for a mind map. Preferred structure: one top-level heading for the root topic, then nested bullet points for branches and leaves using consistent 2-space indentation. Example: `# Product Launch Strategy - Marketing - Social Media - Twitter - LinkedIn - Email Campaign - Newsletter - Promo Codes - Engineering - QA Testing - Server Scaling - Final Deployment - Customer Support - Help Docs Updated - Support Training`. When the topic is suitable for emojis (e.g., marketing, events, social media, holidays, categories like food/travel), use relevant emojis in node names to make the diagram more appealing — like 📱 for Social Media or 🚀 for Launch. Avoid prose paragraphs, tables, fenced code blocks, and mixed list styles.
Optional short title for the mind map
Render an interactive MCP app mind map when the user needs hierarchical structure shown visually instead of as prose. Use it for breaking down ideas, plans, study material, or systems into a root topic with nested branches; do not use it for tables, flowcharts, Mermaid/Graphviz diagrams, or plain text lists. Input `mindmap_markdown` must be a clean markdown tree with one `#` root heading and 2-space-indented bullet nesting. If the user gives prose, first reshape it into that hierarchy, then call this tool.
| Argument | Type | Description |
|---|---|---|
| title | string | Optional short title for the mind map |
| mindmap_markdown* | string | Markdown tree for a mind map. Preferred structure: one top-level heading for the root topic, then nested bullet points for branches and leaves using consistent 2-space indentation. Example: `# Product Launch Strategy - Marketing - Social Media - Twitter - LinkedIn - Email Campaign - Newsletter - Promo Codes - Engineering - QA Testing - Server Scaling - Final Deployment - Customer Support - Help Docs Updated - Support Training`. When the topic is suitable for emojis (e.g., marketing, events, social media, holidays, categories like food/travel), use relevant emojis in node names to make the diagram more appealing — like 📱 for Social Media or 🚀 for Launch. Avoid prose paragraphs, tables, fenced code blocks, and mixed list styles. |
{
"type": "object",
"required": [
"mindmap_markdown"
],
"properties": {
"title": {
"type": "string",
"description": "Optional short title for the mind map"
},
"mindmap_markdown": {
"type": "string",
"description": "Markdown tree for a mind map. Preferred structure: one top-level heading for the root topic, then nested bullet points for branches and leaves using consistent 2-space indentation. Example: `# Product Launch Strategy\n\n- Marketing\n - Social Media\n - Twitter\n - LinkedIn\n - Email Campaign\n - Newsletter\n - Promo Codes\n- Engineering\n - QA Testing\n - Server Scaling\n - Final Deployment\n- Customer Support\n - Help Docs Updated\n - Support Training`. When the topic is suitable for emojis (e.g., marketing, events, social media, holidays, categories like food/travel), use relevant emojis in node names to make the diagram more appealing — like 📱 for Social Media or 🚀 for Launch. Avoid prose paragraphs, tables, fenced code blocks, and mixed list styles."
}
}
}