Xmind Generator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| outputPath | No | Default directory or file path where Xmind files will be saved. This can be overridden by the outputPath parameter in the tool call. | |
| autoOpenFile | No | Controls whether generated Xmind files are automatically opened after creation. Set to "false" to disable auto-opening (default is "true"). | 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
Server capabilities have not been inspected yet.
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 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.