3 ms·
mcp was a dud
by apwell23 1y ago
mcp was a dud
- consumer451 1y agoWhat is the superior way for an LLM to interact with your product?
- apwell23 1y agollm can call my existing apis fine. curious what kind of problems you are running to with your existing apis?
- consumer451 1y agoI want LLM chat integration with my product. So far, it seems that if you give an LLM a few tools to create projects and other entities, they seem to be very good at using them. The user gets the option of chat driven ui for our app, with not that much work for limited features. Currently building internal MCP servers to make that easy. But I can imagine having a public one in the future.
- brazukadev 1y agoTool calling is one of at least 5 core features of MCP
- apwell23 1y agook but not sure why i need to build an mcp for my product if llms can already call my existing apis ?
- brazukadev 1y agoIf you are not sure, you don't need it. If you get to understand the usefulness of MCP, then you might find a use for it.
- apwell23 1y agowell i was responding to person who was asking me "what a better way over mcp" to interact with your product. looks like you inserted yourself with your usual one line non sequiturs. BOT.
- consumer451 1y agoPerson you were responding to here. You do have a solid point/question. To be completely honest: my original thinking was that for once, I am going to go with the flow on something like this. I often fight inertia, but this felt like a bad thing to do it on. Now, I realize that the best argument for MCP vs function calls in my case, is that I want to allow external products/agents/chatbots to interface with my app. MCP is that standard. I will implement very carefully, but that's what I need to do.