MCP Declared Dead, Debate Immediately Follows

A thread titled 'MCP is dead?' is getting pushback and nuance in equal measure. The original concern centered on security vulnerabilities and practical overhead, but commenters are splitting into two camps: those who think small scripts and direct CLI tools beat MCP for personal/team use, and those who argue MCP becomes genuinely useful at the org level when you need to give non-technical users safe, unified access to internal APIs.

The pattern here is that MCP's value proposition is environment-dependent. For solo developers or small teams, the overhead of setting up and maintaining MCP servers doesn't justify the abstraction. But for enterprises, where access control and auditability matter and where the people using AI tools aren't engineers, MCP solves a real problem. BNP Paribas running Mistral on-prem for KYC, as noted in the Mistral AI Now Summit thread, is exactly the kind of use case where a structured tool-calling protocol makes sense.

The security concerns raised earlier (context poisoning) are apparently patched, which is defusing some of the opposition. The debate is settling into a 'right tool for the right context' conclusion rather than a clean verdict.