blockrun-setup

# Installing BlockRun MCP One command per client, then one tool call to see the wallet. Do it in this order; the PATH step is the one people skip and then spend an hour on. ## 1. Check Node first ```bash node -v # must print v20.19 or newer which npx ``` If `node` is from **nvm, Homebrew, fnm, volta or asdf**, assume the client's launcher will NOT find it. GUI-launched apps and Claude Code's MCP spawner do not source your shell profile. The fix is to pass your shell's PATH through at install time — not to pin `nvm alias default`, not to edit `.zshrc`, not to symlink node into `/usr/local/bin`. ## 2. Install — pick the client **Claude Code** (recommended; `-s user` = every project): ```bash claude mcp add blockrun -s user -e PATH="$PATH" -- npx -y @blockrun/mcp@latest ``` The `--` matters: it stops `-y` being parsed by `claude mcp add`. The `-e PATH="$PATH"` is the nvm/Homebrew fix from step 1; it is harmless on a system Node, so always include it. **Codex CLI** (`--env` is Codex's equivalent of `-e`; config lands in `~/.codex/config.toml`): ```bash codex mcp add blockrun --env PATH="$PATH" -- npx -y @blockrun/mcp@latest ``` **Claude Desktop / Cursor / Windsurf** — JSON, in the client's MCP config file: ```json { "mcpServers": { "blockrun": { "command": "npx", "args": ["-y", "@blockrun/mcp@latest"] } } } ``` | Client | File | |---|---| | Claude Desktop | `claude_desktop_config.json` (Settings → Developer → Edit Config) | | Cursor | `~/.cursor/mcp.json` · Wind...