Rohan Chaubey

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

by

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. (BTW, I had hunted the Zapier MCP when it launched)

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:

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? :)

85 views

Add a comment

Replies

Best
Jan Heimes

@rohanrecommends we actually built an MCP server very early on... and later added a remote MCP server as well. MCP is genuinely transforming how we interact with data and LLMs, and it's exciting to see how broadly it's being adopted across both developer and non-developer communities.

Anthropic creating MCP was a huge unlock accelerating adoption is great to see.

For anyone curious, we’ve documented our own @Needle MCP server here and also host a remote MCP server: https://docs.needle.app/docs/guides/mcp/needle-mcp-server/

Rohan Chaubey

@jan_heimes I second you, Jan.

Needle is always ahead of the curve, rooting for you since early days :)