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

211–220 of 444 posts

Re: MCP is dead?

#211

Post by 0x000xca0xfe »

geysersam wrote: post #196
0907 wrote: post #5

I'll kick myself for not remembering, but there was a fantastic article which suggested that MCP works at org level when unified, safe, access to internal utility APIs need to be given to non-technical staff who do use internal agent tools. Codify your workflow(s) via skills and share across instances, anything that needs context aware API access should be mcp...

But what is the advantage of MCP compared to having the agents access the API directly?

Agents are just a stream of text, they cannot access anything. Some kind of interpreter is needed that recognizes special patterns and runs real code.

Do you mean directly == raw shell access on your production server?

Re: MCP is dead?

#212

Post by ekianjo »

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…

You can build a MCP server in minutes these days to connect to a REST API. The friction is close to zero.

Re: MCP is dead?

#213

Post by rand593843 »

ford wrote: post #50
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…

Basically MCP is little more than a brand name for "APIs LLM's can use". This means more services are creating APIs, because xyz company who's never been super tech forward doesn't want their tools to be obsolete when everyone uses agents. Overall, I am in favor of this goal. I'm not sure this is the protocol I'd choose to accomplish it, but it's the one people hear about, and the one they're using.

Yes. But that's dangerous for end users. It enables lock in. All it does is context management, so skills are much better choice

Re: MCP is dead?

#214

Post by 2muchcoffeeman »

holoduke wrote: post #200
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…

Funny thing is that Claude knows the api of Atlassian better than the mcp they provide. Mcp is limited it doesn't have all api calls described.

Is this not just a tooling problem?

Re: MCP is dead?

#215

Post by rvz »

julianlam wrote: post #82
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. I know this because we interact with all of them. Wow if that's not an echo-chamber comment I don't know what is.

The comment just reads to me as:

"Person working on MCP tools says MCP is not dead."

Re: MCP is dead?

#216

Post by robot_jesus »

rvz wrote: post #215
julianlam wrote: post #82

Earlier quoted context omitted.

> 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. Wow if that's not an echo-chamber comment I don't know what is.

The comment just reads to me as: "Person working on MCP tools says MCP is not dead."

Or, "Person who sells tokens responds to article claiming MCP spends too many tokens says please keep buying tokens."

Re: MCP is dead?

#217

Post by ashm1104 »

Well, I am not sure why everything is declared dead nowadays, I am actually trying to find the thing that actually die when people claim "x" is dead. Everyone is riding the wave, and so am I tbh...but the dead thing...I mean.. invite me to the funeral then

Re: MCP is dead?

#219

Post by usrusr »

didibus wrote: post #181
usrusr wrote: post #174

Earlier quoted context omitted.

I think that what they mean is that instead of ten perfectly orthogonal "unix philosophy" tools (skills) for the agent to compose when solving a problem, each with an API surface (description text) the size of Texas, you'd want to can each composition in a shell script (or a bespoke rust binary, if you enjoy watching your bot perform some heavy lifting) that only solves one problem but solves it so focused that the a…

I still didn't follow, you mean to pipe things between tool calls? Like if you want to query something and then update another without the intermediate getting brought in context?

Instead of requiring each session to understand the n tools used to solve a particular problem, you bundle up the solution in a conventional script (that's what I meant by "can", as in canning) that the agent can use with very little documentation in the context. When the model is smart enough to figure out the composition of underlying tools during regular execution, it will also be able to do the canning up as a script and write the lightweight documentation that turns the script into a skill. Subsequent use will only require that lightweight documentation in context.

Re: MCP is dead?

#220

Post by j45 »

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 MCP doesn't have to be the entire or only solution, or judged as such, and another tool in the toolkit.
Post reply on HN