|
2 | 2 |
|
3 | 3 | ## 1.0.0 |
4 | 4 |
|
5 | | -The first semantic version, resuming semver after the date-stamped releases (last `2026.8.31`). It describes everything since `2026.8.31`, and is the last release of the legacy-era server. |
6 | | - |
7 | | -### Major Changes |
8 | | - |
9 | | -- [#5063](https://github.com/modelcontextprotocol/servers/pull/5063) [`b5af226`](https://github.com/modelcontextprotocol/servers/commit/b5af22668592700c02236d737f9836c42654edb6) [@cliffhall](https://github.com/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](https://github.com/modelcontextprotocol/servers/issues/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](https://github.com/modelcontextprotocol/servers/issues/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. |
| 5 | +The first semantic version, resuming semver after the date-stamped releases (last `2026.8.31`). It describes everything since `2026.8.31`, and is the last release of the legacy-era server, on the 1.x MCP SDK. |
10 | 6 |
|
11 | 7 | ### Patch Changes |
12 | 8 |
|
| 9 | +- [#5014](https://github.com/modelcontextprotocol/servers/pull/5014) [`8ea5e05`](https://github.com/modelcontextprotocol/servers/commit/8ea5e0541a448abc10f179dcb7807995336cde6e) [@cliffhall](https://github.com/cliffhall) - Fix the async task tools: `trigger-elicitation-request-async` now stops polling before the 10-minute TTL it requests for the client's task runs out, instead of polling past it and failing on a task the client has expired ([#4986](https://github.com/modelcontextprotocol/servers/issues/4986)); and `trigger-sampling-request-async` reports the status message of a client task that is already finished when it is created, instead of "No message" ([#4987](https://github.com/modelcontextprotocol/servers/issues/4987)). `trigger-elicitation-request-async` had the same flaw and gets the same fix. |
| 10 | + |
13 | 11 | - [#5005](https://github.com/modelcontextprotocol/servers/pull/5005) [`63dc92f`](https://github.com/modelcontextprotocol/servers/commit/63dc92f0e95992faf9d3e339cb8a51b1090d138b) [@cliffhall](https://github.com/cliffhall) - Label dynamic blob resources `application/octet-stream`, matching their resource template, instead of `text/plain`. This applies to `resources/read`, the `get-resource-reference` and `get-resource-links` tools, and the `resource-prompt` prompt; blob resource links are now described as "binary blob resource". |
14 | 12 |
|
15 | | -- [#5034](https://github.com/modelcontextprotocol/servers/pull/5034) [`6bed4c5`](https://github.com/modelcontextprotocol/servers/commit/6bed4c5f7c219e77fe90b9e4b14cdb9f3f7e9503) [@cliffhall](https://github.com/cliffhall) - Server instructions no longer tell every client to use tools that are registered only for clients declaring a capability; they list those tools and the capability each needs ([#4792](https://github.com/modelcontextprotocol/servers/issues/4792), ported from [#4835](https://github.com/modelcontextprotocol/servers/issues/4835)). `trigger-elicitation-request` is now registered only for clients that support form-mode elicitation, so a client that declared only URL-mode elicitation no longer sees a tool it cannot answer ([#4985](https://github.com/modelcontextprotocol/servers/issues/4985)). |
| 13 | +- [#5034](https://github.com/modelcontextprotocol/servers/pull/5034) [`6bed4c5`](https://github.com/modelcontextprotocol/servers/commit/6bed4c5f7c219e77fe90b9e4b14cdb9f3f7e9503) [@cliffhall](https://github.com/cliffhall) - Server instructions no longer tell every client to use tools that are registered only for clients declaring a capability; they list those tools and the capability each needs ([#4792](https://github.com/modelcontextprotocol/servers/issues/4792), ported from [#4835](https://github.com/modelcontextprotocol/servers/issues/4835)). `trigger-elicitation-request` and `trigger-elicitation-request-async` are now registered only for clients that support form-mode elicitation, so a client that declared only URL-mode elicitation no longer sees tools it cannot answer ([#4985](https://github.com/modelcontextprotocol/servers/issues/4985)). |
16 | 14 |
|
17 | 15 | - [#5053](https://github.com/modelcontextprotocol/servers/pull/5053) [`c63255a`](https://github.com/modelcontextprotocol/servers/commit/c63255ae9616b110d6089fa343fcfdf3f5def534) [@cliffhall](https://github.com/cliffhall) - Stop shipping the compiled test suite and Vitest config in the published package: the build now excludes `__tests__/`, `*.test.ts`, `*.spec.ts` and `vitest.config.ts`, as the other TypeScript servers' builds do. |
18 | 16 |
|
| 17 | +- [#5087](https://github.com/modelcontextprotocol/servers/pull/5087) [`09edf63`](https://github.com/modelcontextprotocol/servers/commit/09edf633b93cdaf094ba43622294d587afcd1023) [@cliffhall](https://github.com/cliffhall) - Require `@modelcontextprotocol/sdk` 1.31.0 or later (was `^1.30.0`), so an install can no longer resolve an SDK version affected by GHSA-6qxp-vccf-f47h. The advisory concerns the SDK's OAuth client, which this server does not use. |
| 18 | + |
19 | 19 | - [#5032](https://github.com/modelcontextprotocol/servers/pull/5032) [`d4fb2f4`](https://github.com/modelcontextprotocol/servers/commit/d4fb2f4f11efc084d97958dbecefa12c03020bd9) [@cliffhall](https://github.com/cliffhall) - Session resources are now tracked per server, so two sessions that create a session resource with the same name (for example via `gzip-file-as-resource`) no longer evict each other's resource ([#4808](https://github.com/modelcontextprotocol/servers/issues/4808)). |
20 | 20 |
|
21 | 21 | - [#5020](https://github.com/modelcontextprotocol/servers/pull/5020) [`f7af617`](https://github.com/modelcontextprotocol/servers/commit/f7af617ead2d4c7faf10338159a280d6387a1475) [@cliffhall](https://github.com/cliffhall) - The HTTP+SSE transport now answers requests for sessions it cannot serve instead of leaving them hanging or failing with a 500: `POST /message` for an unknown session returns `404` (and `400` with no `sessionId`), and `GET /sse?sessionId=…` returns `409` for a session that already has its stream and `404` for an unknown one. Each carries a JSON-RPC error body. |
|
0 commit comments