v0.3.0 — install as a Claude Code plugin
Two commands instead of three, and the one it removes is the one that fails without telling you why.
/plugin marketplace add priyanshuN/triago
/plugin install triago@triago
Registering triago-mcp by bare name resolves against the agent's PATH, not your shell's. It works when you test it in a terminal and fails with a bare ENOENT in an editor or desktop app launched from a dock, because those never source your shell profile — so a version manager's bin directory is simply not there. The error names nothing.
As a plugin none of that applies: Claude Code fetches the package and resolves the server path itself, so there is no global install, no symlink and no version manager anywhere in the chain.
The plugin is the npm package, not a second artifact to keep in step. The same tarball now carries .claude-plugin/plugin.json and .mcp.json, and the marketplace entry uses an npm source pointing back at it, so both channels publish from one release and share one version number.
That matters more than it sounds, because the failure is silent: Claude Code uses the plugin's version as its update cache key, so a stale manifest would make /plugin update report already at the latest version while installed users never receive the release. Nothing would error. So npm version rewrites the manifest into the release commit, and a test fails if the two ever disagree.
An npm source is also the only one that can work here — dist/ is gitignored, so a git-sourced plugin would resolve ${CLAUDE_PLUGIN_ROOT}/dist/mcp.js against a clone with no dist in it.
The manual claude mcp add route still works and is still documented, below the plugin one.
npm i -g @triago/cliNo schema, card-format or API change.