Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MCP is dead?

quandri.io

Post reply on HN
Print view View original

281–290 of 444 posts

Re: MCP is dead?

#281

Post by notgenerated »

0xbadcafebee wrote: post #29

Man I wish I could downvote stories. There needs to be some way to push back against dark patterns in writing, like clickbait. Clearly MCP is not dead, as the article itself says. But the article lies in order to play on human sentiment/heuristics and steal your attention. It's like shouting fire in order to get people to run over to see your business.

Most of the internet is clickbait for a long while now. No one would read a title like "MCP and CLI can both be usefull in certain scenarios. Ask your AI and he'll tell ya" :)

Re: MCP is dead?

#282

Post by joka88xj »

mrgaro wrote: post #226
tlogan wrote: post #112

Earlier quoted context omitted.

I would bet that MCP is going to die. The main reason is that it adds another layer (and human) that can, and probably will, get out of sync with the real-world implementation, whether that implementation is an API, web, or a CLI. AI should not be using a protocol or set of instructions that is different from what humans have access to (know and use). Sure, companies want to expose MCP servers because it is the cool…

MCP has a great advantage over agent using cli: MCP is much easier to secure so that it's hardwired that the agent can only call the pre-configured MCP server. We run our agents so that they don't have access to public internet, so they could not run any cli commands. It's all either built-in agent tools, or 3rd party mcp servers. The agents never have access to any credentials, which makes them much more safe to use…

[dead]

Re: MCP is dead?

#283

Post by PunchyHamster »

tlogan wrote: post #112
mxstbr wrote: post #22

I run the team at OpenAI that's responsible for the ChatGPT App Store, Codex plugins, and all things MCP. The thing that all these "MCP is dead" posts are missing is that whether or not MCP is used as a transport protocol is actually completely irrelevant. The reason MCP isn't dead is because practically ~every company on the planet is building an MCP server. I know this because we interact with all of them. Most of…

I would bet that MCP is going to die. The main reason is that it adds another layer (and human) that can, and probably will, get out of sync with the real-world implementation, whether that implementation is an API, web, or a CLI. AI should not be using a protocol or set of instructions that is different from what humans have access to (know and use). Sure, companies want to expose MCP servers because it is the cool…

> The main reason is that it adds another layer (and human) that can, and probably will, get out of sync with the real-world implementation, whether that implementation is an API, web, or a CLI.

The menial task of updating the interfaces when the code changes is something AI should be really good at, so it's essentially little to no actual programmer time waste

> So the current situation is basically that I used Claude to write an MCP server on top of our API. And then I need to occasionally tell it update it match the public doc.

> And my reaction is: really? It is not like our API docs are not public. Claude Code created our MCP server with zero instructions beyond what is publicly available. I just told it to read the docs from the net.

Updating MCP by AI is one time effort.

Having AI re-create what MCP would do for every piece of code that uses a service is massively wasted effort in comparison

It's not question of "model limitation" but of cost effectiveness.

Re: MCP is dead?

#284

Post by MatthewPhillips »

falcor84 wrote: post #243
MatthewPhillips wrote: post #239

Earlier quoted context omitted.

Please keep in mind that CLIs do not run on mobile and never will. This is the elephant in the room that nearly everypne seems to be ignoring. This "debate" is built around the assumption that AI is only for at-your-desk work. It's obviously not. Having the ability to mix/match the services you use for everything in your life, whether that's email or social networks or managing your book collection, is going to be a…

> CLIs do not run on mobile and never will Can you clarify why the never? What's the issue with giving a phone-based AI a sandboxed file system and bash shell?

How is the user installing the CLIs? Proprietary app store for each chat app?

Re: MCP is dead?

#285

Post by MatthewPhillips »

mhalle wrote: post #257
MatthewPhillips wrote: post #239

Earlier quoted context omitted.

Please keep in mind that CLIs do not run on mobile and never will. This is the elephant in the room that nearly everypne seems to be ignoring. This "debate" is built around the assumption that AI is only for at-your-desk work. It's obviously not. Having the ability to mix/match the services you use for everything in your life, whether that's email or social networks or managing your book collection, is going to be a…

CLIs do work on mobile when they are packaged in skills that run in an appropriate VM behind the LLM. Claude on the web does this. The only issue is controlling network access, which could be fixed by per-skill ACLs.

