Skip to main content
Glama
BangyiZhang

Xmind Generator MCP Server

by BangyiZhang

Xmind 生成器 MCP 服务器

用于生成 Xmind 思维导图的 MCP(模型上下文协议)服务器。该服务器允许法学硕士 (LLM) 通过 MCP 协议创建结构化思维导图。

特征

  • 生成具有分层主题结构的 Xmind 思维导图

  • 支持主题注释、标签和标记

  • 保存思维导图到本地文件

  • 轻松与 Claude Desktop 和其他 MCP 客户端集成

Related MCP server: MCP Thinking Server

先决条件

  • Node.js :需要版本 18 或更高版本

  • Xmind :安装Xmind桌面应用程序来打开和编辑生成的思维导图

  • Claude Desktop :需要使用此工具作为扩展

使用 Claude Desktop 进行设置

选项 1:使用 npx(推荐)

  1. 创建或编辑 Claude Desktop 配置文件:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

  2. 添加以下配置:

    {
      "mcpServers": {
        "xmind-generator": {
          "command": "npx",
          "args": ["xmind-generator-mcp"],
          "env": {
            "outputPath": "/path/to/save/xmind/files",
            "autoOpenFile": "false"
          }
        }
      }
    }
  3. 重启Claude桌面

  4. 开始在对话中使用 Xmind 生成器

选项 2:本地安装

  1. 克隆存储库:

    git clone https://github.com/BangyiZhang/xmind-generator-mcp.git
    cd xmind-generator-mcp
    npm install
    npm run build
  2. 创建或编辑 Claude Desktop 配置文件:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

  3. 添加以下配置:

    {
      "mcpServers": {
        "xmind-generator": {
          "command": "node",
          "args": ["path/to/xmind-generator-mcp/dist/index.js"],
          "env": {
            "outputPath": "/path/to/save/xmind/files",
            "autoOpenFile": "false"
          }
        }
      }
    }
  4. path/to/xmind-generator-mcp替换为克隆项目的实际路径

  5. 重启Claude桌面

  6. 开始在对话中使用 Xmind 生成器

注意env部分是可选的。它允许您为服务器设置环境变量:

  • outputPath :Xmind 文件的默认保存目录或文件路径。此设置可以通过工具调用中的outputPath参数进行覆盖。

  • autoOpenFile :控制生成的 Xmind 文件是否自动打开。设置为“false”表示禁用自动打开(默认为“true”)。

可用工具

生成思维导图

从主题的层次结构生成 Xmind 思维导图。

参数:

  • title (字符串):思维导图的标题(根主题)

  • topics (数组):思维导图中要包含的主题数组

    • title (字符串):主题的标题

    • ref (字符串,可选):主题的参考 ID

    • note (字符串,可选):主题的注释

    • labels (字符串数组,可选):主题的标签

    • markers (字符串数组,可选):主题的标记(格式:“Category.name”,例如“Arrow.refresh”)

    • children (数组,可选):子主题数组

  • relationships (数组,可选):主题之间的关系数组

  • outputPath (字符串,可选):Xmind 文件的自定义输出路径。如果已设置,则覆盖环境变量。

例子

以下是如何使用generate-mind-map工具的示例:

{
  "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"
        }
      ]
    }
  ]
}

执照

麻省理工学院

Available Tools

1 tool
generate-mind-mapD
ParametersJSON Schema
NameRequiredDescriptionDefault
filenameYesThe filename for the XMind file (without path or extension)
outputPathNoOptional custom output path for the XMind file. If not provided, the file will be created in the temporary directory.
relationshipsNoOptional array of relationships between topics
titleYesThe title of the mind map (root topic)
topicsYesArray of topics to include in the mind map

TDQS

D1/5.0
Behavior1/5

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.

Conciseness1/5

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.

Completeness1/5

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.

Parameters1/5

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.

Purpose1/5

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.

Usage Guidelines1/5

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedgenerate-mind-map

TDQS

D1.8/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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

ActivitySlowing
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    D
    quality
    D
    maintenance
    An 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.
    1
    51 npm
    1
    MIT
  • A
    license
    B
    quality
    B
    maintenance
    MCP server that enables LLMs to create and edit draw.io diagrams using high-level intent commands, with automatic layout and styling.
    4
    5 npm
    4
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    An 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.
    8
    -