MCP

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 enterprise already has many channels. Humans use some. Machines use some. And now AI is asking for its own. In the last post, I explained why APIs are not enough and how MCP creates a new AI channel. If you missed that, read it here first: From APIs to AI Channels: The Next Evolution This post is the next step. We zoom out and see where this MCP channel actually fits. ...

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. ...

MCP—or Model Context Protocol—is the latest open standard that’s supercharging AI agents by giving them a reliable, universal connection to tools, services, and data. Imagine AI as a savvy assistant… but one stuck in a room with no windows. Until now, every new tool—whether a database, file system, or API—needed a bespoke connection. MCP breaks those walls down. It gives AI the ability to speak a consistent “plug-and-play” language, no matter what it’s connecting to. ...