2.0.0
modelcontextprotocol/inspector2.0.0Jul 28, 2026by cliffhall
AI Summary
The major v2 release consolidates the inspector into a single package with three distinct clients.
Key Highlights
- Single package architecture containing Web UI (Vite + React + Mantine), CLI, and TUI (Ink).
- Unified behavior across all three clients via shared `@inspector/core` runtime.
- Deprecation of the v1 classic inspector packages.
Breaking Changes
- Node.js version requirement increased to >= 22.19.0.
- CLI flags changed substantially (e.g., `--config` meaning changed).
- v1 packages are deprecated.
New Features
- Single package architecture
- Web UI
- CLI
- TUI
Full Release Notes
The v2 Inspector is now the default release. ```bash 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](https://github.com/modelcontextprotocol/inspector/blob/main/docs/mcp-server-configuration.md). - 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: ```bash npm i @modelcontextprotocol/inspector@v1-latest ```