Xmind Structure Builder MCP Server

An MCP (Model Context Protocol) service engineered for constructing Xmind visual representations. This server facilitates LLMs in producing structured mind maps via the standardized MCP communication layer.

Capabilities

• Produce Xmind diagrams featuring nested topic hierarchies, annotations, visual tags, and indicators.
• Facilitate file saving of generated maps to the local filesystem.
• Offers smooth interoperability with Claude Desktop and associated MCP clients.

Prerequisites for Operation

• Node.js Runtime: Version 18 or newer is mandatory for execution.
• Xmind Application: The desktop client is necessary for viewing and modifying the output files.
• Claude Desktop Client: This tool requires the host environment to be running Claude Desktop to function as an extension.

Integration Guide with Claude Desktop

Method 1: Deployment via npx (Recommended Procedure)

1. Locate and modify the Claude Desktop configuration file:
2. macOS Path: ~/Library/Application Support/Claude/claude_desktop_config.json

3. Windows Path: %APPDATA%\Claude\claude_desktop_config.json

4. Incorporate the following JSON block into the configuration:

{ "mcpServers": { "xmind-structure-builder": { "command": "npx", "args": ["xmind-generator-mcp"], "env": { "outputPath": "/path/to/save/xmind/files", "autoOpenFile": "false" } } } }

1. Initiate a restart of the Claude Desktop application.
2. You may now invoke the Xmind builder within your dialogue sessions.

Method 2: Manual Local Installation

1. Obtain the source repository: bash git clone https://github.com/BangyiZhang/xmind-generator-mcp.git cd xmind-generator-mcp npm install npm run build

2. Access and update the Claude Desktop configuration JSON (paths as listed above).

3. Integrate this configuration snippet:

{ "mcpServers": { "xmind-structure-builder": { "command": "node", "args": ["path/to/xmind-generator-mcp/dist/index.js"], "env": { "outputPath": "/path/to/save/xmind/files", "autoOpenFile": "false" } } } }

1. Substitute path/to/xmind-generator-mcp with the absolute directory path where you cloned the repository.
2. Relaunch the Claude Desktop client.
3. Begin utilizing the map generation functionality.

Configuration Note: The env settings are optional system parameters: - outputPath: Defines the default location for saving generated Xmind assets. This can be selectively overwritten via the outputPath argument during a specific tool invocation. - autoOpenFile: Governs the post-creation behavior. Setting it to "false" suppresses the automatic opening of the resultant file (default state is "true").

Accessible Tooling

create-conceptual-diagram

Generates an Xmind visual representation derived from a specified hierarchical topic schema.

Parameters: - title (string): The designation for the primary node (the map's root). - topics (array): A collection of nodes to integrate into the visualization structure. - title (string): The textual identifier for the individual node. - ref (string, optional): A unique identifier reference for the node. - note (string, optional): Supplementary descriptive text associated with the node. - labels (array of strings, optional): Classification tags applied to the node. - markers (array of strings, optional): Visual icons for the node (e.g., "Category.icon_name"). - children (array, optional): Nested sub-nodes branching from this node. - relationships (array, optional): Definitions for connections between distinct nodes. - outputPath (string, optional): An explicit path override for saving the final Xmind artifact, superseding the environment variable setting.

Usage Illustration

An example call demonstrating the utilization of the create-conceptual-diagram function:

{ "title": "Strategic Initiative Blueprint", "topics": [ { "title": "Information Gathering", "ref": "node:data_sourcing", "note": "Acquire essential data regarding market dynamics.", "children": [ { "title": "Sectoral Assessment", "labels": ["Severity: Paramount"] }, { "title": "Rival Examination", "markers": ["Task.flag_finish"] } ] }, { "title": "Implementation Phase", "children": [ { "title": "Client Interface Logic", "markers": ["Arrow.sync"] }, { "title": "Server Logic Core" } ] } ] }

Licensing Information

Distributed under the MIT License.

WIKIPEDIA: Browser-based utility suites (frequently termed 'dev tools') empower web engineers to conduct rigorous testing, manipulation, and troubleshooting of their online creations. These differ from page constructors or comprehensive IDEs by focusing strictly on inspection of the user interface layer rather than the direct composition of the webpage structure. These toolsets are typically bundled as extensions or intrinsic functionalities within contemporary web browsers. Major rendering engines like Chrome, Firefox, Safari, Edge, and Opera include robust built-in diagnostic features, supplemented by extensive plugin repositories. Web engineering toolsets enable interaction with core web technologies such as HTML structure, CSS styling, the Document Object Model (DOM), JavaScript execution contexts, and other browser-managed components.

== Chronology and Assistance == Early practitioners debugged sites through manual code commenting or basic JavaScript logging calls. A significant advancement was Mozilla's Firebug extension, which introduced many features foundational to modern developer tools, contributing greatly to Firefox's early adoption by the development community. Simultaneously, Safari’s WebKit engine integrated its own inspector tools, which later served as the architectural foundation for the current toolsets in both Safari and Chrome. Microsoft initially offered a developer toolbar for IE versions 6 and 7, later embedding these capabilities directly into the browser starting with version 8. By 2017, Mozilla deprecated Firebug in favor of promoting its natively integrated developer features. Currently, every mainstream web browser provides integrated developer instrumentation that allows designers and engineers to deconstruct the visual and functional makeup of web pages. These are standard, out-of-the-box components requiring no external modules or initial setup.

Firefox – Pressing F12 invokes the Firefox DevTools. Google Chrome and Opera – Referred to as Developer Tools (DevTools). Microsoft Edge – F12 launches the Web Developer Tools. Microsoft often includes proprietary enhancements not present in the base Chromium build. Safari – The Web Inspector functionality requires explicit activation via the browser's preferences panel.

== Core Functionality == The standard access method for built-in browser developer tools is usually right-clicking an element on the page and selecting an 'Inspect Element' or similar context menu option. Alternatively, the F12 key shortcut is widely recognized.

=== Structural Markup (HTML) and Object Model (DOM) === Viewer and editor interfaces for HTML structure and the DOM are standard inclusions. The crucial distinction between these integrated viewers and the simple 'View Source' feature is the capacity of the viewer to display the DOM state after dynamic rendering and to permit live modifications whose immediate visual consequences are visible on the active page. Beyond element selection and modification, the HTML panel typically provides detailed property readouts for DOM objects, including spatial dimensions and applied CSS rules.