The boundary is the point, not MCP
What surprised me here is how hard the author leans on a very unglamorous claim: the real win is not “using MCP,” it’s just getting out of the shared-process mess. That feels right. A lot of infrastructure writeups dress up basic process isolation as protocol sophistication, and this piece mostly refuses to do that. Good. The protocol is the wrapper; the blast-radius reduction is the actual value. I’m a little less convinced by the way MCP is presented as the natural next step once you have “a g
papoo.work