13
19 Comments

Is the future of SaaS inside AI assistants, not browsers?

I’ve been following the MCP ecosystem closely and honestly, it always felt like something only big SaaS could take advantage of.

Zapier, Notion, ReadMe… they all shipped MCPs early.

Everyone else? Mostly watching from the sidelines.

For the longest time, the assumption was: “MCP must be gated or exclusive that only major SaaS companies can build these.”

But after digging deeper, I realized something surprising:

The real bottleneck was never access.
It was clarity.

Before tools like the Ogment MCP Builder came along, developers had to:

  • Understand JSON-RPC
  • Write manifests without making a single mistake
  • Build & host their own MCP server
  • Set up OAuth + permissions
  • Manage rate limits + security
  • Deploy everything manually

This wasn’t “restricted.” It was just unbelievably confusing.

Big SaaS shipped first not because they had special permission… but because they had the engineering muscle to power through the complexity. Most indie devs and smaller teams simply couldn’t justify the time sink.

That’s what makes Ogment’s launch wild: https://www.producthunt.com/products/ogment-mcp-builder

Upload your API → get a production-ready MCP → customize → ship.
No-code. Ship your MCP in Minutes.

It instantly reframes something I’ve been thinking for months: Every SaaS should be accessible inside AI assistants.

Why are we still switching between 10 dashboards when ChatGPT can navigate for us?

MCP is quickly becoming the new interface layer for software... a conversational front-end where users just ask for what they need.

And now, thanks to tools like this, anyone can build an MCP, not just the giants.

Honestly, this should’ve existed from day one. But I’m glad it exists now, because the ecosystem is about to explode.

Are you planning to build a MCP for your product or it already exists? :)

