The Model Context Protocol (MCP) reference servers reached version 2.0.0 on October 19, 2026, when the modelcontextprotocol/servers repository on GitHub published release v2.0.0 at 06:46 UTC (12:16 IST). According to the v2.0.0 release notes, "This release refactors all the servers to support the modern era spec, while still answering legacy era clients as expected." GitHub user cliffhall published the release, eight days after v1.0.0 went out on October 11, 2026.

#What changed?

Release v2.0.0 moves the four TypeScript servers to 2.0.0 and the three Python servers to 2026.10.19. The release notes list all seven packages as published:

Package

Version

Registry

@modelcontextprotocol/server-everything

2.0.0

npm

@modelcontextprotocol/server-filesystem

2.0.0

npm

@modelcontextprotocol/server-memory

2.0.0

npm

@modelcontextprotocol/server-sequential-thinking

2.0.0

npm

mcp-server-fetch

2026.10.19

PyPI

mcp-server-git

2026.10.19

PyPI

mcp-server-time

2026.10.19

PyPI

The npm registry lists 2.0.0 as the latest version of all four TypeScript servers, published between 06:49 and 06:51 UTC. PyPI lists 2026.10.19 as the latest version of fetch, git and time, uploaded at about 06:48 UTC.

#Spec versions

The release notes tie "modern era" to specific spec dates. The TypeScript change is titled "feat: modern-era TypeScript servers (2026-07-28 + 2025) and the new features in everything" (#5131). The Python change is titled "feat(fetch,git,time): serve the 2026-07-28 era beside 2025-11-25" (#5126). The release notes do not define the eras further.

#TypeScript servers

The TypeScript servers moved to the TypeScript SDK v2, per the change "chore: migrate the TypeScript servers to TS SDK v2 (codemod)" (#5063). A separate change, "fix: raise the TypeScript servers' Node floor to 24" (#5169), sets a new minimum. npm lists the engine requirement for all four 2.0.0 packages as Node ">=24". The project's CI validates the servers "on Node 22, 24 and 26 in parallel" (#5147), but the published packages declare Node 24 as the floor.

The filesystem server gets three fixes for roots handling:

  • "fix(filesystem): revoke access when a roots update leaves no valid root" (#5095)
  • "fix(filesystem): hold tool calls while any roots refresh is pending" (#5102)
  • "fix(filesystem): apply only the newest roots refresh's answer" (#5098)

#Python servers

The release notes say the Python servers "are now built on the MCP Python SDK's high-level MCPServer" and that they need "Requires mcp>=2.3,<3". PyPI lists the same mcp<3,>=2.3 dependency for all three. The release notes list these changes that clients can see:

  • "Unknown tool: a JSON-RPC -32602 error (Unknown tool: <name>) in both protocol eras, as the spec requires. It used to be an isError result."
  • "Capabilities: each server now advertises prompts and resources capabilities (with listChanged: false)."
  • "time: get_current_time and convert_time declare an outputSchema and return structuredContent. The text content is unchanged."

Other fixes include "fix(git): prefix git_show diff headers with a/ and b/" (#5145) and "time: accept only exact IANA timezone keys on every platform" (#5077).

#Who is affected and what should they do?

Anyone running the reference servers can update now, since the npm and PyPI packages are live. The changes that most often need action are the runtime and dependency floors. Teams running the TypeScript servers on Node 22 should note that the 2.0.0 packages declare Node 24 or later. Python deployments need an mcp package of at least 2.3 and below 3.

Client developers who check for an isError result when calling an unknown tool on the Python servers should handle a JSON-RPC -32602 error instead. For more on how MCP servers fit into agent tooling, see what OpenAI Dots mean for developers. For the network side of running local MCP servers next to coding agents, see our tutorial on controlling what AI coding agents can reach on a Mac.

#Is there a known issue?

The release notes list one known issue, #5176, in mcp-server-git: "the string "null" passed as base_branch to git_create_branch, or as contains / not_contains to git_branch, arrives as no value. This affects only a branch literally named null." For the filters, the release notes say to "pass refs/heads/null or the commit SHA".

#What is still unclear?

The release notes do not say what the modern and legacy eras mean beyond the spec dates quoted above, and no spec page has been reviewed for this article. The project has not stated how long the v1.0.0 servers will be supported. The full list of changes is in the v1.0.0 to v2.0.0 comparison on GitHub. More protocol coverage is in the Agent Platforms & Protocols hub.