stacktree-install

stacktree-install

One-shot installer for stacktr.ee. Wires the MCP server (and the Claude /stacktree skill) into the agents you actually use.

npx stacktree-install

What it does

The CLI walks you through four prompts and then writes the relevant config files.

• Sign in. Pick one:
  • Open browser to sign in (default) — we open app.stacktr.ee/connect/cli with a one-time code, you sign in (Google / GitHub / email — sign-up is the same flow), confirm the code matches your terminal, and click Authorize. We mint a fresh API key bound to your account and the installer picks it up automatically. No copy-paste.
  • Paste an API key I already have — for anyone who already minted a key in the dashboard.
• Token storage. Inline in the MCP config (easiest), or via the STACKTREE_API_KEY environment variable.
• Install location. Current project (writes alongside your repo) or globally (writes to your home directory).
• Agents. Any subset of: Claude Code, Cursor, Codex, OpenCode, Amp.

For Claude, the installer also drops in the stacktree-publish skill so the agent knows when and how to ship HTML artifacts.

Skipping the prompts

Pass an existing key as a positional argument to skip the sign-in step entirely:

npx stacktree-install stk_live_xxxxxxxxxxxx

You'll still be asked the token-storage, location, and agents questions.

Where things land

Agent	Config file
Claude Code	.mcp.json or ~/.claude.json, plus the skill at .claude/skills/stacktree-publish/
Cursor	.cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
Codex	~/.codex/config.toml (global only)
OpenCode	opencode.json or ~/.config/opencode/opencode.json
Amp	~/.config/amp/settings.json

Existing servers and unrelated keys in those files are preserved — the installer merges its entry in.

Privacy & revocation

Browser-flow keys are minted on the server, labelled stacktree-install, and listed alongside any other keys at https://app.stacktr.ee/api-keys. Revoke any time from there.

Env vars

• STACKTREE_API_URL — override the API base (defaults to https://api.stacktr.ee). Mostly useful for local dev.
• STACKTREE_API_KEY — read at install time if you picked "env" token storage; thereafter the agent reads it from its own environment.