AI Agent News/stories/mcp-reference-servers-reach-v2-0-0-with-modern-spec-support.md

MCP

MCP reference servers reach v2.0.0 with modern spec support

The Model Context Protocol reference servers reached version 2.0.0, with all of them refactored to support the modern era spec while still answering legacy-era clients. The release changes error handling for unknown tools and raises the Node requirement for the TypeScript servers, so existing integrations should be checked before upgrading.

Source: github.com/modelcontextprotocol/servers/releases/tag/v2.0.0

The maintainers released the reference servers as v2.0.0 on 19 October. Four TypeScript packages were published to npm at 2.0.0: server-everything, server-filesystem, server-memory and server-sequential-thinking. The Python servers, mcp-server-fetch, mcp-server-git and mcp-server-time, shipped as 2026.10.19 on PyPI.

The Python servers are now built on the MCP Python SDK's high-level MCPServer. An unknown tool now returns a JSON-RPC -32602 error instead of an isError result, and each server advertises prompts and resources capabilities. The time server's get_current_time and convert_time tools also declare an outputSchema and return structuredContent.

The TypeScript servers now require Node 24 as a minimum. The changelog lists a known issue in mcp-server-git where the string null passed as base_branch or as a filter arrives as no value, which affects only a branch literally named null. Suggested workarounds are refs/heads/null or the commit SHA.

Why it matters if you build agents

Clients that treated an unknown tool as a normal tool result now need to handle a protocol error, and the Python servers require mcp 2.3 or later. Teams running the TypeScript servers need Node 24 before upgrading. Anyone creating or filtering branches named null in mcp-server-git should apply the listed workarounds.

Get stories like this every weekday

One short email with the day's agent tooling news.

Subscribe