# TabTree (npm · tabtree-mcp)

Turn conversations into mind maps and whiteboards — in your TabTree account, or local files.

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `tabtree-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/app-tabtree-tabtree/tabtree-mcp.md), [page](https://verifymcp.io/servers/app-tabtree-tabtree/tabtree-mcp)

## Channel facts

- Registry: `npm`
- Package: `tabtree-mcp`
- Version: `1.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (SEE LICENSE IN LICENSE.md) isn't a recognized OSI-approved license.
  - Actively maintained (last published 15 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 938 tokens (~156/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the TabTree MCP server?

TabTree runs locally as an npm package, launched with npx -y tabtree-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add app-tabtree-tabtree -- npx -y tabtree-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "app-tabtree-tabtree": {
      "command": "npx",
      "args": [
        "-y",
        "tabtree-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-tabtree-tabtree": {
      "command": "npx",
      "args": [
        "-y",
        "tabtree-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add app-tabtree-tabtree -- npx -y tabtree-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-tabtree-tabtree": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tabtree-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-tabtree-tabtree --command npx --arg -y --arg tabtree-mcp
```

### Hermes

```yaml
mcp_servers:
  app-tabtree-tabtree:
    command: "npx"
    args: ["-y", "tabtree-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "app-tabtree-tabtree": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tabtree-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-tabtree-tabtree -t stdio -c npx -a -y tabtree-mcp
```

### Other

```json
{
  "mcpServers": {
    "app-tabtree-tabtree": {
      "command": "npx",
      "args": [
        "-y",
        "tabtree-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 79, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 74, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-09-13 (score 73, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-09-11 (score 72, +12)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

## MCP tools (6)

### `list_maps` (~31 tokens)

Lists every mind map and board in the TabTree library (name, type, folder, size, last modified).

### `read_map` (~70 tokens)

Reads one TabTree map. A mind map comes back as a markdown outline; a board as a list of elements and connections. `file` is a file name (or a map name) returned by list_maps.

Input parameters:

- `file` (string, required): The .tabtree file name (or the map name)

### `search_maps` (~44 tokens)

Searches text across the whole TabTree library — map names, nodes, notes, shapes, sticky notes. Case-insensitive.

Input parameters:

- `query` (string, required): Text to search for

### `create_mindmap` (~301 tokens)

Creates a NEW TabTree mind map from a markdown outline (#/## headings, bullet lists indented by 2 spaces, [x]/[ ] checkboxes, [title](url) links, and " @a:<id>" / " @e:<emoji>" at the end of a line for an illustration). The first top-level line becomes the centre. Writes a .tabtree file into the backup folder; the user pulls it into the app from the 🛟 menu.

Input parameters:

- `folder` (string): Optional TabTree subfolder (e.g. "From Claude")
- `markdown` (string, required): Markdown outline (headings and/or bullet list). End any line with " @a:<id>" to give that node a built-in illustration, or " @e:<emoji>" for one large emoji — e.g. "Launch @a:rocket". Ids: person, te…
- `name` (string, required): Name of the map
- `style` (object): Optional look of the document. Omit it for the default.

### `create_board` (~284 tokens)

Creates a NEW TabTree board (whiteboard): shapes (rect, ellipse, diamond, text, sticky) and arrow connections that stay anchored to the shapes in the app. With no x/y coordinates, layout is automatic by level (the connections define the hierarchy, left to right). Good for a diagram, a flow, a brainstorm. In a flowchart use ellipse for start/end, rect for a step, and diamond for a decision — its text should read as a closed question with exactly two ways out.

FIT THE TEXT TO THE BOX. A box shows roughly (w−24)/7 characters per line and (h−10)/20 lines, and every blank line costs a full line. Write captions, not paragraphs: when filling a canvas template (Business Model Canvas, Lean Canvas, SWOT…), the shipped templates use 70–110 characters per block, and that is what looks composed. Longer text is shrunk to fit — nothing ever spills out — but past ~11px it stops being readable and the response will warn you.

Input parameters:

- `connections` (array): Arrows anchored between elements (by id)
- `elements` (array, required): Board elements
- `folder` (string): Optional TabTree subfolder
- `name` (string, required): Name of the board
- `style` (object): Optional look of the document. Omit it for the default.

### `propose_changes` (~208 tokens)

Proposes changes to an EXISTING mind map: add branches, rename a node, write a note, tick a task, remove a branch, illustrate a node — or, with op "persona", re-cast a WORK MAP canvas from a finished interview (the JSON block of the « ma cartographie du travail » skill). Nothing is applied — the proposal appears in TabTree as a banner on that map, the user reviews it change by change and picks what to keep (and can undo with Cmd+Z afterwards). Name each target node by its exact text, or by a path "Ancestor > Node" when the same wording appears twice. Read the map first so the wording matches.

Input parameters:

- `changes` (array, required): The proposed changes, applied in order
- `file` (string, required): The map to change — a file name (or map name) from list_maps
- `note` (string): One line telling the user what this proposal does and why. Shown above the changes.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/app-tabtree-tabtree/tabtree-mcp#diagnostics

## Score history

- 2026-09-25: 79
- 2026-09-24: 78
- 2026-09-23: 78
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 60
- 2026-09-09: 71
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 68
- 2026-09-02: 53

## Common questions

### What is the TabTree MCP server?

TabTree is an MCP server listed in the public MCP registry as app.tabtree/tabtree. Turn conversations into mind maps and whiteboards, in your TabTree account, or local files. This page covers its npm package (tabtree-mcp).

### Is the TabTree MCP server safe to use?

TabTree scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the TabTree MCP server expose?

TabTree exposes 6 tools: list_maps, read_map, search_maps, create_mindmap, create_board, propose_changes. Their descriptions and schemas cost roughly 938 tokens of context every time the server is loaded.

### Is the TabTree MCP server still maintained?

TabTree is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- npm package: https://www.npmjs.com/package/tabtree-mcp
- Socket report: https://socket.dev/npm/package/tabtree-mcp
- Repository: https://github.com/ai4xedu/tabtree-mcp
- Website: https://tabtree.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-tabtree-tabtree/tabtree-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-tabtree-tabtree/tabtree-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-tabtree-tabtree/tabtree-mcp