Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MINDMAP_DIRNoDirectory where diagrams are stored. Each diagram is one JSON file in ~/.plugmcp/mindmap/ by default; set MINDMAP_DIR to keep them somewhere else.
MINDMAP_ALLOWED_HOSTSNoHost names you serve when running with --http (which serves MCP at http://127.0.0.1:3333/mcp). Set this to accept other computers, and put it behind HTTPS.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Mind Map shows ideas to the user as a diagram in the chat. Its tools exist to help the user see what you mean. When your answer would be a long list, plan, breakdown, process or comparison, call visualize so the user can see it, then add at most two sentences of text. Do not repeat the diagram as text. The user can edit the diagram, comment on a node and ask about a node. You are told what they did. Answer by calling edit_diagram on the same docId, so the diagram changes in place. You send structure and labels only. Never send positions, sizes or colors: the user picks the look.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
visualizeA

Show an idea to the user as a diagram instead of a long text. Pick the structure from what the content is: exploring a topic -> mindmap; a hierarchy or parts of a whole -> org or logic; steps and decisions -> flowchart; causes of a problem -> fishbone; events in order -> timeline; who does what -> swimlanes (give lanes, and a lane on each node); a long list to read top to bottom -> outline. Rules: labels of 1-5 words; 3-7 children per node; at most 3 levels and about 30 nodes at first; put detail in note. Give every node a short id. For a tree set parent on every node but the root. For a flowchart leave parent out and join the nodes with edges; label the edges out of a decision. The first node is the root or the start. Send no positions and no colors. To show a diagram again, pass only its docId. To change one that is on screen, use edit_diagram, not this tool.

edit_diagramA

Change a diagram that is already on screen. Use it after the user edits, comments on or asks about a node, and for any refinement. Do not call visualize again for that. Ops apply in order and address nodes by id. A new node's id can be used by later ops in the same call. The open diagram updates itself.

get_diagramA

Read a diagram as an indented outline with node ids, the user's comments, and what the user changed on the canvas. Use it before editing when you are unsure of the current state, or when the client cannot show the diagram. Without docId it reads the most recent one.

load_stateC

The view reads the diagram, or learns it is up to date.

save_stateC

The view saves what the user changed on the canvas.

exportC

The view writes the diagram to a file on this machine.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
visualize-view

TDQS

B3.2/5.0

Scored across 6 tools

Disambiguation4/5

visualize (create) and edit_diagram (modify) have clearly separate roles, and get_diagram reads state. The remaining three (load_state, save_state, export) are view-side plumbing whose boundaries are fuzzier — load_state's description ('reads the diagram, or learns it is up to date') is vague and overlaps conceptually with get_diagram.

Naming Consistency3/5

edit_diagram, get_diagram, load_state, save_state follow a consistent verb_noun pattern, but visualize and export are bare verbs with no noun object, and the noun spelling varies (diagram vs. state). Readable but not uniform.

Tool Count4/5

Six tools is a reasonable scope for a diagram server. However, three of the six (load_state, save_state, export) are client/view plumbing rather than agent-facing capabilities, which makes the set feel slightly padded relative to the core visualize/edit/get trio.

Completeness4/5

The core lifecycle is covered: create (visualize), read (get_diagram), update (edit_diagram), and export. Missing a delete/remove-diagram operation and any listing of existing diagrams, but these are minor gaps an agent can work around.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues