TabTree MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to TabTree account and local-file mind-map editing: Do local-file and account modes retain distinct storage and credential boundaries?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Turn agent conversations into mind maps/whiteboards stored in a TabTree account or a user-scoped local folder.

What we know

Local stdio MCP that creates/reads/writes TabTree mind maps and whiteboards either through TabTree account storage or a configured local backup directory.

Maintenance / activity evidence

tabtree-mcp 1.2.1 published 2026-09-09T23:16:54.063Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Mind-map/whiteboard read/write within configured local folder or account library. Writes: Create/update map/whiteboard files.
Local folder or TabTree account credential.
Sensitive access: Conversation-derived notes/diagrams, Potential project context

Bounded file writes are lower risk, but maps may contain sensitive session/project context.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do local-file and account modes retain distinct storage and credential boundaries?

The bounded review of the publisher's documented TabTree account and local-file mind-map editing and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Bounded file writes are lower risk, but maps may contain sensitive session/project context.
Mind-map/whiteboard read/write within configured local folder or account library.
Local folder or TabTree account credential.
Local mode stores files in the chosen folder; account mode stores maps in TabTree service.
Reviewed write actions: Create/update map/whiteboard files
Sensitive access: Conversation-derived notes/diagrams, Potential project context
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Local-folder mode can read/write only the configured folder, but account mode sends map data to TabTree service.
Source uses a custom source-available license rather than an OSI license.
Exact account retention details were not established.
Source-available custom license; do not label as conventional open source.

Original activity observations

tabtree-mcp 1.2.1 published 2026-09-09T23:16:54.063Z

Technical identity

npm/tabtree-mcp

Exact implementation source: https://www.npmjs.com/package/tabtree-mcp ↗
Reviewed resource type: MCP Server
Repository identity: ai4xedu/tabtree-mcp
Package identity: npm:tabtree-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
tabtree-mcp
Recorded package identity, distribution or download evidence.
GitHub repository ↗
ai4xedu/tabtree-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
Evidence source ↗
tabtree.app
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Claude Code only · Publisher instructions
claude mcp add tabtree --scope user -e TABTREE_DIR="/path/to/your/backup/folder" -- npx -y tabtree-mcp
Configure / authenticate
MCP100 setup guide
Either local TabTree backup directory or TABTREE_API_KEY for account. Claude Desktop .mcpb alternative; install script supports --dry-run and --check.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Environment settings: TABTREE_DIR (local-folder mode), TabTree account key/config for cloud mode
Check connection
Suggested check
node mcp/install.mjs --check (only from checked-out publisher source), or check MCP tool listing and read-only map inventory.
Remove / uninstall / revoke
MCP100 setup guide
Publisher says Claude Desktop connector is removed in the app; for Claude Code registered `tabtree`, remove its actual MCP entry with `claude mcp remove tabtree`. Do not delete backup folders.
Publisher install example registration name(s): tabtree. The supplied removal example applies only to an existing Claude Code registration named tabtree-mcp; it does not remove the differently named install example. Confirm the actual host entry before use.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide · Review before use
```
claude mcp remove tabtree-mcp
```

Official Documentation & Sources

What it does

Local stdio MCP that creates/reads/writes TabTree mind maps and whiteboards either through TabTree account storage or a configured local backup directory.

Capability: Files & Knowledge
Resource type: MCP Server
Best fit: Turn agent conversations into mind maps/whiteboards stored in a TabTree account or a user-scoped local folder.

Representative uses

Create mind maps from conversation
Update whiteboard/map files
Use local-folder storage without an account
Sync maps to TabTree account when configured

Limitations

Local-folder mode can read/write only the configured folder, but account mode sends map data to TabTree service.
Source uses a custom source-available license rather than an OSI license.
Exact account retention details were not established.
Source-available custom license; do not label as conventional open source.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Local folder or TabTree account credential.
Permissions: Mind-map/whiteboard read/write within configured local folder or account library.
Data handling: Local mode stores files in the chosen folder; account mode stores maps in TabTree service.
Cost: free_or_account_based
Risk and cautions: Bounded file writes are lower risk, but maps may contain sensitive session/project context.

Access scope and cautions

Write actions: Create/update map/whiteboard files
Sensitive access: Conversation-derived notes/diagrams Potential project context
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Create mind maps from conversation; Update whiteboard/map files; Use local-folder storage without an account; Sync maps to TabTree account when configured.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y tabtree-mcp. Recorded transport: stdio. Recorded environment-variable notes: TABTREE_DIR (local-folder mode); TabTree account key/config for cloud mode. No configuration values are supplied here. Prerequisites: Node/npm; MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local-folder mode can avoid account auth; cloud mode uses TabTree account/key.

Can it modify data or perform write operations?

Documented write actions include: Create/update map/whiteboard files. Recorded permission boundary: Mind-map/whiteboard read/write within configured local folder or account library.

What data-handling boundary should I consider?

Local mode stores files in the chosen folder; account mode stores maps in TabTree service. Recorded sensitive-access context: Conversation-derived notes/diagrams; Potential project context.

What limitations and risks should I check before use?

Bounded file writes are lower risk, but maps may contain sensitive session/project context. Local-folder mode can read/write only the configured folder, but account mode sends map data to TabTree service. Source uses a custom source-available license rather than an OSI license. Exact account retention details were not established. Source-available custom license; do not label as conventional open source. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.