3 ms·
I meant to say that MCP is just a wrapper around good old function/tool calling, it's not a new superpower by itself. So, if you're designing a Saas, you don't
by neya 1y ago
I meant to say that MCP is just a wrapper around good old function/tool calling, it's not a new superpower by itself. So, if you're designing a Saas, you don't need to use MCP yourself, you can just use good old function/tool calling.
To answer your specific queries, I use the autocomplete in VS Code and I directly chat with ChatGPT-o3 for advanced problems because my background is in Elixir and most models that are hyped up fail badly with Elixir. I'm always a huge fan of o3 as it can solve the most complex problems I throw at it..
- atonse 1y agoYes, but if I'm implementing "good old function/tool calling" today, why would I not implement it as MCP? I suppose it complicates things? MCP, in addition to being tooling endpoints, would also open up my software to a rapidly growing ecosystem that requires minimal additional work. AND I can still use those same endpoints as tools. What would be the argument for "you don't need MCP when implementing new stuff"?
- neya 1y agoI think you're confusing implementing MCP for your own software offering/Saas, which is different and I think you should do it, vs implementing third party MCP servers into a Saas backend, which is what I'm talking about. Because, to do the latter, the standard design is one hosted MCP server per vendor. If you use more than even 5, that's a lot of servers to maintain in a Saas context.
- atonse 1y agoah that's a great point. noted.