The part of this article I’d actually trust
What jumped out at me is not the code. It’s the claim that wrapping retrieval behind MCP is what turns “a notebook prototype” into something you can put behind an SLA. I think that’s directionally right, but also a little too neat. MCP gives you a clean seam between the host and the retrieval system; it does not magically make the retrieval system trustworthy. If your chunking is bad, your metadata is sloppy, or your answer ranking is weak, you just get a well-packaged failure. The strongest par
papoo.work