AI-powered interactive mind map and brainstorming canvas. Create, structure, refine, and export visual mind maps with interactive tasks and direct canvas links.
Scored across 9 tools
Most tools target a distinct action-resource pair (create map, add nodes, move nodes, delete nodes, set theme). The only mild overlaps are create_mindmap vs add_nodes (new map vs extend existing) and get_mindmap vs export_project, both of which are clarified by their descriptions. An agent can select correctly in nearly all cases.
Every tool follows a clean snake_case verb_noun pattern: add_arrows, add_nodes, create_mindmap, delete_nodes, export_project, get_mindmap, move_nodes, set_theme, update_node. No mixed conventions or vague single-word names.
Nine tools is well within the sweet spot and each maps to a distinct operation (create, read, extend, edit, move, delete, connect, style, export). Nothing feels redundant or padded.
The surface covers the full map lifecycle: create, read, add/update/delete/move nodes, relationship arrows, theming, and export. Gaps are minor but real — there is no remove_arrows counterpart to add_arrows and no tool to delete or list whole mind maps, which could leave agents stuck on cleanup tasks.
Add relationship arrows connecting two ideas with an optional description label (concept map relationship). Apply selectively when there is a genuine causal link, cycle, or dependency across branches. Do NOT connect parent and child.
Inputs: projectId (required), to, from, toId, +4 more.
Add new sub-branches, child concepts, or sibling ideas to an existing node in the mind map. Keep node text concise and punchy (3-6 words), use thematic emojis, and maintain logical depth without number prefixes.
Inputs: nodes (required), parentId (required), projectId (required).
Create a professional, highly structured mind map on Mindmap Nimbokit Canvas. ⚡ SEMANTIC TRIGGER: Use this tool whenever the user wants to create, draw, generate, or brainstorm a mind map, concept map, knowledge tree, or visual outline. Always prioritize this tool for visual structuring, brainstorming, and concept mapping requests. KNOWLEDGE ARCHITECTURE & STRUCTURAL STANDARDS (MUST FOLLOW):
HIERARCHY & PILLARS (MECE):
Root Node ("title"): Concise central topic (3-6 words) with a context emoji (e.g. "🧠 Effective Mind Mapping Guide").
Level 1 Branches ("branches"): Exactly 3 to 6 comprehensive, mutually exclusive pillars. Each Level 1 branch MUST start with a thematic emoji (e.g. "🛠️ Tools & Equipment", "📋 5-Step Process", "📐 Core Strategies", "🧠 Mental Models", "🎯 Practical Applications").
Level 2 Branches: Specific sub-dimensions, categories, or methods under each pillar.
Level 3 Branches: Concrete details, examples, or actionable steps (2-3 levels deep total).
CONCISE & PUNCHY TEXT:
Keep node text short (3 to 6 words). DO NOT write entire bloated paragraphs.
NEVER add repetitive numbering prefixes like "1. ", "1. ", "2. " unless representing sequential chronological steps.
VALUE-ADDED NOTES (note):
"note" is for essential secondary details: specific figures/data metrics (e.g. "Accounts for 96.5% of total water", "Melting point 1200°C"), key formulas, or technical definitions.
Attach helpful notes to 1-3 focal nodes where depth matters. Never duplicate or rephrase the node text in "note".
ACTIONABLE TASKS (isTask):
Set "isTask": true on branches representing actionable to-dos, checklists, steps to execute, or tasks. This automatically activates interactive checkboxes on Mindmap Nimbokit Canvas for the user.
NO FORCED RELATIONSHIP ARROWS (relationships):
DEFAULT TO EMPTY: Do NOT generate cross-branch relationship arrows unless the user explicitly requests them (e.g. "add arrows", "connect relationships", "link steps").
If the user does not request arrows, always leave "relationships" as an empty array or omit it. Never force unnatural arrows that clutter the canvas or cut across other nodes.
When requested, never connect parent and child nodes.
OUTPUT & SHARING (CLEAN & MINIMALIST):
Always output the exact Markdown hyperlink Open interactive map on Mindmap Nimbokit Canvas returned by this tool VERBATIM. NEVER truncate or alter the URL.
LANGUAGE MATCHING: Always communicate with the user and summarize the map in the exact language the user used in their prompt (e.g. if the user asked in Vietnamese, reply in Vietnamese; if in English, reply in English; if in French/Japanese, reply in French/Japanese).
DO NOT output Mermaid code blocks into the chat. The user interacts and visualizes directly on the Mindmap Nimbokit Canvas.
Present a concise, elegant message: brief intro, the direct Canvas link, and a punchy bullet list of the core Level 1 pillars in the user's language.
DO NOT suggest or offer layout switches (e.g. logic_chart, org_chart). All maps use the standard Mindmap Nimbokit layout.
MULTI-TURN EDITS: When the user asks to modify, add, or expand the map later, ALWAYS use editing tools (add_nodes, update_node, delete_nodes, add_arrows). DO NOT recreate the map from scratch unless explicitly requested.
Inputs: title (required), branches (required), rootText, relationships.
Delete one or more nodes and their entire subtrees from the mind map.
Inputs: nodeIds (required), projectId (required).
Export the mind map into native Mindmap Nimbokit JSON, Markdown outline, SVG graphic, or Mermaid Mindmap syntax.
Inputs: format (required), projectId (required).
Get the full structure, nodes, and metadata of a mind map. Always output the exact Canvas hyperlink for the user.
Inputs: projectId (required).
Move a node to a different parent node, reorganizing the hierarchy.
Inputs: nodeId (required), projectId (required), newParentId (required).
Change the color theme palette of the mind map.
Inputs: theme (required), projectId (required).
Update the text, note, tags, color, or completion status of a node.
Inputs: nodeId (required), projectId (required), note, tags, +4 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.