No user-submitted related servers found.
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.