How do you know when a tech article is bullshit? It declares something popular, by dint of their unassailable insight and authority, is definitively dead.
Windows has been dead for decades, but people still insist on using it. Hell, I know people still writing useful, functional new code in Perl. It’s not my cup of tea, but if it’s getting the job done, who am I to judge?
But now we have this chucklefuck who is going to single-handedly steer the course of adoption for millions of people through main force of will? Okay, sure.
the problem is that MCP isn’t really solving a problem that can’t be solved with existing technology. it’s actually infuriating that access to resources is hidden behind this silly new protocol for agents only as if just giving me API access, which is already well-understood and supported, is insecure or traffic heavy.
plus, the gold rush at my company of adding an MCP server to every resource has turned into a graveyard of wasted effort and abandoned projects.
I know people still writing useful, functional new code in Perl. It’s not my cup of tea
I will drink all that sweet Perl tea. It’s f’ing delicious
Anyway, I actually skimmed the article (which smells AI-generated but with decent prompts).
TL;DR: MCP eats context, has low reliability, and overlaps with existing CLI/API.
Yeah, SKILS.md and CLI access is the way to go for anything you can. MCP is for the rare complex UIs that can’t/don’t break down into CLI-friendly subcomponents and/or need bidirectional real-time communucation.
How do you know when a tech article is bullshit? It declares something popular, by dint of their unassailable insight and authority, is definitively dead.
Windows has been dead for decades, but people still insist on using it. Hell, I know people still writing useful, functional new code in Perl. It’s not my cup of tea, but if it’s getting the job done, who am I to judge?
But now we have this chucklefuck who is going to single-handedly steer the course of adoption for millions of people through main force of will? Okay, sure.
the problem is that MCP isn’t really solving a problem that can’t be solved with existing technology. it’s actually infuriating that access to resources is hidden behind this silly new protocol for agents only as if just giving me API access, which is already well-understood and supported, is insecure or traffic heavy.
plus, the gold rush at my company of adding an MCP server to every resource has turned into a graveyard of wasted effort and abandoned projects.
I will drink all that sweet Perl tea. It’s f’ing delicious
Anyway, I actually skimmed the article (which smells AI-generated but with decent prompts).
Yeah, SKILS.md and CLI access is the way to go for anything you can. MCP is for the rare complex UIs that can’t/don’t break down into CLI-friendly subcomponents and/or need bidirectional real-time communucation.