70d5d70
@@ -223,8 +223,11 @@
npm test          # offline: unit tests plus regression tests against a local st
npm run test:e2e  # live, requires TYPESAFE_API_KEY
```
To run your local build instead of the npm release, register it directly and skip
the plugin, since the plugin always launches the published version:
Inside this repo the plugin's server fails to connect. `npx jev-mcp@<version>` sees a
local project already named `jev-mcp` at that version, skips the registry, and looks
for a bin that is never linked into the project's own `node_modules`. Every other
directory is fine. For work in this checkout, register the local build directly and
skip the plugin, since the plugin always launches the published version:
```bash
claude mcp add --scope user jev -- node /absolute/path/to/jev-mcp/dist/index.js
		@@ -223,8 +223,11 @@ npm test # offline: unit tests plus regression tests against a local st
223	223	npm run test:e2e # live, requires TYPESAFE_API_KEY
224	224	```
225	225
226		To run your local build instead of the npm release, register it directly and skip
227		the plugin, since the plugin always launches the published version:
	226	Inside this repo the plugin's server fails to connect. `npx jev-mcp@<version>` sees a
	227	local project already named `jev-mcp` at that version, skips the registry, and looks
	228	for a bin that is never linked into the project's own `node_modules`. Every other
	229	directory is fine. For work in this checkout, register the local build directly and
	230	skip the plugin, since the plugin always launches the published version:
228	231
229	232	```bash
230	233	claude mcp add --scope user jev -- node /absolute/path/to/jev-mcp/dist/index.js