Playbooks · Coding tasks
MCP reference servers 2.3.0: what's new
Written November 6, 2026
Filesystem 2.2.0, memory 2.1.0, and fresh Python packages. What changed, what to pin, and what the drift report says to check first.
What shipped
The v2.3.0 release publishes new versions across the reference servers:
| Package | Version | Registry |
|---|---|---|
@modelcontextprotocol/server-everything | 2.2.1 | npm |
@modelcontextprotocol/server-filesystem | 2.2.0 | npm |
@modelcontextprotocol/server-memory | 2.1.0 | npm |
@modelcontextprotocol/server-sequential-thinking | 2.1.1 | npm |
mcp-server-fetch | 2026.11.4 | PyPI |
mcp-server-git | 2026.11.4 | PyPI |
mcp-server-time | 2026.11.4 | PyPI |
Filesystem 2.2.0: new tools, tighter boundaries
The filesystem server gains three new tools: append_file, copy_file, and an optional depth on directory_tree. It also gains two flags that narrow what the server can touch: --read-only, which serves only the read tools, and --confine-roots, which keeps client Roots inside the directories given on the command line. Files can now be exposed as resources through a file:// template, and the server logs the effective allowed directories and where they came from.
Several fixes change what the server reports. search_files now names the subdirectories it could not read, and says it matches names, not contents. A dangling symlink is reported as broken, not as a missing parent. edit_file shows the closest file lines when an edit has no match. And read_text_file returns no lines for head or tail of 0, instead of the old behaviour. The release also moves minimatch to ^11.0.4 for GHSA-g3hv-75wg-m249, and expands ~\ to the home directory on Windows.
Memory 2.1.0: lighter reads, clearer hints
The memory server adds lightweight read modes to the read tools and documents when to use search_nodes and open_nodes. It declares idempotentHint on create_entities, create_relations, and add_observations, and sets idempotentHint and destructiveHint on the filesystem server's read-only tools in the same release. An observation repeated inside one add_observations call is now stored once. The server also warns when the memory file sits inside node_modules and documents a durable MEMORY_FILE_PATH — a small fix for a file that should outlive a reinstall.
Python packages 2026.11.4: fetch, git, time
The three Python servers all move to CalVer 2026.11.4. Fetch gains an operator host allowlist (--allowed-hosts), a configurable HTTP request timeout, native Markdown through Accept content negotiation, and opens the simplified result with the page title. It also runs Readability.js under a bounded subprocess, off the event loop and stdout, and rejects an invalid prompt URL with -32602. Git gains a git_merge tool, a read-only git_remote tool that lists remotes, prompts that embed the repository's changes, and revision ranges such as main..feature in git_diff. Sequential-thinking 2.1.1 trims the tool description to fit 1024 characters and caps the thought history each connection keeps.
Before you upgrade: the runtime note and the pinning rule
The release carries a security note about the October Node.js runtime and CA certificate updates. The TypeScript servers rely on the Node.js runtime for certificate checks and ship no CA certificates of their own, so if you run a server from npm, run Node.js 24.22.1 or 26.12.1, or later, and check with node --version — the packages' engines field accepts any Node.js 24, so npm will not warn you about an older, unpatched runtime. For mcp-server-fetch, an environment created before October 23 keeps its older certifi; refresh it with uvx --refresh mcp-server-fetch or pip install -U certifi.
And the drift lesson from the last release still applies: pin the version, read the changelog on update, and test your tool calls after upgrading. The reference servers changed tool contracts 140 times without notice in the drift report's count, and this release adds new tools and changes what several existing ones return. A new release is not a fix for silent drift — it is another change to check. If you run the filesystem server, decide before upgrading whether --read-only or --confine-roots belongs in your setup, and re-check any client that depended on the old search_files wording or the old symlink error.
Limits
- No server was installed or run while writing this page. The versions and changes above come from the release notes; tool behaviour after upgrading still needs a test against your own client.
- This release does not fix the drift problem. It ships new package versions; it does not add version pinning, changelog checks, or contract tests — those stay your job.
- The release notes list every change per package, including fixes that only affect one platform. Only the changes that alter tools, flags, or reported behaviour are covered above.
Related playbooks
- Patch your MCP reference servers now
- MCPhantom: agents install dead MCP servers
- Two MCP servers patched holes this week
- Manage Airbyte pipelines through its MCP server
Sources
Back to: Coding playbooks hub · Also: 140 silent MCP contract changes, and how to pin them · A malicious MCP server probed cloud credentials · Catch bad agent behaviour chains with Quarry