MCPnewsletter: MCP goes stateless
MCPnewsletter
Issue #005: MCP goes stateless
This edition starts with the biggest protocol news: the MCP 2026-07-28 release. The theme is simpler serving, stronger extension points, browser-facing MCP, and the beginning of more serious operations around MCP servers.
---
MCP 2026-07-28 lands with a stateless core
Links: MCP specification announcement · David Soria Parra announcement
The MCP 2026-07-28 specification is out, and it is one of the most important releases so far. The core change is that MCP is now stateless, with semantics for multi-round-trip requests. The release also adds header-based routing, cacheable list results, authorization hardening, a formal extensions framework, and updated Tier 1 SDKs.
David Soria Parra described it as one of MCP's biggest releases, built from 18 months of lessons. The important part for builders is practical: stateless MCP should be simpler to host, scale, route, and operate across infrastructure that already expects request-based services.
Extensions are the other major shift. MCP Apps, Tasks, Enterprise Managed Auth, and other domain-specific additions now have a clearer place to evolve without forcing every experiment into the protocol core.
If you run an MCP server today, this is the release to study before your next architecture change. Pay attention to stateless request handling, authorization changes, and SDK migration paths before assuming older server patterns are still the best default.
---
Claude starts bringing MCP 2026-07-28 into Claude products
Link: Claude blog
Anthropic published guidance on bringing the 2026-07-28 MCP spec to Claude. The post frames the new spec around a stateless core, standardized extensions, and hardened auth, with support rolling out across Claude products.
This matters because protocol releases only become real when major clients adopt them. Claude support gives MCP builders a clearer target for compatibility, especially if they are building tools that need to work across hosted, remote, and enterprise-controlled environments.
Builder takeaway: track both the spec and client rollout. A server can implement the new MCP version correctly and still need compatibility checks against actual Claude behavior, connector UX, approval flows, and auth expectations.
---
Cloudflare doubles down: Workers support for the new MCP and WebMCP preview
Links: Cloudflare MCP v2 blog · Cloudflare MCP v2 post · WebMCP blog · WebMCP post
Cloudflare published two notable MCP updates during Agents Week.
First, Cloudflare covered the next generation of MCP and why the rewritten stateless core fits Workers. Their post focuses on protocol upgrades, feature lifecycle, SDK migration, and early adopters already running the new model in production.
Second, Cloudflare launched a developer preview of WebMCP. The pitch: with one switch, any site can become usable by browser AI agents without new APIs or origin changes, while the human stays in control and creators keep their traffic.
Together, these are important because they attack two different bottlenecks. Stateless MCP makes server hosting more natural. WebMCP explores how normal websites can expose agent-usable interfaces without forcing every creator to build a custom API first.
Builder takeaway: the MCP surface is widening. Some teams will build explicit MCP servers. Others may make existing web properties more agent-readable. In both cases, control, consent, and observability matter more than the demo.
---
Cloudflare Kitesurf shows browser control through MCP
Link: Dina Kozlov post
Dina Kozlov shared Cloudflare's Kitesurf MCP server in action with a simple summary: give your agent a browser, but make it MCP.
Browser MCP remains one of the clearest categories for real utility. Agents become more useful when they can inspect pages, click through flows, verify UI states, and debug from the browser instead of only editing code and guessing.
Builder takeaway: browser tools need strong guardrails. Letting agents browse is useful. Letting them submit forms, purchase items, change settings, or scrape sensitive pages needs explicit boundaries and human approval.
---
PostHog releases MCP Analytics for server visibility
Link: PostHog announcement
PostHog says most MCP servers are black boxes: engineers often do not know how much they are used, what works, or what breaks. Their MCP Analytics release is aimed at making MCP server behavior visible.
This is a sign of MCP maturing. Once teams deploy MCP servers beyond experiments, they need the same operational basics they expect from APIs: usage metrics, error patterns, user journeys, tool-level performance, and visibility into which capabilities are actually valuable.
Builder takeaway: add observability before the server becomes important. Log tool calls, failures, latency, auth outcomes, and approval decisions. Avoid logging secrets or sensitive prompt content by default.
---
MCP Summit pushes MCP certification at AGNTCon and MCPCon China
Link: MCP Developers Summit post
MCP Developers Summit announced the Model Context Protocol Associate certification as an add-on for AGNTCon and MCPCon China in Shanghai on September 6 to 7.
Certification is not the same as real production experience, but it shows the ecosystem is getting more formal. As MCP moves into enterprise workflows, teams will need shared language around protocol basics, auth, server design, testing, client behavior, and safety patterns.
Builder takeaway: if your team is adopting MCP internally, document your own operating standard too. A certification may teach the protocol, but your org still needs rules for permissions, secrets, approvals, and production access.
---
Field notes from Reddit: what people actually use and what surprises them
Links: Most used MCP tool thread · Underrated free MCP server thread · Three things nobody tells you thread
The r/mcp discussions are useful because they show the gap between protocol announcements and daily builder behavior. People are asking which tools are actually used, which free servers are underrated, and what surprises new MCP users after setup.
Three free MCP servers worth trying if you are building your baseline stack:
- Context7 for current documentation context during coding workflows.
- Playwright MCP for browser automation and UI verification.
- GitHub MCP server for repository, issue, and pull request workflows.
The practical lesson from these threads is that utility clusters around boring workflows: docs lookup, browser testing, repo operations, file access, and search. The surprising parts are usually permissions, install friction, context overload, and figuring out which tool calls should require approval.
Builder takeaway: your first MCP stack should solve repeated work, not impress people with a long tool list. Start with three tools you can explain, secure, and observe.
---
Community demo: MCP plus creative and deployment tools
Link: Argona post
Argona shared a workflow combining Claude Code, a Higgsfield MCP, and a Netlify connector to generate and deploy a more polished website experience.
The signal is not only the specific tools. It is the pattern: agents chaining creative generation, code changes, and deployment infrastructure. That can be powerful, but it also crosses from content generation into production mutation.
Builder takeaway: creative MCP workflows still need deployment safety. Preview links, branch deploys, rollback paths, and approval gates are the difference between a fun demo and a usable workflow.
---
Builder checklist
- Read the MCP 2026-07-28 spec before starting a new server.
- Check whether your SDK has a v2 migration path.
- Treat stateless MCP as an opportunity to simplify hosting and scaling.
- Add analytics for tool calls, failures, latency, and approvals.
- Use browser MCP for verification, but gate consequential actions.
- Keep your first MCP stack small: docs, browser, repo, and one domain-specific tool.
- Watch WebMCP closely if your product is mainly a website rather than an API.
---
Reddit discussion starter
MCP 2026-07-28 makes the protocol stateless, adds extensions, and pushes the ecosystem closer to production infrastructure. At the same time, Cloudflare is previewing WebMCP, Claude is rolling out support, and PostHog is adding analytics for MCP servers.
The direction feels clear: MCP is becoming less about isolated tool demos and more about scalable, observable, governed agent interfaces.
What do you think matters most next: better auth, better observability, easier hosting, or more client support for MCP apps?
---
About MCPnewsletter
MCPnewsletter is a weekly briefing on Model Context Protocol tools, servers, apps, SDKs, registries, community projects, and practical implementation patterns.
Subscribe at: https://mcpnewsletter.com
Send MCP servers, news, feedback, or sponsorship inquiries: contact@mcpnewsletter.com