I Was Exploring MCPs — And It Changed How I Think About the Internet

I was exploring what MCPs are and how to implement them into a project I’m trying to build.

What I found about it — and its use cases — is massive.


Here are my thoughts.

🌍 My Prediction

In a few years, no serious business will build apps anymore.


They’ll build MCPs.

Here’s what I think is coming:

• AI-first interaction becomes the norm
  


• App Stores decline in importance
  


• UX shifts from visual to conversational
  


• New businesses launch without ever building a frontend
  


• Brands compete on clarity, service, and logic — not looks

The internet becomes ambient. The AI becomes your universal agent. And the MCP? That’s the gateway every service plugs into.

🚀 First, What Even Is an MCP?

MCP stands for Machine-Callable Protocol.

It’s not a new app, library, or framework.


It’s a shift in how we think about services on the internet.

At its core, MCP is a way for businesses to expose their services in a standardized, machine-readable format that any AI can understand and interact with — without needing a frontend or an app.

That sentence alone changed how I was thinking about building my own product.

🤯 No More Apps?

Exactly. I had to sit with that for a moment too.

At least not the one's that have repeatable steps like bookings, e-e-commerce, utility apps, CRMs, etc

If a business builds an MCP server, it doesn’t need to build an app anymore.


No UI. No onboarding flows. No downloads. Just pure logic.

Instead of users opening your app, they’ll just talk to their AI — and the AI will talk to your MCP server.

And that’s the big unlock.

💡 How It Works (At a High Level)

Let me simplify this with a quick comparison:

It’s almost like we’re shifting from websites and apps to “logic endpoints” that are universally accessible. The AI becomes the new browser — or more accurately, the new OS.

💪 Why This Is So Powerful

This isn't just about convenience — it’s about a complete rethinking of digital interaction.

I realized a few things quickly:

• MCPs make every service ambient and available
  
  
  I don’t open my bank app — I just ask my AI to send money.
  
  
  I don’t browse five websites — I just tell my AI what I want, and it figures it out.




• Businesses will compete on logic, not UI
  
  
  Imagine if 5 insurance providers exposed MCPs. The AI picks the one with the best coverage, price, and terms — not the prettiest app.




• You can build once, access everywhere
  
  
  No more Android vs iOS. No more screen sizes or layouts. If your MCP is solid, you’re instantly compatible with any AI — phone, car, home assistant, wearable.

🔧 What It Means for Me as a Builder

I was originally thinking: "What kind of mobile UI should I design for my product?"

Now I’m asking:


"What does the MCP schema for my service look like?"


"How do I make it so an AI can understand, query, and execute it easily?"

The layers look something like this:

It’s weirdly freeing. I don’t need to obsess over microinteractions or layout grids.


I need to design for clarity, logic, and trust — because it’s the AI, not the human, that will talk to my product.

🛒 Real Use Cases That Got Me Excited

Here’s where it clicked for me — imagine these happening without any apps:

Every one of these can be fulfilled without opening an app — just by your AI calling an MCP.

That’s not future tech. That’s now — if we build it.

🧭 Where It Doesn’t Work Well (Yet)

MCPs excel in intent-based tasks, not exploratory or creative workflows (at least for now).

👋 Wrapping Up

So yeah — I started off just curious about MCPs for a side project.


Now, I’m completely rethinking how I build.