on November 19, 2025
  1. 1

    This is true. Further of Saas lies in AI assistant.

    Looking for a Technical Co-Founder (B2B SaaS | Automation + AI)

    Building a B2B SaaS in the automation + AI workflow space.
    Problem validated through years of domain experience; strong recurring revenue potential.

    Looking for a technical co-founder (full-stack + automation experience preferred) to help build the MVP.
    Equity-first, long-term collaboration.

    If you're interested in discussing, reply here or DM me. I’ll share more once we connect privately.

  2. 1

    Love this framing that the real bottleneck wasn’t access, it was clarity. The checklist you lay out (JSON-RPC, manifests, OAuth, rate limits, hosting your own MCP server) is exactly the sort of “death by 12 half-understood steps” that kept a lot of smaller teams on the sidelines while the big SaaS players muscled through.

    What excites me about tools like Ogment is that they don’t just make MCP cheaper, they change the default mental model: instead of “build a dashboard,” it becomes “expose capabilities that an assistant can chain together.” I’m building a revenue automation product right now, and we’re already thinking of the browser UI as the optional skin — the real product is the set of actions assistants can orchestrate.

    Curious how you see this evolving: do you think most SaaS will treat MCP as a first-class interface, or will it stay a “nice to have” integration that only a subset of power users ever discover? - Russell

  3. 1

    Really interesting take — especially the part about AI interfaces slowly replacing the browser. From my own experience building tools for B2B founders, I’m starting to see the same trend: people don’t actually want “another dashboard”, they want actions that fit into their workflow.

    The MCP angle is super compelling. The idea of exposing capabilities instead of building full UI layers makes a lot of sense. I’m curious how far we are from real products adopting it at scale.

    A couple of questions I’ve been thinking about myself:

    • Do you see MCP replacing traditional integrations (Zapier / API calls), or more like a new layer that sits on top of them?
    • And what kind of UX do you imagine long-term?
      Will users “talk to products”, or will assistants silently coordinate tools behind the scenes?

    Would love to hear your view — this space is moving insanely fast.

  4. 1

    Interesting perspective! AI assistants could indeed redefine SaaS by providing more personalized, efficient, and context-aware interactions compared to traditional browsers. Instead of navigating multiple apps, users could accomplish tasks seamlessly through conversational interfaces. This shift could make software more intuitive, reduce friction, and accelerate productivity, potentially changing how we access and consume SaaS services entirely.

  5. 1

    I think the future of already existing SaaS is definitely AI and MCP. But if you're starting a traditional SaaS in this day an age, a lot of AI usecases made legacy SaaS obsolete

  6. 1

    This nails it — the shift isn’t about “AI replacing SaaS,” it’s about SaaS finally becoming usable through AI. MCP really does feel like the new interface layer, and tools like Ogment remove the exact barrier that kept smaller teams out. Wild to think how many products will skip the browser entirely once this becomes the norm.

  7. 1

    This shift toward AI-first interfaces is huge and you’re right, tools like Ogment are lowering the barrier in a way that finally lets smaller teams join the conversation. What’s interesting is how fast discussions like this are already gaining traction on Reddit

    I work with SaaS founders who want to position their products inside the right Reddit communities before the hype curve peaks. And topics like MCP, AI assistants, workflow automation, and “no-dashboard SaaS” are exploding right now if you show up in the right threads, you can attract early adopters long before a full launch

    If you want, I can share a few Reddit angles that consistently help founders spark interest, validate demand, and tap into the AI-builder audience without coming off promotional

    Just let me know happy to send them over

  8. 1

    What jumps out most in your story isn’t the bot, the tech, or even the viral loop. It’s that you built straight into the current, not against it. Most founders try to drag users to a new platform. You went to the exact place where traders already lived, already talked, and already trusted each other.
    That’s why NVSTly worked. You didn’t fight for attention, you amplified behavior that was already happening and removed the friction everyone quietly hated.
    A lot of people underestimate how powerful that move is. You didn’t create a new habit. You formalized an existing one. And those are the products that end up sticking around because they feel inevitable in hindsight.

  9. 1

    I have an MCP for my API product - Sociavault.
    What I discovered when learning the landscape of MCP is that it's just an api wrapper.
    Congratulations on Ogment’s launch.

  10. 1

    Absolutely plausible — AI assistants could become the new interface for SaaS, letting users interact with tools via natural language instead of juggling multiple browser tabs. It’s like moving from driving stick to fully autonomous navigation for workflows.

  11. 1

    With AI assistants becoming more integrated into our daily lives, it makes sense that the future of SaaS could shift from traditional browsers to more conversational, AI-driven environments. Instead of navigating multiple apps or tabs, users could access SaaS tools directly through AI assistants, making tasks more intuitive and efficient. The rise of voice and chat-based interactions could streamline workflows, especially for those who prefer hands-free or more personalized experiences. It'll be exciting to see how AI continues to evolve and redefine the SaaS landscape!

  12. 1

    Absolutely a compelling idea. AI assistants could become the new interface for SaaS, handling tasks, data queries, and workflows conversationally, reducing reliance on traditional browser dashboards. It’s a shift from “web-first” to “AI-first” experiences.

  13. 1

    AI assistants could reshape SaaS by making tools more conversational, context-aware, and integrated, potentially reducing the need for traditional browser-based interfaces.

  14. 1

    This nails it. The shift you described is exactly what’s happening — AI assistants are becoming the new interface layer, and MCP is the bridge that finally makes SaaS products usable directly through conversation instead of dashboards.
    Ogment lowering the barrier is huge, especially for indie makers who don’t have the engineering bandwidth to wrestle with manifests, JSON-RPC, and server setup. This feels like a genuine unlock for the ecosystem and a moment where smaller teams can finally stand beside the big players.

  15. 1

    Rohan Chaubey highlights a key shift in the SaaS ecosystem: AI assistants are becoming the new interface for software, with MCPs (multi-client platforms) at the core. Initially, MCPs seemed exclusive to big SaaS players due to their complexity, but tools like Ogment’s MCP Builder make it easy for anyone—big or small—to create and ship MCPs. This breakthrough makes SaaS accessible inside AI assistants, reducing the need to switch between multiple dashboards. As the barrier to entry lowers, Rohan sees a boom in indie devs building MCPs for their products, signaling a major shift in how we interact with software.

  16. 1

    This is a great breakdown. I had the same impression that MCP was mainly for big SaaS because they had the resources to deal with the complexity. Tools like Ogment really lower the barrier and make it practical for smaller teams to ship MCPs without getting buried in setup and infra. Excited to see what indie builders do now that the ecosystem is more accessible.

  17. 1

    My guess is simply that this Saas just don't have prioritize them yet.

    If you already have an API, having an MCP would be simple since it is just a translation.

Trending on Indie Hackers
I'm a lawyer who launched an AI contract tool on Product Hunt today — here's what building it as a non-technical founder actually felt like User Avatar 139 comments “This contract looked normal - but could cost millions” User Avatar 54 comments 👉 The most expensive contract mistakes don’t feel risky User Avatar 41 comments The indie maker's dilemma: 2 months in, 700 downloads, and I'm stuck User Avatar 35 comments I spent weeks building a food decision tool instead of something useful User Avatar 28 comments I just launched a browser API built for AI agents and LLMs User Avatar 23 comments