Xmind Generator MCP Server
The Xmind Generator MCP Server allows you to programmatically create and manage structured mind maps in Xmind format. With this server, you can:
Generate hierarchical mind maps with a root topic and nested subtopics
Customize topics by adding notes, labels, and markers
Define relationships between topics with titles and directional connections
Reference topics using IDs to establish connections
Save mind maps to a specified output path or temporary directory
Integrate easily with Claude Desktop and other MCP clients
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Xmind Generator MCP Servercreate a mind map for my project plan with research and development topics"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Xmind Generator MCP Server
An MCP (Model Context Protocol) server for generating Xmind mind maps. This server allows LLMs to create structured mind maps through the MCP protocol.
Features
Generate Xmind mind maps with hierarchical topic structures
Support for topic notes, labels, markers, and relationships
Save mind maps to local files
Read existing .xmind files and export an outline as Markdown
Easy integration with Claude Desktop and other MCP clients
Related MCP server: MCP Thinking Server
Prerequisites
Node.js: Version 18 or higher is required
Xmind: Install Xmind desktop application to open and edit the generated mind maps
Claude Desktop: Required to use this tool as an extension
Setup with Claude Desktop
Option 1: Using npx (Recommended)
Create or edit the Claude Desktop configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the following configuration:
{ "mcpServers": { "xmind-generator": { "command": "npx", "args": ["xmind-generator-mcp"], "env": { "outputPath": "/path/to/save/xmind/files", "autoOpenFile": "false" } } } }Restart Claude Desktop
Start using the Xmind generator in your conversations
Option 2: Local Installation
Clone the repository:
git clone https://github.com/BangyiZhang/xmind-generator-mcp.git cd xmind-generator-mcp npm install npm run buildCreate or edit the Claude Desktop configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the following configuration:
{ "mcpServers": { "xmind-generator": { "command": "node", "args": ["path/to/xmind-generator-mcp/dist/index.js"], "env": { "outputPath": "/path/to/save/xmind/files", "autoOpenFile": "false" } } } }Replace
path/to/xmind-generator-mcpwith the actual path to your cloned projectRestart Claude Desktop
Start using the Xmind generator in your conversations
Note: The env section is optional. It allows you to set environment variables for the server:
outputPath: Default directory or file path where Xmind files will be saved. This can be overridden by theoutputPathparameter in the tool call.autoOpenFile: Controls whether generated Xmind files are automatically opened after creation. Set to "false" to disable auto-opening (default is "true").
Available Tools
generate-mind-map
Generates an Xmind mind map from a hierarchical structure of topics.
Parameters:
title(string): The title of the mind map (root topic)topics(array): Array of topics to include in the mind maptitle(string): The title of the topicref(string, optional): Reference ID for the topicnote(string, optional): Note for the topiclabels(array of strings, optional): Labels for the topicmarkers(array of strings, optional): Markers for the topic (format: "Category.name", e.g., "Arrow.refresh")children(array, optional): Array of child topics
relationships(array, optional): Array of relationships between topicsoutputPath(string, optional): Custom output path for the Xmind file. This overrides the environment variable if set.
read-mind-map
Reads an existing .xmind file and exports it as a Markdown outline.
Parameters:
inputPath(string): Path to the.xmindfilestyle(string, optional): Markdown style. Currently supportsA(outline). (Breserved for future richer exports.)
Example:
{
"inputPath": "/path/to/file.xmind",
"style": "A"
}Example
Here's an example of how to use the generate-mind-map tool:
{
"title": "Project Plan",
"topics": [
{
"title": "Research",
"ref": "topic:research",
"note": "Gather information about the market",
"children": [
{
"title": "Market Analysis",
"labels": ["Priority: High"]
},
{
"title": "Competitor Research",
"markers": ["Task.quarter"]
}
]
},
{
"title": "Development",
"children": [
{
"title": "Frontend",
"markers": ["Arrow.refresh"]
},
{
"title": "Backend"
}
]
}
]
}License
MIT
Available Tools
1 toolgenerate-mind-mapD
| Name | Required | Description | Default |
|---|---|---|---|
| filename | Yes | The filename for the XMind file (without path or extension) | |
| outputPath | No | Optional custom output path for the XMind file. If not provided, the file will be created in the temporary directory. | |
| relationships | No | Optional array of relationships between topics | |
| title | Yes | The title of the mind map (root topic) | |
| topics | Yes | Array of topics to include in the mind map |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generate-mind-map' stands alone with a distinct purpose, making it impossible for an agent to misselect between multiple options.
The naming is trivially consistent as there is only one tool. It follows a clear verb_noun pattern ('generate-mind-map'), and with no other tools to compare against, there is no inconsistency in naming conventions.
A single tool is generally too few for a server's purpose, as it limits functionality and may not cover the domain adequately. For a mind map generator, one tool might suffice for basic generation, but it feels thin and could lack features like editing, saving, or retrieving maps, suggesting an under-scoped implementation.
The tool surface is severely incomplete for a mind map domain. With only a generation tool, there are obvious gaps such as no ability to retrieve, update, delete, or list existing mind maps. This will likely cause agent failures when trying to perform full lifecycle operations, as the server does not support basic CRUD functionality.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Turn outlines and hierarchical notes into interactive mind maps through a hosted remote MCP server.
MCP server for generating rough-draft project plans from natural-language prompts.
MCP server for AI dialogue using various LLM models via AceDataCloud
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseDqualityDmaintenanceAn MCP server that enables users to generate structured XMind mind maps with hierarchical topics, notes, and labels through natural language. It features automatic file saving to the local Documents folder and can automatically open generated maps in the XMind application.1611MIT
- AlicenseNot gradedqualityDmaintenanceA powerful MCP server that enhances LLMs with advanced sequential thinking capabilities, supporting 19 thinking modes for structured reasoning and complex cognitive tasks.17MIT
- AlicenseBqualityBmaintenanceMCP server that enables LLMs to create and edit draw.io diagrams using high-level intent commands, with automatic layout and styling.4174MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that lets Claude or ChatGPT read, create, and edit mind maps stored in a GitHub repository, with support for local and HTTP transport.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BangyiZhang/xmind-generator-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server