mcp server
The MCP server exposes the architecture/wiki-engine over the Model Context Protocol. Any agent that speaks MCP gets these tools.
mind-map serves MCP over stdio when invoked as:
mind-map serve --stdio --dir ~/.mind-map/wiki
Wire that command into your agent's MCP client config (Claude Desktop, Copilot, etc.). The same binary that serves the architecture/web-ui also serves the MCP — just a different launch flag.
See agents/mcp-tools for the full reference. The headline ones:
-
search_pages— full-text concepts/search -
get_page— read a page including concepts/backlinks -
create_page/update_page/delete_page— write -
move_page— atomic rename -
list_pages— list, optionally by path prefix -
get_backlinks— incoming references -
register_sync— wire a path prefix to a guides/sync -
get_wiki_context— orientation: page count, top-level dirs, recent pages
The MCP layer is intentionally thin — every tool is a 5-10 line adapter over a Wiki method. The interesting logic lives in the architecture/wiki-engine. This keeps the surface auditable and ensures the HTTP API and MCP stay semantically equivalent.
graph LR
A[Agent] --MCP stdio--> S[MCP server]
S --calls--> E[Wiki engine]
B[Browser] --REST--> H[HTTP server]
H --calls--> E
- agents/index — why this matters
- agents/workflows — patterns
- architecture/http-api — the parallel REST surface
Sidebar search: results filtered + highlighted as you type
In-page search: match-highlighting in the rendered body