DoctorCheck that every installed tool works
toolshed doctor
checks every installed tool and says how to fix what it finds:
| Finding | Fix |
|---|---|
| the registry entry changed since it was installed | toolshed update <id> |
it’s registered with a toolshed binary that’s gone, e.g. after switching from go install to Homebrew | toolshed update <id> |
its command isn’t on PATH | install the command |
| a secret is missing from the keyring | toolshed install <id> |
| an npm or PyPI package isn’t pinned (a warning) | toolshed upgrade <id> |
| it doesn’t start, or doesn’t list its tools | toolshed tools <id> to see why |
It also lists servers registered through toolshed that are no longer in your
registry (toolshed import <name> brings them back), and how many other
servers Claude Code and Codex have that toolshed doesn’t manage (see
Import).
--no-start skips starting the servers, which is much faster with npm and
Python packages. It exits with 1 if anything is broken (warnings don’t
count), so it works in scripts, and --json prints the report.