←back to thread

MCP is eating the world

(www.stainless.com)
335 points emschwartz | 1 comments | 21 Jun 25 16:30 UTC | HN request time: 0.229s | source
Show context
0x500x79 ◴[24 Jun 25 15:52 UTC] No.44367530[source]▶
I believe that MCP is a bit over-marketed.

MCP allows you to bring tools to agents you don't control. It's awesome, but it isn't the right match for every problem. If you believe the hype of X/LinkedIn you would think that MCP everywhere is going to be the solution.

Bringing tools to your local Claude client is awesome, but there are still challenges with MCP that need to be solved and like all technology, it isn't applicable universally.

Not to mention it's a recipe for burning tokens!

replies(6): >>44367740 #>>44367752 #>>44367901 #>>44367968 #>>44368623 #>>44371990 #
pphysch ◴[24 Jun 25 17:30 UTC] No.44368623[source]▶
MCP is a major lifeline for OpenAI and Anthropic. Their only reasonable way to compete with the big vertical AI integrators is if the "community" does all the hard work of integration, hence MCP. After the initial burst of greenfield enthusiasm I suspect it will stagnate as a yet another maintenance burden.
replies(2): >>44373979 #>>44374653 #
1. visarga ◴[25 Jun 25 07:47 UTC] No.44374653[source]▶
Simple - you use MCP agents to update your MCP servers. I made 2 MCPs both 100% vibe coded. Keep the constraints - docs+tests - and you can regenerate the code as needed.