Topic
6 articles on MCP, written from production systems rather than documentation.
Stdio is the default and it quietly decides your deployment model. The transport question is really a question about process lifetime and blast radius.
When an agent misuses a tool, the instinct is to rewrite the prompt. Usually it's the tool's own signature that made the mistake available in the first place.
MCP gets described as USB-C for AI tools. The useful question is narrower: which parts of tool integration stop being your problem, and which never were.
An MCP server turns an internal API into something a model calls on its own initiative. The threat model changes, and the existing auth boundary rarely fits.
Most teams only ever write servers. Building the client side is what shows you where the protocol stops and your own orchestration has to take over.
Every agent framework needs to call your internal APIs, not just the web. A custom MCP server exposes them safely once, instead of bespoke glue per agent.
Whether it needs designing from scratch or rescuing from its own success, tell me what you’re building and I’ll tell you how I’d architect it.
Open to remote and hybrid work worldwide