Migrate all three clients + core + test-servers from
@modelcontextprotocol/sdk@1.29 to SDK v2 (2.0.0-beta.4), keeping behavior
identical against legacy (2025-11-25) servers. Foundation for the SDK V2 +
New Spec stack.
Packages
- Split @modelcontextprotocol/sdk -> @modelcontextprotocol/client (Client,
transports, OAuth, error taxonomy, protocol types) + core (Zod schemas);
stdio -> client/stdio, Ajv -> client/validators/ajv. Test-servers ->
@modelcontextprotocol/server (+ server-legacy/sse). Deterministic import
rewrite (schemas -> core, everything else -> client); the codemod misroutes
client code to /server so it was not used for path routing.
- new Client(..., { versionNegotiation: { mode: 'legacy' } }) — nothing
2026-era goes on the wire.
Runtime (core/mcp/inspectorClient.ts)
- Error taxonomy: McpError -> ProtocolError, ErrorCode -> ProtocolErrorCode;
RequestTimeout -> SdkError/SdkErrorCode.
- Handlers take method strings; task methods (tasks/*, notifications/tasks/*)
use the 3-arg custom form (excluded from v2's spec-method set).
- Legacy tasks kept working (per project requirement): requestor tasks re-
implemented over raw client.request + explicit deprecated schemas;
experimental.tasks.callToolStream replaced by a local pollTaskToolCall
async generator (with _progressHandlers revival so task-execution progress
still reaches the caller). Receiver (server-initiated) tasks: the v2 Client
validates a sampling/elicit handler result and rejects the legacy { task }
response with -32602 — installReceiverTaskResponseBypass swaps the wrapped
entry in the private _requestHandlers map for the task-augmented branch so
{ task } reaches the wire (fixes server-initiated sampling-via-task).
- Pagination: list verbs use raw client.request({method}, List*ResultSchema)
for single-page behavior (v2's client.listX() auto-aggregate all pages).
Web / auth / apps
- Rename local JsonSchemaType -> InspectorFormSchema + add toFormSchema()
structural narrowing at the SDK-schema -> form boundary.
- ext-apps still peers on SDK v1: one compat boundary with documented casts
(remove when ext-apps#702 lands a v2 peer).
- OAuth provider saveClientInformation reconciled with v2's
OAuthClientInformationContext; InvalidClientMetadataError re-homed as a
local class (server-legacy/auth is not browser-safe).
- vitest.shared.mts dedupes @modelcontextprotocol/client+core to one copy so
vi.mock intercepts the SUT's import.
Accepted v2 behavior changes (per #1624 / spec §9.2): unknown-tool call
rejects with -32602; cancellation is stream-abort (no guaranteed
notifications/cancelled frame); output-schema strictness restored via the
Inspector's own Ajv check on the default path.
npm run ci green: validate (web 3087 / cli 212 / tui 274 / launcher 5),
coverage (>=90 per-file, all clients), smoke (launcher/cli/web), storybook
(410).
Closes #1624
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
65 lines
2.3 KiB
TypeScript
65 lines
2.3 KiB
TypeScript
/**
|
|
* Shared Vite config (build externals + optimizeDeps). Consumed by `vite.config.ts`
|
|
* and by `start-vite-dev-server.ts` so the in-process Vite starter can apply the
|
|
* same node-only exclusions without re-loading `vite.config.ts` (Node can't
|
|
* import .ts directly).
|
|
*
|
|
* Aliases and the vitest project setup live in `vite.config.ts` itself — only
|
|
* the parts needed by both the CLI runner and `vite dev` belong here.
|
|
*/
|
|
|
|
import { rmSync } from "node:fs";
|
|
import { join } from "node:path";
|
|
|
|
const NODE_ONLY_OPTIMIZE_DEPS_EXCLUDE = [
|
|
"@modelcontextprotocol/client/stdio",
|
|
// `atomically` is reached only through `core/storage/store-io.ts`,
|
|
// which is imported by `core/mcp/remote/node/server.ts` (the Hono
|
|
// app). The module never lands in the browser graph; excluding it
|
|
// keeps Vite's dev-time scanner from chasing it through the plugin's
|
|
// node-only import chain.
|
|
"atomically",
|
|
// `chokidar` is only loaded inside `core/mcp/remote/node/server.ts`
|
|
// when the lazy mcp.json watcher starts. It transitively imports
|
|
// `readdirp` and core node fs/os modules; excluding it keeps Vite's
|
|
// dep scanner from walking into them during dev startup.
|
|
"chokidar",
|
|
"cross-spawn",
|
|
"which",
|
|
// `@napi-rs/keyring` is loaded only inside
|
|
// `core/auth/node/secret-store.ts` from the Hono `/api/servers`
|
|
// handlers. It's a native-binding package (no browser code path) so
|
|
// excluding it keeps Vite's dep scanner from chasing into the
|
|
// platform-specific binaries during dev startup.
|
|
"@napi-rs/keyring",
|
|
] as const;
|
|
|
|
export function getViteBaseConfig() {
|
|
return {
|
|
optimizeDeps: {
|
|
exclude: [...NODE_ONLY_OPTIMIZE_DEPS_EXCLUDE],
|
|
},
|
|
};
|
|
}
|
|
|
|
/**
|
|
* Dev-server optimizeDeps: rebuild from scratch each launch — no stale
|
|
* pre-bundles carried across restarts (avoids 504 Outdated Optimize Dep).
|
|
* Do not use under Vitest.
|
|
*/
|
|
export function getViteDevOptimizeDeps() {
|
|
return {
|
|
exclude: [...NODE_ONLY_OPTIMIZE_DEPS_EXCLUDE],
|
|
force: true,
|
|
ignoreOutdatedRequests: true,
|
|
include: ["ajv", "@modelcontextprotocol/client/validators/ajv"],
|
|
};
|
|
}
|
|
|
|
/** Remove Vite's pre-bundle cache under clients/web before a dev launch. */
|
|
export function clearViteDepsCache(clientWebRoot: string): void {
|
|
rmSync(join(clientWebRoot, "node_modules", ".vite"), {
|
|
recursive: true,
|
|
force: true,
|
|
});
|
|
}
|