freeplane-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FREEPLANE_MCP_HOST | No | Host to bind the MCP HTTP server to. | 127.0.0.1 |
| FREEPLANE_MCP_PORT | No | Port to bind the MCP HTTP server to. | 8000 |
| FREEPLANE_GRPC_HOST | No | Host of the Freeplane gRPC plugin. | 127.0.0.1 |
| FREEPLANE_GRPC_PORT | No | Port of the Freeplane gRPC plugin. | 50051 |
| FREEPLANE_GRPC_TIMEOUT | No | Timeout in seconds for Freeplane gRPC requests. | 10 |
| FREEPLANE_MCP_TRANSPORT | No | Transport for the MCP server: 'stdio' or 'http'. | stdio |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| export_mapA | Export the current Freeplane mind map to canonical JSON. Returns the whole map as a JSON string. Each node has at least "text" and "id"; optional fields include "children", "note", "detail", "link", "tags", "icons", "attributes", "background_color", "folded" and "relationships". |
| import_mapA | Import a mind map (canonical JSON) into the running Freeplane instance. |
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 2 tools
export_map and import_map have clearly opposite purposes and there is no overlap. An agent can unambiguously determine which to call based on the direction of data transfer.
Both tool names follow the same verb_noun pattern: export_map and import_map. The naming is simple, predictable, and perfectly matches the server's purpose.
Two tools is a very minimal set, but each covers one half of the map exchange workflow. It feels slightly thin for a general MCP server, though the scope is focused.
The two tools provide a complete round-trip: export the map as JSON and import it back. For this server's apparent purpose of whole-map synchronization, there are no obvious gaps.