Let Claude build in your TabTree.
Claude reads your maps and kanban boards, creates new ones from a conversation, and adds or moves cards for you — in your account, on every device, and in the team spaces you belong to.
TabTree-Connector.mcpb · 170 KB · macOS, Windows, Linux · with Pro and Team, and during your 14-day trial
SHA-256 136ba0698406d445e21b71837225a9a50dc341bbe1381d4f6cf3b61594d5764c
One address: https://tabtree.app/mcp
ChatGPT, claude.ai, Cursor and any app that speaks MCP connect by address. The app opens a TabTree page: sign in, read what it will be able to do, press Allow. No key to copy.
Add a custom connector
Settings → Connectors → Add custom connector, paste https://tabtree.app/mcp, then
Connect and allow TabTree.
Add a connector
In ChatGPT's settings, open Apps & Connectors, create a connector with the address
https://tabtree.app/mcp and OAuth sign-in, then allow TabTree.
One line of JSON
In mcp.json: { "mcpServers": { "tabtree": { "url": "https://tabtree.app/mcp" } } }.
Cursor opens the sign-in page the first time.
Claude Code: claude mcp add --transport http tabtree https://tabtree.app/mcp
Every app you connect appears in TabTree → Settings → Claude connector as a key. Revoke disconnects it.
What an app reads goes to that app's provider — see our privacy policy.
Three steps, two minutes.
Create a connector key
In TabTree, open Settings → Account → Claude connector and press Create a connector key.
It is shown once — copy it. It starts with tt_live_.
Double-click the file
Open TabTree-Connector.mcpb. Claude Desktop shows its install screen and asks for your key —
paste it. Nothing else to install.
Ask Claude
“Make a kanban for our launch with these tasks.” The board appears in TabTree, ready on your laptop and your phone.
No account yet? Start free — the key lives in your account, and the trial includes the connector.
The maps Claude makes are waiting for you everywhere you sign in.
One line, or one block of JSON.
Any client that speaks MCP can use the connector. This route needs Node.js 18 or later.
claude mcp add tabtree --scope user \
-e TABTREE_API_KEY="tt_live_…" \
-- npx -y tabtree-mcp
{
"mcpServers": {
"tabtree": {
"command": "npx",
"args": ["-y", "tabtree-mcp"],
"env": { "TABTREE_API_KEY": "tt_live_…" }
}
}
}
Talk to Claude. The board moves.
“Turn these meeting notes into a mind map.”
A new map in your library, branches and all.
“Make a kanban for the launch: these eight tasks, Sara owns the design ones, due Friday.”
Columns, cards, owners and dates in one go.
“Add the three follow-ups from this call to the sprint board, in Doing.”
The cards land on the board by themselves.
“Move ‘Write the brief’ to Done and give the press kit a red label.”
Moved and labelled — ⌘Z undoes it.
“Plan the next six weeks as a Gantt.”
A timeline with start and due days.
“Draw our onboarding flow as a board.”
Shapes and arrows that stay anchored.
A card can carry everything the board shows: an owner, start and due days, a priority, colour labels, a time estimate, a lever, a note — a meeting link in it becomes clickable — and sub-tasks.
What applies by itself, and what waits for you.
Adding and moving
- New maps, kanbans, notes, Gantts and boards
- New cards and branches, cards moved or ticked
- Owner, dates, priority, labels, estimate, lever, comments
Rewriting and removing
- Renaming something, rewriting a note
- Deleting a branch or a card
- Replacing a board’s columns
Changes land while TabTree is open on one of your devices — or the next time you open it — and
⌘Z undoes them like anything you do.
The rest appears as a banner on the map: you tick what you want and apply it.
What it will never do
- Overwrite or delete one of your maps.
- Read anything outside your account and the team spaces you are a member of.
- Change a team map where your role is viewer.
- Put your key inside a map — it stays in your Claude settings, and you can revoke it from TabTree at any time.