blockrun-upgrade

# Upgrading BlockRun MCP The server is run by `npx`, so "upgrading" means making npx fetch a newer version and the client restart into it. Which of those two is the problem depends on how it was installed. ## 1. Read how it was installed ```bash claude mcp get blockrun # registered command + args + env + scope npm view @blockrun/mcp version # what "latest" is on the registry right now ``` | Registered spec | What happens at each client start | |---|---| | `npx -y @blockrun/mcp@latest` | npx re-resolves `latest` against the registry and downloads if newer. **A client restart is the upgrade.** | | `npx -y @blockrun/mcp` (no tag) | npx reuses whatever is in `~/.npm/_npx` — the version from the day it was installed. Restarting changes nothing. | | `npx -y @blockrun/mcp@0.39.2` | Pinned on purpose. Only changes if you re-register. | The startup notice is the server telling you it is not on `latest`: ``` [BlockRun] Update available: v0.39.2 → v0.42.0 [BlockRun] Run: claude mcp add blockrun -s user -- npx -y @blockrun/mcp@latest ``` ## 2. Upgrade **Registered with `@latest`:** restart the client. Done. If the notice persists, the cache is stale or the registry was unreachable at start: ```bash rm -rf ~/.npm/_npx # safe — it is only a download cache ``` then restart again. **Registered without a tag, or pinned:** re-register with `@latest`. `claude mcp add` refuses a name that already exists, so remove first — at the scope `claude mcp get` reported — an...