Mcp Xmind Server

What is Mcp Xmind Server about?

Mcp Xmind Server provides a Model Context Protocol (MCP) interface for working with XMind mind‑map files. It enables smart fuzzy searching, hierarchical content navigation, extraction of TODO tasks, link/reference harvesting, and bulk analysis across multiple XMind files while enforcing directory‑level security.

How to use Mcp Xmind Server?

1. Installation – Install via Smithery or manually with npm. The recommended quick‑start is:

   npx -y @smithery/cli install @41px/mcp-xmind --client claude
   

   or manually:

   npm install @modelcontextprotocol/sdk adm-zip zod
   npm install --save-dev typescript @types/node
   

2. Start the server – Provide one or more allowed directories:

   node dist/index.js <allowed-directory> [additional-directories...]
   

3. Invoke tools – Use the MCP JSON payloads such as search_nodes, extract_node, get_todo_tasks, etc., specifying the XMind file path and relevant arguments.

Key features of Mcp Xmind Server

• 🔍 Smart fuzzy search across mind maps
• 📝 Task management and TODO extraction
• 🌲 Hierarchical navigation and subtree extraction
• 🔗 Link and reference extraction
• 📊 Multi‑file analysis and comparison
• 🏷️ Label/tag support
• 📂 Recursive directory scanning for XMind files
• 🔒 Secure directory access with path validation

Use cases of Mcp Xmind Server

• Project planning – Quickly locate tasks, milestones, or feature ideas scattered across multiple mind maps.
• Knowledge base mining – Extract and index concepts, notes, and references for later retrieval.
• Compliance & audit – Scan mind maps for specific keywords or tags to ensure regulatory coverage.
• Team collaboration – Provide a searchable backend for shared XMind repositories, enabling assistants or bots to fetch context.
• Automation – Integrate with Claude Desktop or other agents to trigger actions based on mind‑map content.

FAQ from the Mcp Xmind Server

Q: Which directories can the server access? A: Only the directories passed as arguments when launching the server. All paths are normalized and validated.

Q: How do I run the server in production? A: Use the provided production configuration that invokes the package via npx:

{
  "xmind": {
    "command": "npx",
    "args": ["-y", "@41px/mcp-xmind", "/path/to/allowed"]
  }
}

Q: Can I query multiple XMind files at once? A: Yes, the read_multiple_xmind_files and search_xmind_files tools support batch processing.

Q: Do I need an API key? A: No external API key is required; the server runs locally.

Q: How do I add new search fields? A: The search_nodes tool accepts a searchIn array where you can specify fields like title, notes, or custom attributes.

MCP XMind Server

A Model Context Protocol server for analyzing and querying XMind mind maps. This tool provides powerful capabilities for searching, extracting, and analyzing content from XMind files.

Features

• 🔍 Smart fuzzy search across mind maps
• 📝 Task management and tracking
• 🌲 Hierarchical content navigation
• 🔗 Link and reference extraction
• 📊 Multi-file analysis
• 🏷️ Label and tag support
• 📂 Directory scanning
• 🔒 Secure directory access

Installation

Installing via Smithery

To install XMind Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @41px/mcp-xmind --client claude

Manual Installation

npm install @modelcontextprotocol/sdk adm-zip zod
npm install --save-dev typescript @types/node

Usage

Starting the Server

node dist/index.js <allowed-directory> [additional-directories...]

Available Tools

1. read_xmind

   • Parse and analyze XMind files
   • Extract complete mind map structure

2. get_todo_tasks

   • Extract and analyze TODO tasks
   • Include task context and hierarchy

3. list_xmind_directory

   • Recursively scan for XMind files
   • Filter and organize results

4. read_multiple_xmind_files

   • Process multiple files simultaneously
   • Compare and analyze across files

5. search_xmind_files

   • Search files by name patterns
   • Recursive directory scanning

6. extract_node

   • Smart fuzzy path matching
   • Ranked search results
   • Complete subtree extraction

7. extract_node_by_id

   • Direct node access by ID
   • Fast and precise retrieval

8. search_nodes

   • Multi-criteria content search
   • Configurable search fields

Examples

Search for Nodes

{
    "name": "search_nodes",
    "arguments": {
        "path": "/path/to/file.xmind",
        "query": "project",
        "searchIn": ["title", "notes"],
        "caseSensitive": false
    }
}

Extract Node

{
    "name": "extract_node",
    "arguments": {
        "path": "/path/to/file.xmind",
        "searchQuery": "Feature > API"
    }
}

List Tasks

{
    "name": "get_todo_tasks",
    "arguments": {
        "path": "/path/to/file.xmind"
    }
}

Configuration

Development Configuration

Example claude_desktop_config.json for development:

{
  "xmind": {
    "command": "node",
    "args": [
      "/Users/alex/Src/mcp-xmind/dist/index.js",
      "/Users/alex/XMind"
    ]
  }
}

Production Configuration

Example claude_desktop_config.json for production using npmjs:

{
  "xmind": {
    "command": "npx",
    "args": [
      "-y",
      "@41px/mcp-xmind",
      "/Users/alex/XMind"
    ]
  }
}

Security

• Only allows access to specified directories
• Path normalization and validation
• Error handling for invalid access attempts

Development

Building

npm run build

Type Checking

npm run type-check

MCP Inspector

npx @modelcontextprotocol/inspector node dist/index.js /Users/alex/XMind