Robert TaFounder & CEO, Clarity · Building Hyper-Personalized Agents

What Nobody Tells You About Building With AI in 2026

12 Apr 2026 · 1 min

Watch on YouTube

1:09

In this monologue, the speaker reflects on the hyper‑fast pace of AI development, noting that best‑practice guidance that is current today will likely be outdated within weeks. While many teams are adopting MCP (a widely‑used AI integration platform), the speaker observes a lack of critical discussion about its drawbacks. He argues that instead of granting continuous MCP access, developers should give coding or automation agents a lightweight CLI tool to invoke. This approach reduces the attack surface and prevents the agent from polluting the broader system context, offering a more secure and maintainable way to build with AI.

Chapters

Anybody that's building right now with AI would probably identify strongly with the fact that, uh, things change so fast that everybody's head is spinning. And so what is true of best practices and common knowledge today is different than what it was a month ago and will likely be different in a month or two months' time. It's just that fast-paced. Recently, I've been Like, despite the fact that MCP has a lot of momentum in terms of adoption, I have not started to see critiques, which I actually think are valid and viable critiques, that rather than giving MCP access, what you need instead is something like a CLI tool that you can give to a coding agent. For example, or another agent so that it just runs the CLI tool rather than having MCP access all the time. Because that's less likely to have a large attack surface. And it's less likely to pollute your context.