Generate and read XMind (.xmind) files via the published xmind-generator-mcp MCP server (npm), with a chat-first UX.
Generate and read XMind .xmind files using the published MCP server xmind-generator-mcp (npm).
This skill is chat-first:
.xmind and sends it back..xmind file that opens in XMind.The MCP tool generate-mind-map accepts Schema A JSON:
{
"title": "Root topic",
"filename": "mindmap-name-no-date",
"topics": [
{
"title": "Topic title (keep core info in the title)",
"note": "Optional: use sparingly; only when the title would be too long",
"labels": ["optional"],
"markers": ["Arrow.refresh"],
"children": [{"title": "Child topic"}]
}
]
}
Use npx [email protected] as the MCP server command:
mcporter call --stdio "npx -y [email protected]" generate-mind-map --args '{...}'
mcporter call --stdio "npx -y [email protected]" read-mind-map --args '{"inputPath":"/path/to/file.xmind","style":"A"}'
When a user sends an .xmind file and asks to “read/understand” it:
generate --output can be a directory (recommended) or a full .xmind path.outputPath environment variable (see below).Trigger phrases:
Language rule (important):
Filename rule (important):
one-day-trip-detailed in Chinese characters, but keep it short).hong-kong-1-day-itinerary).\\ / : * ? \" < > | → replace with -.Steps:
~/Desktop.note: use sparingly. Only put content in note when it would make the topic title too long or noisy. If the content is core to the plan, keep it in the title instead of hiding it in note.labels: add lightweight categorization (e.g. must-do/optional/rainy-day/budget/family-friendly).relationships: sparingly (mode A) — only for truly cross-branch links that add clarity./tmp/xmind-<ts>.json.generate-mind-map via mcporter stdio (npx [email protected]).
Capture/compute the output file path..xmind back in chat as an attachment.