←back to thread

MCP is eating the world

(www.stainless.com)
335 points emschwartz | 2 comments | 21 Jun 25 16:30 UTC | HN request time: 0.787s | source
Show context
neya ◴[24 Jun 25 18:00 UTC] No.44368934[source]▶
Obligatory note - if you're a backend developer, you do not need MCP. MCP is just tool/function calling. It has been around for a lot longer now. MCP is only needed if you need something to integrate with the frontend chat applications. If you need to automate something with LLMs, you do not need MCP. Right now, it's just the new cool buzzword to throw around.
replies(2): >>44369143 #>>44371579 #
1. hadlock ◴[24 Jun 25 22:09 UTC] No.44371579[source]▶
You don't need to use RESTful JSON to get two computers to communicate with eachother, either. You can just implement your own thing, and if someone wants to interface with it, they can write their own adapter! Who needs decades of battle tested tooling? This can be a Not Invented Here safe-space. Why not.
replies(1): >>44373381 #
2. neya ◴[25 Jun 25 03:21 UTC] No.44373381[source]▶
You think you're being sarcastic, but you don't get the point - implementing 3rd party Saas tools in your Saas backend means one MCP server per service, which can quickly add up, not to mention is bad design. I'm not opposed MCP protocol itself, it's just not needed if you're providing a Saas that talks to many vendors, you don't necessarily need MCP for it.

Also, MCP is relatively new, not "bAtTlE tEstEd"