Show HN: mcp-use v2 rebuilt from scratch for stateless 2026-07-28 MCP spec

Luigi and the mcp-use maintainers announced a Show HN for mcp-use v2, an open-source TypeScript framework for building MCP servers and MCP Apps. They rebuilt the project from scratch to match the 2026-07-28 Model Context Protocol specification revision, which makes MCP stateless. The framework lives at github.com/mcp-use/mcp-use, and the protocol change is documented on the Model Context Protocol blog post for 2026-07-28.

The technical driver is the move to a stateless MCP design. Earlier protocol assumptions no longer fit cleanly, so the team chose a full rewrite rather than patching an older server and app stack. mcp-use remains TypeScript-first and targets both MCP servers and MCP Apps under the new revision, so builders work against one framework surface aligned with the updated protocol instead of a stateful-era codebase.

For engineers and builders, that alignment reduces friction when adopting the July 2026 MCP revision. Teams already using or evaluating mcp-use get a path to servers and apps that match the current protocol model. Stateless MCP also changes how connection lifetime, session state, and multi-instance deployment are reasoned about, so a framework rewritten for that model is more useful than one that only partially tracks the spec.

In the open MCP tooling market, Show HN threads like this surface framework choices next to other agent and tool-server stacks. mcp-use competes on open-source TypeScript coverage for both servers and apps, not on a closed product alone. A from-scratch v2 aimed at the 2026-07-28 revision is a signal that protocol churn is real enough that maintainers are willing to discard the old architecture rather than paper over it.

Watch how quickly the v2 release lands for day-to-day server and app workflows, and how the rebuild claims around performance and ergonomics hold up once the truncated throughput details are published in full. Practical next steps: read the 2026-07-28 MCP blog post, compare your current MCP session assumptions to the stateless model, and try mcp-use v2 if you are building TypeScript MCP servers or MCP Apps against the new revision.