Mind Map MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_mindmapB | 根据输入内容生成思维导图 |
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
Only one tool exists, so there is no possibility of ambiguity.
With a single tool, naming consistency is trivial; the name 'generate_mindmap' follows a clear verb_noun pattern.
A single tool for generating mind maps feels thin; while it might cover the basic need, a typical mind map server could benefit from additional tools for tasks like listing, editing, or exporting.
The server only provides a generation tool; there are no tools for retrieval, update, or deletion of mind maps, leaving potential gaps in a full workflow.