nodeland-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODELAND_API_KEY | Yes | Your NodeLand API key (from Settings → API Keys) with maps:read and maps:write permissions. | |
| NODELAND_BASE_URL | No | Base URL for the NodeLand API. Default is https://nodeland.io. Set to https://staging.nodeland.io for staging. | https://nodeland.io |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_mapA | Create a persistent, shareable NodeLand map from concepts and relations. Use when the user wants a mind map, concept map, organogram, or study map they can open later and edit by hand. Do not invent Cytoscape JSON or coordinates — pass concepts/relations and a named template. After success, give the user the returned url. |
| add_to_mapA | Append concepts and relations to an existing NodeLand map, preserving what is already there. Use across a conversation when the agent keeps discovering structure — this is how the map stays the durable artifact, not a one-shot dump. |
| get_mapA | Fetch a NodeLand map as a compact concepts/relations summary (not raw Cytoscape JSON). Use before editing an existing map or to remind yourself what is already on it. |
| list_mapsA | List maps owned by the API key's user. Use to find an existing map id before get_map or add_to_map. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| templates | Named map layouts and when to use each one. Prefer these over inventing layout instructions. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: create a new map, add to an existing map, fetch one map, and list all maps. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: create_map, add_to_map, get_map, list_maps. The names are predictable and clearly indicate the action and resource.
Four tools is well-scoped for a focused map management server. Each tool covers a core operation without unnecessary bloat or fragmentation.
The lifecycle covers create, read, update (via add_to_map), and list operations. The only notable gap is a delete/remove operation, but it may be intentionally omitted since maps are shareable and editable externally.