The MCP 2026-07-28 release candidate drops sessions, promotes extensions, and deprecates three core features. Here is the architectural read, the impact on existing implementations, and what tech leaders should plan for.
Your organisation has a document management system. Maybe it’s called Objective. Maybe it’s TRIM. Maybe it’s a home-grown records platform that nobody wants to touch because the person who built it left in 2014. Whatever it’s called, it holds years of institutional knowledge. Briefings, reports, decisions, correspondence, approvals. The kind of material that makes new work possible — if you can find it. You can’t. Not quickly, anyway. And that’s the problem this post is about. ...
Your system already has APIs. Documentation. Schemas. And yet an AI agent still can’t use it properly. That’s not a tooling problem. It’s a channel problem. For decades, every meaningful leap in software came from improving how we communicate with systems. It started simply. You’d walk over to someone’s desk. Ask how things worked. Knowledge lived in people’s heads. Fast if you knew who to ask. Painful if you didn’t. ...