chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to v2/main, this PR will be updated.

Releases

@modelcontextprotocol/server-everything@2.0.0

Major Changes

• #5118 5b400a6 Thanks @cliffhall! - Move to the TypeScript SDK v2 packages (@modelcontextprotocol/server, @modelcontextprotocol/node, and @modelcontextprotocol/server-legacy for the deprecated HTTP+SSE transport) from @modelcontextprotocol/sdk 1.x (#4856). The task tools simulate-research-query, trigger-sampling-request-async and trigger-elicitation-request-async are removed, and the server no longer advertises the tasks capability, because SDK v2 dropped the experimental tasks layer they were built on; they return on the tasks extension in #4852. Breaking for clients: the server now requires Node.js 20 or later; over stdio, a single incoming JSON-RPC message larger than 10 MiB now closes the connection (the SDK v2 default read-buffer cap; SDK 1.x buffered without a limit); an unknown tool name is rejected with JSON-RPC error -32602 instead of returning an isError result; error messages no longer carry the MCP error <code>: prefix, and input-validation messages name the field first (field: message); tool schemas in tools/list declare JSON Schema 2020-12 instead of draft-07; and tools no longer advertise execution.taskSupport. The optional state argument of args-prompt now carries its description.

@modelcontextprotocol/server-filesystem@2.0.0

Major Changes

• #5118 5b400a6 Thanks @cliffhall! - Move to the TypeScript SDK v2 packages (@modelcontextprotocol/server) from @modelcontextprotocol/sdk 1.x (#4856). Breaking for clients: the server now requires Node.js 20 or later; over stdio, a single incoming JSON-RPC message larger than 10 MiB now closes the connection (the SDK v2 default read-buffer cap; SDK 1.x buffered without a limit); an unknown tool name is rejected with JSON-RPC error -32602 instead of returning an isError result; error messages no longer carry the MCP error <code>: prefix, and input-validation messages name the field first (field: message); and tools no longer advertise execution.taskSupport.

@modelcontextprotocol/server-memory@2.0.0

Major Changes

• #5118 5b400a6 Thanks @cliffhall! - Move to the TypeScript SDK v2 packages (@modelcontextprotocol/server) from @modelcontextprotocol/sdk 1.x (#4856). Breaking for clients: the server now requires Node.js 20 or later; over stdio, a single incoming JSON-RPC message larger than 10 MiB now closes the connection (the SDK v2 default read-buffer cap; SDK 1.x buffered without a limit); an unknown tool name is rejected with JSON-RPC error -32602 instead of returning an isError result; error messages no longer carry the MCP error <code>: prefix, and input-validation messages name the field first (field: message); tool schemas in tools/list declare JSON Schema 2020-12 instead of draft-07; and tools no longer advertise execution.taskSupport.

@modelcontextprotocol/server-sequential-thinking@2.0.0

Major Changes

• #5118 5b400a6 Thanks @cliffhall! - Move to the TypeScript SDK v2 packages (@modelcontextprotocol/server) from @modelcontextprotocol/sdk 1.x (#4856). Breaking for clients: the server now requires Node.js 20 or later; over stdio, a single incoming JSON-RPC message larger than 10 MiB now closes the connection (the SDK v2 default read-buffer cap; SDK 1.x buffered without a limit); an unknown tool name is rejected with JSON-RPC error -32602 instead of returning an isError result; error messages no longer carry the MCP error <code>: prefix, and input-validation messages name the field first (field: message); tool schemas in tools/list declare JSON Schema 2020-12 instead of draft-07; and tools no longer advertise execution.taskSupport.