MCP Servers 2025.9.1 リリース、Everythingサーバ更新 MCP Servers Releases 2025.9.1

The official Model Context Protocol (MCP) servers repository maintained by Anthropic, modelcontextprotocol/servers, has been tagged as release 2025.9.1. Rather than a headline feature drop, this appears to be a routine maintenance release bundling incremental improvements across the reference servers and their tooling.

The most concrete change highlighted is the addition of an elicitation testing tool to the Everything reference server. Elicitation is a relatively recent capability in the MCP specification that lets a server request additional structured input from the end user via the client, effectively standardizing form-like interactions at the protocol layer. Because the Everything server is designed as an exhaustive showcase of protocol features, having a dedicated tool to exercise elicitation makes it easier for client developers — building Claude Desktop integrations, IDE plug-ins or custom agents — to verify their handling of the flow against a known-good implementation.

Beyond that, the release likely consolidates the usual housekeeping: dependency bumps for the TypeScript and Python SDKs, README and example refinements, and assorted bug fixes. None of these individually are dramatic, but together they keep the reference implementations aligned with the evolving spec, which has been moving quickly since MCP debuted in late 2024.

It is worth situating this release in a broader trend. Over the past months Anthropic has been narrowing the scope of the official servers repository, archiving several first-party servers — including Filesystem, Git and others — and encouraging the community to maintain forks. What remains in-tree is converging on a minimal reference set: Everything, Fetch, Memory, Sequential Thinking and Time. That shift suggests the repository is being repositioned less as a catalog of useful integrations and more as a conformance and demonstration suite for the protocol itself, with the long tail of practical servers expected to live in third-party registries and community projects.

The surrounding ecosystem context is also relevant. MCP adoption has accelerated noticeably in 2025: Cursor, Zed, Windsurf and various JetBrains and VS Code extensions ship MCP client support, and OpenAI has embraced MCP within its Agents SDK, signaling that the protocol is on a path to becoming a cross-vendor standard for tool and context exchange between LLM applications and external systems. In that environment, the reliability and completeness of the reference servers carry outsized influence — a misbehaving Everything server can quietly mislead client implementers, while a well-instrumented one accelerates interoperability.

For most users, upgrading to 2025.9.1 should be straightforward and low-risk. Developers actively building MCP clients, however, may want to pull the new Everything build specifically to validate elicitation handling, and to confirm their tooling still works against the latest dependency versions. Teams running production MCP deployments based on the now-archived first-party servers should treat this release as another nudge to plan a migration toward community-maintained equivalents.