Cursor -- Treeship -- Treeship

Add Treeship to Cursor via MCP. Signed receipts for tool calls and wrap-friendly shell hooks.

Cursor uses the same @treeship/mcp bridge as other MCP hosts: every callTool can be attested into your Treeship session when the CLI and an active session are present. There is no Cursor-specific plugin with editor hooks today; pair MCP with treeship wrap or shell hooks for shell commands.

Quick setup

Install Treeship

curl -fsSL treeship.dev/install | sh
treeship init

Run treeship install if you want shell hooks to attest matching terminal commands automatically.

Enable the Treeship MCP server (recommended)

From your project directory:

treeship add cursor

This merges a treeship entry into ~/.cursor/mcp.json with TREESHIP_ACTOR=agent://cursor. Use treeship add (no argument) to configure every detected agent at once.

Restart Cursor so it reloads MCP configuration.

If treeship add skips Cursor, create ~/.cursor by opening Cursor once, then run treeship add cursor again.

Trust doc in the repo

The first successful treeship add in a project drops ./TREESHIP.md (if missing). Read it once: it lists exactly what the MCP bridge captures and what never leaves your machine without an explicit action.

(Optional) `.cursorrules` for `treeship wrap`

If you want the model nudged to wrap shell invocations, add a .cursorrules file. This is optional—TREESHIP.md is the source of truth for trust; rules are for ergonomics.

# Treeship — optional reminders

- Prefer: treeship wrap -- <command> for shell work when not covered by `treeship install` hooks
- When finishing a block of work: treeship session close (after sealing makes sense for your flow)

Session + verify

treeship session start
# work in Cursor (MCP tools + your workflow)
treeship log --tail 20
treeship session close
treeship package verify .treeship/sessions/<id>.treeship

Shell hooks from treeship install can attest many terminal commands even when the model does not type treeship wrap explicitly. MCP captures tool calls through @treeship/mcp; built-in editor actions that do not go through MCP or your shell are outside that path unless you add more instrumentation later.

Templates

Copy-paste MCP snippets and a longer walkthrough: integrations/cursor/ in the monorepo.

Cursor