The Content Wrangler

The Content Wrangler

The Standard That Connects AI To Your Content Now Forgets On Purpose

A major revision to the Model Context Protocol changes how AI apps exchange context with content and tools they connect to, and what tech docs teams need to explain

Scott Abel's avatar
Scott Abel
Oct 22, 2026
∙ Paid

On July 28, 2026, the maintainers of the Model Context Protocol (MCP) released a new specification. MCP lets AI assistants and autonomous agents connect to external content and tools, such as your documentation portal or your support ticketing system. The maintainers describe it as MCP’s largest revision since its launch.

The main change is that the protocol no longer keeps track of ongoing exchanges between AI apps and the other systems it connects to. Each message now carries the info needed to handle it on its own. Engineers call this a stateless design.

The change affects how developers run MCP servers and how documentation teams explain those integrations. It also mirrors a decision anyone who writes reusable help topics makes every day: what to include so a piece of content works without relying on the content contained on the pages around it.

The Content Wrangler is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

User's avatar

Continue reading this post for free, courtesy of Scott Abel.

Or purchase a paid subscription.
© 2026 Scott Abel · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture