nodeland-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@nodeland-mcp Create a concept map for our Q3 roadmap and share the NodeLand link."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
nodeland-mcp
NodeLand is the persistent destination where agent output becomes an editable map — not a one-shot Mermaid render that dies with the chat.
This MCP server talks to the NodeLand Maps API. Agents emit concepts + relations; NodeLand stores the map, runs layout, and returns a URL the human can open, share, embed, and keep editing.
Demo maps (open these)
Replace these with maps you create during a real agent session before publishing:
Create your own with Claude/Cursor below, then paste the live URL here — the artifact is the demo.
Related MCP server: MegaMemory
What you get
Tool | When to use |
| Turn a topic into a shareable map (returns |
| Keep writing into the same map across a conversation |
| Read concepts/relations summary (not raw Cytoscape JSON) |
| Find an existing map id |
Resource: nodeland://templates — named layouts (StandardMindMapTemplate, TonyBuzzanTemplate, Tree TD / Tree LR, …).
Maps are public by default so the link works without login. Pass isPublic: false only when the user asks for private.
1. Get an API key (the real onboarding step)
Sign up / log in at nodeland.io
Open Settings → API Keys
Generate a key with
maps:readandmaps:writeCopy it once — it is shown only at creation time
2. Install in your agent
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"nodeland": {
"command": "npx",
"args": ["-y", "nodeland-mcp"],
"env": {
"NODELAND_API_KEY": "YOUR_API_KEY"
}
}
}
}Claude Code
claude mcp add nodeland --env NODELAND_API_KEY=YOUR_API_KEY -- npx -y nodeland-mcpCursor
Cursor Settings → MCP → add server:
{
"mcpServers": {
"nodeland": {
"command": "npx",
"args": ["-y", "nodeland-mcp"],
"env": {
"NODELAND_API_KEY": "YOUR_API_KEY"
}
}
}
}Optional staging:
"NODELAND_BASE_URL": "https://staging.nodeland.io"3. Try it
Ask the agent:
Map the central concepts of [topic], put a short markdown description on each node, and give me the NodeLand link.
Then open the URL in a private/incognito window — it should render without signing in.
Config
Env | Required | Default |
| yes | — |
| no |
|
The key is never logged. Missing key fails fast with a readable message.
Local development
git clone https://github.com/nodeland/nodeland-mcp.git
cd nodeland-mcp
npm install
npm run build
NODELAND_API_KEY=... npm startSmoke test (creates a public map and fetches the URL without credentials):
NODELAND_API_KEY=... NODELAND_BASE_URL=https://staging.nodeland.io npm run smokeInspector:
npx @modelcontextprotocol/inspector npx nodeland-mcpLicense
MIT
Available Tools
4 toolsadd_to_mapAdd concepts to an existing 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.
Inputs: mapId (required), concepts, template, relations.
create_mapCreate NodeLand 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.
Inputs: title (required), concepts (required), isPublic, language, +2 more.
get_mapGet map summaryA
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.
Inputs: mapId (required).
list_mapsList NodeLand mapsA
List maps owned by the API key's user. Use to find an existing map id before get_map or add_to_map.
Inputs: limit, search.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Capability registry for the agentic economy. Semantic search over verified MCP server listings.
Hosted MCP server for live public-data APIs and Skills for AI agents.
Cloud-hosted MCP server for durable AI memory
Build your own tools from chat: design, test and host them on a shareable MCP server URL.
Related MCP Servers
- AlicenseDqualityDmaintenanceAn MCP server that enables users to generate structured XMind mind maps with hierarchical topics, notes, and labels through natural language. It features automatic file saving to the local Documents folder and can automatically open generated maps in the XMind application.129 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets coding agents build and query a persistent knowledge graph of concepts, architecture, and decisions, enabling them to remember across sessions.123 npm736MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server exposing Kiuwo's mind map APIs as tools for creating, searching, expanding, and fetching mind maps.1-
- AlicenseNot gradedqualityDmaintenanceOfficial MCP server for creating, reading, and updating mind maps on coret.id from AI agents. Changes appear live in the Coret editor.1MIT