Re:An LLM does not need to understand MCP
by anthonypasq on Thursday August 07, 2025 @10:20AM
(#44824795)
it separates FE and BE for agent teams just like we did with web apps. the team building your agent framework might not know the business domain of every piece of your data/api space that your agent will need to interact with. in that case, it makes sense for your differnet backend teams to also own the mcp server that your companies agent team will utilize.
[ Parent
| on HN ]
Why don’t they just own a REST or RPC server? This is the part of the MCP motivation I’m not totally getting. In fact, you can prove to yourself that your LLM can hook into almost any existing REST api in a few minutes, which gives it more existing options and functionality than just about anything else as it stands now.
Things like swagger or graphql already provide you discovery.
Re:An LLM does not need to understand MCP
by dragonwriter on Thursday August 07, 2025 @11:07AM
(#44825471)
> This is the part of the MCP motivation I’m not totally getting
Would it help you to know that the original use case of MCP was communicating information about and facilitating communication with servers that the LLM frontend would run locally and communicate with over stdio, and that remains an important use case?