0.17.3 not available in npx

[alexprengere]

Hi,
I am not sure this is the right place to post this, sorry about that.
I use npx to run the MCP inspector, but it looks like 0.17.3 (release 2 weeks ago), is not yet available there:

npx @modelcontextprotocol/inspector@latest

This will run 0.17.2 (if this helps, I am running macOS)

[olaservo]

Hi @alexprengere this is the right place. We had a build error pop up in the publish pipeline last time we tried to publish to npm. We fixed the error but it looks like we still need to create a new release to trigger the publish again. Will update here once that happens.

[olaservo]

@alexprengere I recreated the release, just waiting on approval from core team on this publish pipeline: https://github.com/modelcontextprotocol/inspector/actions/runs/19657715962 Once that finishes running it should be available in npm.

[alexprengere]

@olaservo thanks for looking into this. It looks like the build failed, it references 0.17.4 which does not exist (yet).

[ln-12]

I still get an error after the release of 0.17.4 unfortunately:

$ npx modelcontextprotocol/inspector
Need to install the following packages:
github:modelcontextprotocol/inspector
Ok to proceed? (y) y

npm error code ETARGET
npm error notarget No matching version found for @modelcontextprotocol/inspector-cli@^0.17.4.
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.

If I run the command with latest, it falls back to 0.17.2:

Need to install the following packages:
@modelcontextprotocol/inspector@0.17.2
Ok to proceed? (y) y

npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead
Starting MCP inspector...

[olaservo]

Update: we're now running into a new build issue which I believe is being caused by a mismatch between the package versions being referenced in the PR workflow build vs the CI workflow build.

[olaservo]

New release pipeline is here: https://github.com/modelcontextprotocol/inspector/actions/runs/19933471965

[alexprengere]

It looks like it failed again.

[olaservo]

Yes, now there's a npm token issue again. :( There's a conversation happening in the Discord to resolve that part (again, as a long term fix).

[olaservo]

Phew, confirming that the latest is now on npm: https://www.npmjs.com/package/@modelcontextprotocol/inspector

[alexprengere]

I saw that over the weekend, thanks! I also confirm that this release finally fixes #846