Mcp

Most solo builders now run an AI agent with real access: a file system, a couple of API keys, a database, maybe a deploy script. To make it useful, you connected it to things. A server from a README. A config you copied from a blog post. Something that “just worked” in about four minutes. That’s the part worth slowing down on. The thing you actually agreed to An MCP server is not a plugin. When you connect one, you hand the agent a set of tools, and you hand it the schema that describes those tools — their names, their parameters, and their descriptions. The model reads that description and decides when to call it. ...

Model Context Protocol won. It’s now “the boring infrastructure layer” — 78% of enterprise AI teams run MCP-backed agents in production, and it just got its biggest update ever, a fully stateless rewrite meant for “really big players” with tens of thousands of agents. So the question a solo builder faces is pointed: if the protocol is the standard, why would I ever write a raw API call myself? The instinct to just grab the API is right more often than the hype suggests. Here’s the rule. ...