Repository navigation
v0.9.0 — MCP TypeScript SDK v2, Node 20
Changed
-
The server is built on MCP TypeScript SDK v2 (
@modelcontextprotocol/server2.2) instead of@modelcontextprotocol/sdk1.x (closes #75).- BREAKING — Node 20 or later is required; the SDK does not run on Node 18.
- The stdio server now speaks MCP 2026-07-28 as well as the 2025 revisions. A client that opens with
server/discoveris served on 2026-07-28; one that opens withinitializegets the revision it asks for, as before. Claude Code 2.1.287 was observed opening withserver/discover, so it now runs on the new revision instead of falling back. - Tool names, descriptions, order and input schemas are the same, with three differences on every tool, none of which changes what a tool accepts:
$schemaishttps://json-schema.org/draft/2020-12/schemainstead of draft-07;$schemais the second key of the schema instead of the first; and the tool member"execution":{"taskSupport":"forbidden"}is no longer sent (forbiddenis the default). - Input that fails a tool's schema is reported with different wording: one line, without the
MCP error -32602:prefix. - A call to a tool name the server does not have is answered with a JSON-RPC error (
-32602) instead of a tool result markedisError. - When stdin closes, the server stops at once: a request still in progress is not answered. Before, it was allowed to finish and its result was written. Clients that keep stdin open for the session, as MCP clients do, are unaffected. A one-shot pipe (
printf '…' | dataverse-mcp-server) gets no answer to a call that had not finished, and a write sent that way may still reach Dataverse. - On a 2026-07-28 session every result also carries
resultTypeand_metawith the server's name and version, andtools/listcarriesttlMsandcacheScope.
An error thrown inside a tool still reaches the client as the tool's error text with
isError: true.