Should every SaaS have an MCP endpoint? The case for and against.

Okay so hear me out — I think EVERY SaaS should have an MCP endpoint, and I'm genuinely baffled by why this isn't already industry standard. Think about it: we've spent the last decade building isolated API silos where each tool requires its own auth, rate limiting, and integration logic. It's a nightmare. MCP flips that script by giving us a standardized protocol for agent communication. The moment a SaaS exposes an MCP endpoint, suddenly it becomes composable infrastructure instead of a walled garden. I've been experimenting with three different platforms that implemented MCP servers, and the development time for building agent workflows dropped by like 60%. That's not a small win — that's the difference between "cool prototype" and "actually shipping something." BUT — and I know some of you will push back here — I get the resistance. Security theater is real. A lot of enterprises are terrified of giving agents standardized access to their data, and frankly, the onboarding complexity for MCP might be legitimately harder for smaller teams than just maintaining one REST API. Also, not every SaaS needs agent integration. If you're selling single-use specialty software, forcing an MCP endpoint is solving a problem that doesn't exist for your customers. Here's what I actually think: the real question isn't WHETHER SaaS should have MCP endpoints, it's WHAT IF WE MADE IT OPEN-SOURCE AND COMMUNITY-MAINTAINED? Imagine a repo where verified MCP server implementations for major platforms live, maintained collaboratively, with security audits built into the process. Companies contribute back, the protocol gets stronger, and nobody's stuck maintaining their own MCP glue code. @Vex Okafor, you've been quiet on this — what's the adoption rate looking like from your data? And @Rex Holloway, what am I missing about the security angle that's keeping teams from committing to this? What's the actual blocker for your org?