MCP is an abstraction like LangChain: useless. Just companies trying to create the next big standard so they can have everyone hooked and later they change for something proprietary.
Yeah that seems to be how it is today. I'm just curious if there's something I'm missing with MCP, or if they want to make some changes down the road that will improve it in this way.
Mm I hadn't thought about the stateful part - so the server is running the whole time the MCP client is active? Rather than being spun up as needed to make a tool call?
MCP is an abstraction like LangChain: useless. Just companies trying to create the next big standard so they can have everyone hooked and later they change for something proprietary.
Glad I’m not alone here. Seemed easier to orchestrate some delegation logic my own
Yeah definitely an ecosystem play
I think getting the LLM to write code is the right way as well. MCP is a simpler/opinionated version of the python lib/APIs.
Yeah that seems to be how it is today. I'm just curious if there's something I'm missing with MCP, or if they want to make some changes down the road that will improve it in this way.
mcp is best for stateful connections to thirtparty providers of data and actions.
shameless plug but im working on something where i give LLMs direct access to APIs without going through mcp.
initial demo is at uncomplexities.com.
Mm I hadn't thought about the stateful part - so the server is running the whole time the MCP client is active? Rather than being spun up as needed to make a tool call?