Walk me through how a user installs and then uses these CLIs from their mobile phone.

Re: MCP is dead?

#286

Post by delusional »

mxstbr wrote: post #22

I run the team at OpenAI that's responsible for the ChatGPT App Store, Codex plugins, and all things MCP. The thing that all these "MCP is dead" posts are missing is that whether or not MCP is used as a transport protocol is actually completely irrelevant. The reason MCP isn't dead is because practically ~every company on the planet is building an MCP server. I know this because we interact with all of them. Most of…

> Maybe we will turn every MCP server into a CLI under the hood. Maybe we'll use code mode. Maybe we'll implement tool search.

Its absolutely hilarious to me how tech people keep imagining that "this time it will be different".

This has been done 100 times before, it's COM, it's the remote Java object marketplace, it's the semantic web.

You are imaging a world where businesses are OK being marginalized into a nameless, faceless api provider with no control over their product. This will never happen. You might get a couple of years while they chase investment frenzy, but it will fragment. They will lock you out of their services. They will interact directly with their customers.

Re: MCP is dead?

#287

Post by delusional »

zimbatm wrote: post #279
mxstbr wrote: post #22

I run the team at OpenAI that's responsible for the ChatGPT App Store, Codex plugins, and all things MCP. The thing that all these "MCP is dead" posts are missing is that whether or not MCP is used as a transport protocol is actually completely irrelevant. The reason MCP isn't dead is because practically ~every company on the planet is building an MCP server. I know this because we interact with all of them. Most of…

Another aspect is access control. CLIs live in the same namespace as the agent, so any secrets the CLI needs access to, the agent can also exfiltrate. And access control is lightly gated by the agent's tool call policy. For an enterprise-level deployment, it becomes quickly desirable to have a centralized MCP backbone, on which each MCP is attached to. A place you can attach policies to, log activity, and reason abou…

To the extent this is true, and it isn't with setuid binaries, it's a limitation of operating system apis.

Re: MCP is dead?

#288

Post by tlogan »

hnlmorg wrote: post #182
tlogan wrote: post #112

Earlier quoted context omitted.

I would bet that MCP is going to die. The main reason is that it adds another layer (and human) that can, and probably will, get out of sync with the real-world implementation, whether that implementation is an API, web, or a CLI. AI should not be using a protocol or set of instructions that is different from what humans have access to (know and use). Sure, companies want to expose MCP servers because it is the cool…

That’s only true for the frontier. The moment you start looking at enterprise consumers of AI you’ll see slow monoliths that make decisions by committee and those committees often don’t even understand the tech they’re passing ruling on. And you’ll also often see CISO-offices that are managed by checklists and yet more committees. Asking for MCP access is generally easier than asking for an API for several reasons: 1…

Here is my vision: the future of AI is about truly understanding the real world. The world around us.

Not everything in the real world will expose an MCP server so AI can interact with it.

Eventually, AI will need to move beyond MCP and interact with the real world the same way humans do: by observing, interpreting, reasoning, and taking action in messy, imperfect environments.

MCP tries to organize our messy word to make interaction part with the world easier in the near term, and it will help accelerate very early progress. But ultimately, MCP is a temporary bridge. Not the final destination.

I give it max 3 to 6 years and it will just die.

Re: MCP is dead?

#289

Post by IFC_LLC »

I love those "A coring drill is dead?" article.

"We've done extensive renovations in our apartment and while the coring drill was essential to install electrical conduits it's pretty useless in making furniture installations".

In the world of AI development we are jumping from tech to tech every 20 minutes. I'm in shivers every time when I see "A new claude version was released, do you want to update now?"

The moment you kinda automate something with the AI, the process breaks and you have to build the new thing.

So don't blame a coring drill.

Re: MCP is dead?

#290

Post by rwoerz »

zwischenzug wrote: post #204
js4ever wrote: post #148

Earlier quoted context omitted.

Totally agree, MCP is the WAP equivalent of mobile internet access.

I'm old enough to get this reference! Spent years writing WAP... it was really great at the time.

Those were the days of the dotcom era when finding the next restaurant with your Nokia + WAP was THE killer use case.
Post reply on HN