XMind Generator MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| outputPath | No | Directory where XMind files will be saved | ~/Documents/XmindFiles |
| autoOpenFile | No | Automatically open generated files in XMind | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate-mind-mapD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'generate-mind-map' stands alone with a distinct purpose, making disambiguation trivially perfect.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'generate-mind-map' follows a clear verb_noun pattern, which would be consistent if more tools existed.
One tool is too few for a server named 'XMind Generator MCP', which suggests a domain of mind map generation and potentially related operations. A single tool feels thin and incomplete for this scope, lacking basic operations like editing, saving, or listing mind maps.
The tool surface is severely incomplete for mind map generation. With only a 'generate-mind-map' tool and no description, there are obvious gaps: no way to retrieve, update, delete, or manage mind maps, and no coverage of related functionalities like templates or exports, making it impossible for agents to perform meaningful workflows.