@modelcontextprotocol/inspector 2.5.0 → 2.7.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 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
@@ -75,8 +76,10 @@ Each client has its own README with client-specific detail:
75
76
  | [Publishing](./docs/publishing.md) | What ships in the tarball, the packaging invariants, and `pack:verify` |
76
77
  | [Docker](./docs/docker.md) | Running the container image — ports, volumes, and where secrets go |
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 |
79
+ | [Environment variables](./docs/environment-variables.md) | Every variable that changes runtime behavior — auth, ports, storage, the secret store, logging, proxies — plus the Node TLS variables for a self-signed server |
78
80
  | [MCP server configuration](./docs/mcp-server-configuration.md) | Which server(s) the Inspector connects to, and the config file format |
79
81
  | [Reviewing an MCP App](./docs/mcp-app-review.md) | The CLI-first → one-shot-web recipe for automated App-tool review |
82
+ | [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
83
  | [Launcher and config consolidation](./docs/launcher-config-consolidation-plan.md) | Why the launcher runs a client in-process rather than spawning it |
81
84
 
82
85
  ## Testing and the quality gate
@@ -86,7 +89,7 @@ Each client self-validates from its own folder; the root scripts chain them. The
86
89
  ```bash
87
90
  npm run validate # fast inner loop: format:check + lint + typecheck + build + unit tests
88
91
  npm run coverage # the per-file ≥90% gate (lines/statements/functions/branches)
89
- npm run local:gate # MANDATORY before pushing — a strict superset of GitHub CI
92
+ npm run local:gate # MANDATORY before pushing — every GitHub CI check, plus two local-only ones
90
93
  ```
91
94
 
92
95
  `npm run local:gate` chains every check below, plus the smokes and the Storybook tests. [Testing and the quality gate](./docs/quality-gate.md) owns the stage list and says what each one covers and why two are local-only; [`AGENTS.md`](./AGENTS.md) holds the testing rules themselves.