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

71–80 of 444 posts

Re: MCP is dead?

#71

Post by ProAm »

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…

No offense but you are paid to say these things. Your paycheck depends on it [1]

[1] “It is difficult to get a man to understand something, when his salary depends on his not understanding it.” ― Upton Sinclair, I, Candidate for Governor: And How I Got Licked

Re: MCP is dead?

#73

Post by sandeepkd »

adastra22 wrote: post #60
jimbokun wrote: post #33

Earlier quoted context omitted.

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?

[flagged]

At times I feel like these people are naive and may be do not have enough practical industry experience around software development, and then on second thought I realize that they are way smarter and counting on everyone else being naive here. This is a cycle of FOMO and a temporary phase.

Something like MCP is not a one time investment, the API's need to be maintained and updated regularly to be useful. Maintenance work is already a cost factor and no one gets promoted by maintaining anything.

Within organizations, smart carrier oriented folks are picking up this area of work for their personal growth and visibility which comes across as if every company is going for it.

Re: MCP is dead?

#74

Post by dnautics »

CharlieDigital wrote: post #70
dnautics wrote: post #66

Earlier quoted context omitted.

i mean you can surface an openapi schema too.

MCP is more than is more than tools. Tools is one of three major features: prompts[0] and resources[1] being the other two. Prompts are effectively "server delivered skills" which are are quite powerful because it solves a distribution and synchronization problem. It also allows server materialization and dynamic construction of skills. MCP also has a few other under utilized mechanisms: elicitation[2] on the client…

can these not be surfaced in an api and accessed using curl, with instructions in a SKILLS.md?

Re: MCP is dead?

#75

Post by iJohnDoe »

MCP is dead. AI bubble. Windows is dead. Linux is dead.

The only thing worse than the people saying it are the people that repeat it.

Re: MCP is dead?

#76

Post by bluegatty »

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.

"and the one they're using." no it's not.

Agents are just making REST calls and that's it.

The best thing a company can do to make their stuff 'agent ready' is to make sure the lllm.txt docs are clear-cut and ready for the AI with clear instructions for agentic use.

'MCP' is frankly a hurdle.

Now - it probably does make sense to add MCP, because it's not expensive at all, and some will like that use case, it maybe garners a bit more attention .

MCP is a 'weak externalization' - people are using it because others are using it, and it's a 'workable' but 'not strong' solution.

It could very well entrench itself however.

Re: MCP is dead?

#77

Post by satvikpendem »

adastra22 wrote: post #60
jimbokun wrote: post #33

Earlier quoted context omitted.

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?

[flagged]

Their comment does not sound like an LLM to me, it doesn't have most of the other tells.

Re: MCP is dead?

#78

Post by itsmek »

adastra22 wrote: post #60
jimbokun wrote: post #33

Earlier quoted context omitted.

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?

[flagged]

Also a dead giveaway: >That's what matters

Re: MCP is dead?

#80

Post by CharlieDigital »

dnautics wrote: post #74
CharlieDigital wrote: post #70

Earlier quoted context omitted.

MCP is more than is more than tools. Tools is one of three major features: prompts[0] and resources[1] being the other two. Prompts are effectively "server delivered skills" which are are quite powerful because it solves a distribution and synchronization problem. It also allows server materialization and dynamic construction of skills. MCP also has a few other under utilized mechanisms: elicitation[2] on the client…

can these not be surfaced in an api and accessed using curl, with instructions in a SKILLS.md?

Sure. It would be great if they were portable as well.

To make them interoperable so that the APIs have similar surface areas and can just be used without special skills, we could even come up with a standard API surface area and create a...protocol.

If you squint, the SKILL.md and the context that it takes up is literally the same thing as the MCP server and tool description. They are literally the same thing except one is server delivered and one is not.

MCP is "Let's use Google Sheets and have a server-managed experience". Everyone sees the same thing on the server in real time.

Skills is "Let me download the Excel and send it back to you". Why? How is this better? Every time I update the Excel, I have to add a `.2026.final.final2.xlsx` and everyone updates their copy...how is this the superior experience?

Post reply on HN