Live data from Hacker News

MCP is dead?

quandri.io

81–90 of 444 posts

Re: MCP is dead?

#81
I have been working full time in the MCP (& WebMCP) space for about a year now. Half consulting half spec work.

The article is semi right. Local MCPs that are made by enthusiasts wrapping an api they don’t own? Yes that is dead and should never have been a thing in the first place.

But MCP in its current direction and form is really an OAuth Protocol over http. And it has something other that other agent identity protocols don’t: client adoption

Re: MCP is dead?

#82
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.

Re: MCP is dead?

#83
post #40
post #24

Earlier quoted context omitted.

personally if i have the need to move a skill/script, etc. to another one of my machines, i'll make a git repo for them (if they aren't already on git)

This was one of the first ideas me and my team had for sharing skills and scripts. The problem is this is a very "why Dropbox and not FTP" answer. The second you utter the word git, you may have lost 90% of your audience - depending on their background, of course. MCPs are a lot more non-tech friendly

Really? 90% of your claude code using team gets lost over git? That seems like it's own problem.

Re: MCP is dead?

#84
I just don't see how she missed in her example that the post to linear graphql endpoint needs the model to load the graphql definitions, there's no way it's 65x the tokens. Whatever overage it actually is, it's well worth not having to muck around with graphql.

Re: MCP is dead?

#85
post #50

Earlier quoted context omitted.

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 ga…

It's that extra amazon box that wrap the actual box that wrap the thing you ordered. Except you're doing the wrapping.

Re: MCP is dead?

#86

Earlier quoted context omitted.

MCP seems like what you'd do when you want to encapsulate and share a skill+script in a standard way.

You can share a skill by copy pasting the text file to someone in slack. Its not that hard.

right, but if you have 300 employees using ai and you want to share a skill with all of them, and you want to be able to push an update to the skill, mcp provides you with a standard way to do that.

i dont understand why people are so invested in making this a winner-take-all battle. skills are ligthweight and ad-hoc, MCP is managed and centralized. there's a place for both of those things, even if your personal workflow only needs skills.

Re: MCP is dead?

#87
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.

It’s definitely an outlandish statement to make. There’s 200-400mn companies in the world on a conservative estimate. I assume the poster means something like “all listed companies”.

Re: MCP is dead?

#88

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]

Did you consider that maybe he has different information than you do, and thus he holds a different opinion?

I for one love MCP. It's way faster in my experience than skills / shell. And I like how (with Claude Code) I can setup the MCP in the web interface, use it in the chat and the CLI.

Plus the flow to add an MCP via the browser is achievable to any user.

And one thing I don't understand of skills is this. I have an MCP for my life organisation app that authorizes via OAuth. The flow is fully via the browser so I can use the app session and its stored somewhere in claude.ai. How does authentication work with skills?

Re: MCP is dead?

#90
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 number one value of MCP's is that it forced everyone align on an API protocol, but the protocol itself has room for improvement.
Post reply on HN