Skip to content

chore(deps): update dependency @modelcontextprotocol/inspector to v2 - #185

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/modelcontextprotocol-inspector-2.x
Open

chore(deps): update dependency @modelcontextprotocol/inspector to v2#185
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/modelcontextprotocol-inspector-2.x

Conversation

@renovate

@renovate renovate Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@modelcontextprotocol/inspector ^0.22.0^2.0.0 age confidence

Release Notes

modelcontextprotocol/inspector (@​modelcontextprotocol/inspector)

v2.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: modelcontextprotocol/inspector@2.0.0...2.1.0

v2.0.0

Compare Source

The v2 Inspector is now the default release.

npx @modelcontextprotocol/inspector          # web UI
npx @modelcontextprotocol/inspector --cli    # CLI
npx @modelcontextprotocol/inspector --tui    # TUI

What's new

v2 ships as a single package with three clients — a Vite + React + Mantine web UI, a scriptable CLI, and an Ink-based TUI — over a shared @inspector/core runtime, so all three behave identically.

Upgrading from v1

  • Node >= 22.19.0 is now required (was >= 22.7.5).
  • CLI flags changed substantially. In particular --config now means a read-only session file; --catalog is the writable server list. See MCP server configuration.
  • The v1 sub-packages (inspector-client, inspector-server, inspector-cli) are deprecated and not part of v2 — v2 publishes a single package.

v1

v1 is deprecated and receives security fixes only, published under the v1-latest tag:

npm i @modelcontextprotocol/inspector@v1-latest

v1.0.1: — v1 deprecated

Compare Source

v1 is deprecated. Use @​modelcontextprotocol/inspector@​latest (v2). v1 receives security fixes only.

v1.0.0

Compare Source

Versioning Note

Since this should be the last release of the classic MCP Inspector, it is finally being promoted to 1.0.0, primarily so that it can be referred to as the V1 implementation. It fixes outstanding security warnings and includes a couple of bug fixes.

Along with the release of the the upcoming 2026-07-28 MCP specification, we will be publishing an entirely new Inspector with a completely different codebase. The V2 web-based inspector client, the CLI, and a new TUI — all of which have a shared code architecture — will all ship as a single npm package. The V1 Inspector package will be officially deprecated at that time, and no further work will be done on that line.

What's Changed

New Contributors

Full Changelog: modelcontextprotocol/inspector@0.22.0...1.0.0


Configuration

📅 Schedule: (in timezone Europe/Rome)

  • Branch creation
    • Between 12:00 AM and 06:59 AM, only on Sunday and Saturday (* 0-6 * * 6,0)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/modelcontextprotocol-inspector-2.x branch 3 times, most recently from 84196b9 to e568c25 Compare August 14, 2026 19:13
@renovate
renovate Bot force-pushed the renovate/modelcontextprotocol-inspector-2.x branch from e568c25 to 399ed6a Compare August 19, 2026 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants