4 ms·
I think there's going to be a lot of places where you want the middleare that's only exposing a sub-set of apis. and the Ideas that you copy some URL, put it i
by taude 1y ago
I think there's going to be a lot of places where you want the middleare that's only exposing a sub-set of apis. and the Ideas that you copy some URL, put it in your LLM Client, and then it magically gets all the tools/endpoints available to you, and you start interacting with it, simplifies the process greatly for a lot of users. No swagger, no http post, body vs params, etc....just play with with your prompt sentance until you get it to do what you want.
(edit: sorry, I responded to wrong thread.)
- v3ss0n 1y agoYeah that but - Why SSE? - Why JsonRPC - Why Statefulness REST based Tool Call Server would work 100% fine. Now auth have to be redone for those specifically. And for users of MCP Tools - they are sending a lot of their information to whatever service they are running - that they have never control of For developer it is not necessary and security nightmare if you use someone's MCP service or run your own. For users , it is a privacy nightmare .