xmind-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_xmindA | Parse an entire XMind document (.xmind file) and return formatted output (Markdown or JSON). Markdown format is more token-efficient and recommended for large documents. JSON format includes structure summary and detailed metadata. Supports both Zen (modern) and Legacy (XMind 8) formats. |
| search_xmind_nodesA | Search for nodes in an XMind file by keyword (title/notes) or label. Returns matching nodes with breadcrumb paths. Useful for large mind maps to find specific topics without loading entire document. |
| get_xmind_node_branchA | Extract a specific node and its subtree (up to specified depth) from an XMind file. Useful for large mind maps to avoid token overload by retrieving only relevant branches. |
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 3 tools
Each tool has a clearly distinct purpose: parse the entire document, search nodes by keyword, and extract a specific branch. No ambiguity between these operations.
All tool names follow the consistent verb_noun snake_case pattern (parse_xmind, search_xmind_nodes, get_xmind_node_branch), making the API predictable.
Three tools is a well-scoped count for an XMind reading/exploration server. Each tool serves a distinct need without redundancy.
The tool set covers the full read-side lifecycle: full-document parsing, keyword search, and subtree extraction. There are no obvious gaps for the apparent purpose of exploring XMind files.