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

271–280 of 444 posts

Re: MCP is dead?

#271

Post by wolttam »

zingar wrote: post #249
mrgaro wrote: post #226

Earlier quoted context omitted.

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…

Can you not just install/ restrict the available CLIs in the same way you do with MCPs? Or what else am I missing about why MCP is more secure than a CLI?

[dead]

Re: MCP is dead?

#272

Post by twoodfin »

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…

I think that’s exactly right: MCP provides a capability security model for agents.

Re: MCP is dead?

#273

Post by PaulHoule »

CharlieDigital wrote: post #236
nostrebored wrote: post #115

Earlier quoted context omitted.

this is bad. Anyone doing any cursory work with agents will realize how brittle > can be. Adding an extra layer of indirection isn’t helpful, it’s a gigantic hindrance that gives you a moving eval target. Being an MCP developer means you have a moving target of model optimization. It is a win for nobody. The tools we need to solve this problem exist and they are boring. Types, jsonschema, openapi, all of it is a bett…

That's because you're not thinking about how teams and enterprises work. You're thinking about how individuals work. An enterprise has 20 services that each have a secret key (Datadog, Snowflake, etc). I want my team to have access to those services via coding agents. How do I guard those keys from both developer and agent? Put it behind MCP; neither dev nor agent ever sees the key. If developer leaves, revoke one OA…

You’re not talking about how teams and enterprises work, you’re talking about how teams and enterprises don’t work.

Teams and enterprises had problems maintaining API keys long before there was MCP and they will have the same problems afterwards. The better teams and enterprises have had solutions for a long time.

Re: MCP is dead?

#274

Post by PaulHoule »

didibus wrote: post #133
varenc wrote: post #95

Earlier quoted context omitted.

The value is that many companies like building MCP servers much more than CLIs. For whatever reason. Here's some companies that offer MCP servers but don't seem to offer an equally featured CLI: - Asana - Square - Linear - Dropbox - Canva - Slack (sorta) - Figma (sorta) and many more that offer both, but support their MCP more. Should they all be offering CLI tools? IMHO, yes absolutely. But an MCP server gets much m…

A CLI needs to work on windows, mac, linux, android, iOS, etc. And it still needs some backend APIs to call. So creating one is a lot more work than just making an MCP.

That kind of code is easily portable in C or Rust or Go or Java or Python so long as it is a CLI and not GUI.

Re: MCP is dead?

#275

Post by qsxfthnkp2322 »

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…

Mcp is not dead says the guy who gets paid half a million to work on it.

News at 11.

Re: MCP is dead?

#276

Post by 0x696C6961 »

jimbokun wrote: post #33
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…

You failed to describe what value the MCP protocol provides. If all of these companies spent equivalent time writing a CLI for agents to consume as they spend on MCP servers, would they be any worse off in terms of agents being able to interact with their products?

I have a couple MCP servers connected to my Claude web & mobile clients. How would your clis work there?

Re: MCP is dead?

#277

Post by vonneumannstan »

MCP will die for the same reason RAG died and why prompt engineering is dying. The models get better at understanding what you want and where to find the right tool or context to solve the problem on their own.

Re: MCP is dead?

#279

Post by zimbatm »

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 about access control.

Re: MCP is dead?

#280

Post by croes »

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…

> The reason MCP isn't dead is because practically ~every company on the planet is building an MCP server.

Didn’t ~every company also jump on blockchain and NFTs?

Post reply on HN