mindmapio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MINDMAP_API_TOKEN | Yes | Your personal access token from mindmap.io settings. | |
| MINDMAP_API_BASE_URL | No | API base URL. | https://mindmap.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_mapsA | List the authenticated user's maps (metadata only, newest first). |
| get_mapA | Read one full map including its complete node tree. |
| get_nodeA | Read a single node without its descendants. Its children field still lists child ids for navigation. |
| get_subtreeA | Read a node and its descendants as a nested tree. Omit depth for the full subtree; 0 returns just the node. |
| create_mapB | Create a map owned by the token's user. Pass an initial node tree in data so node primitives have a parent. |
| delete_mapB | Delete a map and all of its nodes. |
| create_nodeA | Create a structural node under a parent. nodeId is optional; a uuid is minted when omitted so you can reference ids you choose. |
| update_nodeA | Apply a structural update to a node (content, note, type, collapsed flag, model). No LLM call, no metering. |
| delete_nodeA | Delete a node and all of its descendants (cascade). The root node cannot be deleted. |
| submit_nodeA | Run the LLM on a node and return the completed node. Blocks until ancestors finish; metered. |
| auto_expandA | Generate follow-up prompts as queued child nodes and return their ids. One level only; submit each child yourself. |
| retry_nodeB | Clear a node's error state and re-run its generation. Retrying an expand node with children needs force=true. |
| interrupt_nodeA | Stop an in-flight generation; a generating or queued node flips to interrupted with partial output preserved. Idempotent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose: map vs node operations, different scopes for reading (single node vs subtree vs full map), and distinct generation-related actions (auto_expand, submit_node, retry_node, interrupt_node). No overlapping or ambiguous tools.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_map, delete_node, get_subtree, list_maps). No mixing of conventions or vague verbs.
13 tools cover the full lifecycle of mind map management (CRUD for maps and nodes) plus AI generation features (expand, submit, retry, interrupt). The count is well-scoped for the domain.
The toolset covers creation, reading (with varying depth), updating, deletion, listing, and AI-powered node expansion with error handling (retry, interrupt). No obvious gaps for the stated purpose of mind map management with generation.