@modelcontextprotocol/inspector 2.5.0 → 2.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/clients/cli/build/index.js +1485 -78
- package/clients/tui/build/index.js +2539 -838
- package/clients/web/build/index.js +14 -3
- package/clients/web/dist/assets/index-30pI79Cf.js +1595 -0
- package/clients/web/dist/assets/{prism-light-_bvDBTQE.js → prism-light-9SaQe5zv.js} +1 -1
- package/clients/web/dist/index.html +1 -1
- package/package.json +3 -2
- package/clients/web/dist/assets/index-ZYqA4f7P.js +0 -1486
package/README.md
CHANGED
|
@@ -54,6 +54,7 @@ inspector/
|
|
|
54
54
|
├── core/ Shared code consumed via the `@inspector/core` alias (no package.json)
|
|
55
55
|
├── test-servers/ Composable MCP test servers + fixtures used by integration and smoke tests
|
|
56
56
|
├── scripts/ Root build/verify tooling (install cascade, smokes, the verify:* guards)
|
|
57
|
+
│ and repo automation run from CI (the dependency, Dependabot-alert and SDK sweeps)
|
|
57
58
|
├── docs/ Task-oriented guides — see below
|
|
58
59
|
├── specification/ Design/build specifications
|
|
59
60
|
├── .claude/skills/ Agent skills: the repo's procedures, invokable by name
|
|
@@ -77,6 +78,7 @@ Each client has its own README with client-specific detail:
|
|
|
77
78
|
| [Migrating from v1 to v2](./docs/v1-to-v2-migration.md) | CLI flag mapping, `--config` vs. `--catalog`, the Node engine bump, env-var renames |
|
|
78
79
|
| [MCP server configuration](./docs/mcp-server-configuration.md) | Which server(s) the Inspector connects to, and the config file format |
|
|
79
80
|
| [Reviewing an MCP App](./docs/mcp-app-review.md) | The CLI-first → one-shot-web recipe for automated App-tool review |
|
|
81
|
+
| [Smoke-testing an MCP server](./docs/cli-smoke-testing.md) | The connect → list → call → assert workflow for a shell or CI job: `--format json` + `jq`, the exit-code map, and keeping OAuth non-interactive |
|
|
80
82
|
| [Launcher and config consolidation](./docs/launcher-config-consolidation-plan.md) | Why the launcher runs a client in-process rather than spawning it |
|
|
81
83
|
|
|
82
84
|
## Testing and the quality gate
|