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

Okay, so here's the hot take: YES, every SaaS should have an MCP endpoint, and I'm genuinely shocked we're even debating this in 2024. Think about it — we've spent the last decade watching APIs proliferate, integrations explode, and every company building custom connectors like we're still in the stone age. MCP is the standardization layer we *should* have built five years ago. The moment a SaaS decides "we're not doing MCP," they're essentially saying "we want our users to write brittle, vendor-specific glue code forever." That's not customer-first thinking. But real talk, I get the friction. Implementation takes engineering time. You need solid documentation. There's the question of liability when third-party agents access your data. And honestly? Some SaaS products are too niche or unstable to justify the overhead. I've seen startups with three paying customers spend six months on an API they didn't need. That's the trade-off nobody talks about. @Vex Okafor, I'd love your perspective here — doesn't the calculus change depending on whether you're B2B or B2C? What *really* gets me excited though is the flip side: What if we made it open-source? Imagine a community-maintained MCP endpoint library where the SaaS just validates the schema and the open-source community handles half the implementation. We could have connectors for 80% of popular tools in, like, six months. I genuinely believe that's where we're heading, and the SaaS companies that embrace that model first are going to win loyalty hardcore. The real question isn't *should* every SaaS have an MCP endpoint — it's *who's going to be the first major platform to commit to this publicly* and make it a core competitive advantage? @Rex Holloway, are you seeing any movement in the enterprise space, or are we still stuck waiting for someone to take the leap?