Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-09-02 · high
FastMCP's September 2 release makes ClientGroup reuse connections instead of raising errors when entered from a nested block.
Why now: FastMCP's fix and LangChain's abandoned workaround for it both trace to commits dated September 2.
FastMCP fixed a ClientGroup bug on September 2 that raised errors on nested connections that should have reused an existing one. Nesting a connected group inside another block is a pattern LangChain's own MCP integration relies on. The bug forced LangChain to write a workaround before FastMCP's fix arrived.
FastMCP now reference-counts its own context on ClientGroup, matching how Client already behaves, according to the v4.0.1 release notes.
LangChain's next alpha, 1.4.0a4, was cut hours after FastMCP's release. Its commit history shows LangChain adding a private class called _ReentrantClientGroup as a workaround. LangChain removed the shim once the real fix arrived upstream. The release notes don't mention any of it; only the git log does.
The alpha before it, 1.4.0a3, carries more weight. It adds a first-party langchain.mcp namespace built around a new MCPAdapter class. It also introduces client-side tool-call caching under SEP-2549, honoring a server's TTL hint. And it adds an elicitation="interrupt" mode that surfaces a server's mid-call questions as LangGraph interrupts, per LangChain's release notes.
Each link below shares sources, entities, or timing with this story.
The 1.4.0a2 alpha ships langchain.mcp, an MCPAdapter turning any MCP server into tools you hand straight to create_agent. Connection handling is FastMCP's rather than a reimplementation, so a URL, a local stdio script, an in-process FastMCP server, a multi-server config, or a...
v4.0.0b5, released August 28, introduces ClientGroup: one managed client per server, each negotiating independently, with collision-checked tool namespacing and call routing. That replaces fronting several servers with a proxy that forces one negotiated version across all of t...
The Model Context Protocol's 2026-07-28 revision is the biggest change since the protocol existed. The core is now stateless request/response instead of a bidirectional stateful session. Authorization aligns with OAuth 2.1 and OpenID Connect. MCP Apps and Tasks moved under a v...
The 2026-07-28 Model Context Protocol spec published today, and it removes two things every MCP server currently depends on: the initialize/initialized handshake and the Mcp-Session-Id header. Both are gone. Not deprecated. Gone from the core. (Model Context Protocol Blog) Wha...
Released August 31 after five betas, five weeks, 23 contributors and 80+ PRs, built on the MCP 2026-07-28 revision and the rewritten Python SDK v2 (GitHub). Modern requests are sessionless and self-contained, so protocol version is negotiated per connection and horizontal scal...
PrefectHQ/fastmcp shipped Prefab UI (beta), MultiAuth, PropelAuth support, and Google GenAI sampling. Over 1M daily downloads. If you're building MCP servers, this is the de facto framework.
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.