MagicTrees MCP server

Your trees, inside every agent you use

Connect Claude, Cursor or any MCP agent to MagicTrees. It can build a tree from a conversation or a document, grow it with AI, read any branch into its context, and keep your plans up to date — all as you, in your own trees.

Connect your agent See the 7 tools

Included with Pro and Max.

What is MCP?

The Model Context Protocol is an open standard that lets AI apps use outside tools. Add the MagicTrees MCP server to an app that supports it — Claude Desktop, Claude Code, Cursor, and a growing list of agents — and the AI you're already talking to can open, read and change your trees for you. No copying and pasting between windows: you ask, and the tree updates.

What you can do with it

Your thinking stays in one living tree, whichever AI you're working in.

Turn a conversation into a tree

Ask Claude to map out what you just talked through. It builds the whole tree — every branch, with descriptions — in one call, ready to open on your canvas.

trees.create

Turn a document into a tree

Hand your agent a spec, meeting notes or a brief. It outlines it as a tree and attaches the source file to the root, so later growth can draw on it.

trees.createfiles.upload

Grow from wherever you work

“Grow the Risks branch two levels deeper.” Your agent runs the same AI growth the canvas uses, with the whole tree as context, and the new ideas land in your tree.

grow

Pull a tree into context

Before it writes code or a document, your agent reads the outline, then pulls in only the branch it needs — or exports the tree as Markdown.

nodes.shapenodes.get_branchtrees.export

Keep a project plan current

At the end of a session, the agent marks what's done with node types, colours and fields, moves what changed and adds what's next — in one all-or-nothing batch.

batchnodes.update

Stay organized as you go

File trees into projects that share AI context, attach outputs to the nodes they came from, and turn on a tree's public link when it's ready to share.

projects.move_treefiles.attach_to_nodetrees.share

The tools

7 tools your agent sees as soon as it connects. Every change is recorded in the tree's history, just like an edit on the canvas.

Trees and nodes

Create whole trees, read exactly the part you need, and edit any node.

`trees`

List, read and manage your trees — including creating a complete tree, with every branch, in one call.

listreadsyour trees
getreadsone tree, in full
exportreadsa tree as JSON or Markdown
createwritesa new tree — empty, from a full branch structure, from a template, or forked from a shared tree
importwritesa whole tree from JSON
updatewritesname, context, pin and settings
duplicatewritesa copy of a tree
sharewritesturn its public link on or off
deletewritesa tree

`nodes`

Read and edit the nodes inside one tree. Reads are sized for an agent's context window: see the outline first, then pull only the branch you need.

shapereadsthe tree's outline: ids and sizes, no content
getreadsone node
get_branchreadsa branch, bounded by depth and node count, with its size
addwritesa child node, with a description
updatewritesname, description, context, node type, colour and custom fields
movewritesa node to a new parent or position
reorder_childrenwritesa node's children
set_collapsedwritesfold or unfold a branch
deletewritesa node, or only its children

`batch`

Up to 50 node edits to one tree as a single commit — all or nothing. A node added in the batch can be named and edited again later in the same batch.

operationswritesadd, update, delete, move, reorder and fold, in one call

AI growth

The same growth the canvas uses, aware of the whole tree.

`grow`

Run an AI growth pass on a node: new children for the node, or for its children, all its descendants or every leaf. Optionally say how many and steer it with a prompt.

growwritesscope node | children | descendants | leaves, 1–50 ideas, custom prompt

Spends your plan's AI credits, exactly as growing in the app does.

Projects and files

Keep related trees together, and give the AI your documents to work from.

`projects`

Projects group trees and share AI context between them.

listreadsyour projects
getreadsone project
createwritesa project, with a description and shared context
updatewritesname, description and context
move_treewritesfile a tree into a project, or take it out
deletewritesa project

`files`

Attach files to a tree or a node — as context the AI reads, or as an output you keep.

listreadsa tree's or a node's files
getreadsa file's contents
uploadwritesa file (base64), optionally onto a node
attach_to_nodewritesa file to a node, as context or output
detach_from_nodewritesa file from its node
deletewritesa file

Up to 10 MB per file.

Account

So an agent can check before it spends.

`account`

Your plan, credit balance, today's usage, and what your plan allows.

get_usagereadscredits and today's usage
get_capabilitiesreadsyour plan's limits and MCP access

Connect in two steps

1. Get your API key
In MagicTrees, open Settings → API Key and generate a key. It starts with mt_live_ and is shown once, so copy it somewhere safe.
2. Add the server to your agent
The server URL is https://mcp.magictrees.ai/mcp. Send your key as a Bearer token in the Authorization header.

Claude Desktop — claude_desktop_config.json (through mcp-remote)

{
  "mcpServers": {
    "magictrees": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://mcp.magictrees.ai/mcp",
        "--header", "Authorization:${MAGICTREES_AUTH}"
      ],
      "env": { "MAGICTREES_AUTH": "Bearer mt_live_your_key" }
    }
  }
}

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "magictrees": {
      "url": "https://mcp.magictrees.ai/mcp",
      "headers": { "Authorization": "Bearer mt_live_your_key" }
    }
  }
}

Claude Code — in a terminal

claude mcp add --transport http magictrees https://mcp.magictrees.ai/mcp \
  --header "Authorization: Bearer mt_live_your_key"

Some hosts only accept OAuth for remote MCP servers and have no place to paste a key. The MagicTrees server signs in with your API key, so it can't be added there that way — connect from a client that lets you set a header, like the ones above.

Included with Pro and Max

The MCP server comes with the Pro and Max plans. It isn't part of Starter or the free trial, and it turns on when your paid plan starts.
Growing with AI spends your plan's credits, exactly as it does in the app. Reading and editing don't.
If your plan ends, the key stops working until you're on Pro or Max again.

See plans

Keep your key safe

Treat the key like a password: anyone holding it can read and change your trees. Keep it out of shared files and code repositories.
If it ever leaks, regenerate it in Settings → API Key. The old key stops working at once. There's one active key per account.
An agent works only in your own trees. Nodes it creates are marked as made by AI over MCP, and each key is limited to 60 requests a minute.

Let your agent grow the tree

Included with Pro and Max. Get your key in Settings → API Key.

Get your API key Compare plans