Re:MCP vs. API Explained
by 1116574 on Saturday March 08, 2025 @04:17PM
(#43303619)
The article has the same usb-c photo three times, but doesn't actually explain what it is, or how it works.
[ Parent
| on HN ]
Not only that, but the whole section on "Consider these scenarios" simply described the same thing as an API each time, but added words like "smoothly" and "richer" to make it sound different.
I honestly think most of the article was written by an LLM.
Re:MCP vs. API Explained
by crabmusket on Saturday March 08, 2025 @10:57PM
(#43306060)
The structure seems very LLM-ish. And the details are blurry:
> Two-way communication: MCP supports persistent, real-time two-way communication - similar to WebSockets. The AI model can both retrieve information and trigger actions dynamically".
This is not what two-way communication means.
unfortunately it is indistinguishable from what a reasonable human high on mcp copium might write
Re:MCP vs. API Explained
by doug_durham on Saturday March 08, 2025 @06:50PM
(#43304690)
The usb-c metaphor along with most of the text are lifted from the Anthropic documentation without attribution. I'm not impressed with the author.
Author here – fair point! I can def see how it could've used more explanation. I'll update the post - appreciate the heads-up!