MCP

What I write about here ​

MCP, the Model Context Protocol, is how an agent reaches outside its own conversation. Files, databases, browsers, your terminal, a remote service. The protocol gives a model a way to call tools the people who built the model never had to think about.

That's the promise. The reality is more interesting.

Posts under this tag look at MCP from two angles. The practical side: which servers earn their keep, how to wire them in without giving an agent more authority than your most senior engineer. And the critical side: what happens when a protocol designed for convenience inherits all the trust assumptions of the user that runs it.

I am not anti-MCP. The protocol is useful and most of my workflow depends on it. I am sceptical of the way it is being adopted, which is roughly the same way every powerful tool gets adopted at first. Convenience first, audit later, surprise eventually.

Read these posts expecting opinions on specific servers and patterns. Some MCPs earn their stars. Some do not. The protocol itself is fine. What people build on top of it is the question.