Preferences

Yeah there's no there there when it comes to MCP. It's crazy to me that the world bought into the idea when the "spec" literally boils down to "have your server give the LLM some json". Just illustrates how powerful it is to attach names to things, especially in a hypestorm in which everyone is already frothing at the mouth and reason is hard to come by. Give people some word they can utter to help them sound like they're on the "bleeding edge" and they'll buy into it even if it's totally pointless.

"Have your XYZ give the LLM some JSON" is pretty close to how all tool calling works with or without MCP.
What next you are going to tell me rest and async are implemented in code?! And not just willed into existence by the compiler!
Markdown is for output too.
It gave everyone a reason to think about the usability of the interfaces they were exposing.

Many endpoints have tons of fields irrelevant to 95% of external users. Now those are gone.

Or they implemented higher level abstractions for the actual tasks instead of making developers compose a bunch of little pieces.

And it has a standardized manifest.

Execs, PMs, and customers having that word to utter as part of the AI hype train created the opportunity for that industry-wide cleanup to happen. Calling it pointless is very naive. It's actually kind of extraordinary.

Thanks for offering another perspective on it. I can buy into this partially.

At the same time, I'm skeptical that this won't just become yet another dead protocol once the hype abates, at which point all of the perceived benefits were for naught.

This item has no comments currently.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal