Install the Taskhold CLI (optional)

Install the CLI

curl -fsSL https://taskhold.com/install.sh | sh

• Needs Node.js 18 or later, or Bun. No sudo: everything goes in ~/.taskhold.
• Downloads the latest build from taskhold.com and checks its sha256 against /dl/latest.json before installing anything.
• Links taskhold-mcp into ~/.local/bin when that folder is on your PATH. Otherwise it prints the PATH line to add, and the full path ~/.taskhold/bin/taskhold-mcp works everywhere.

Then save your API key (Settings, API keys):

taskhold-mcp login

Watch your agents from the terminal

taskhold-mcp watch

The live board in a terminal: tasks in progress with a bar split by step, what each agent says it is doing, blocked tasks with their question, and recent activity. It redraws as events arrive over the events stream and reconnects on its own. Ctrl-C quits.

Show the task in the Claude Code status line

taskhold-mcp statusline --install

This adds a statusLine entry to ~/.claude/settings.json and keeps a backup next to it. If you already have a status line, it leaves yours alone and tells you; add --force to replace it. New Claude Code sessions show the line:

▶ Deploy v2.4 to staging ███░░░░░░░ 33% 1/3 · Run migrations

To mix Taskhold into a status line you already like, use the status line recipe or the status line generator instead.

Use the stdio server

For MCP clients that only run local servers. npx downloads the latest build from taskhold.com each time the client starts the server:

{
  "mcpServers": {
    "taskhold": {
      "command": "npx",
      "args": [
        "-y",
        "https://taskhold.com/dl/taskhold-mcp-latest.tgz"
      ],
      "env": {
        "TASKHOLD_API_KEY": "atd_sk_..."
      }
    }
  }
}

If you installed the CLI, the installed copy is a faster stdio server: set command to its full path (for example /Users/you/.taskhold/bin/taskhold-mcp), no args. It reads the saved key.

Updates and version pins

• taskhold-mcp update installs the latest version. taskhold-mcp update 1.3.0 installs that version and pins it.
• The CLI checks for a new version at most once a day and prints one line when there is one. The line goes to stderr, so an MCP client never sees it. Turn it off with TASKHOLD_NO_UPDATE_CHECK=1; pinned installs don't check.
• npx configs that use taskhold-mcp-latest.tgz get each new version on the next start. To pin one, put the version in the file name: taskhold-mcp-1.3.0.tgz.
• To pin at install time: curl -fsSL https://taskhold.com/install.sh | sh -s -- --version 1.3.0

Current version and checksums

Check a download yourself:

curl -fsSL https://taskhold.com/dl/taskhold-mcp-1.3.1.mjs | shasum -a 256

Uninstall

taskhold-mcp uninstall

Removes ~/.taskhold, the ~/.local/bin link and the Claude Code status line if the installer set it. By hand: rm -rf ~/.taskhold. Stdio entries in an MCP client config are yours to delete. The remote server has nothing to uninstall; revoke its key in Settings.