I'm not sure how this relates to the comment you replied to?
I see the confusion :) I meant my comment not as an actual reply to my own comment but more as an afterthought.
Show HN: Mcp-use – Connect any LLM to any MCP
41–50 of 75 posts
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#42> MCP-Use supports running MCP servers in a sandboxed environment using E2B's cloud infrastructure. If you want to support a local and privacy friendly sandboxed environment for code execution, you may consider something I have built, Coderunner - https://github.com/instavm/coderunner - it uses Apple's native container for hosting a jupyter server and a headless browser.
That is nice, is this like a local E2B ?
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#43Huge variety of problems with this for mid-market or enterprise use. This is basically a toy right now and can’t be used for solving repeatable, valuable problems for actual businesses, ie: stuff that matters. One: dependence on langchain. Two: Security? Observability? Three: You have never asked yourself, why would someone want to connect an LLM to infinite random mcp servers. The vast majority (of mcp tools and ser…
Why is dependence on LangChain an issue? Not that I disagree necessarily, just wondering if there's a consensus that LangChain is too opinionated/bloated/whatever for real industry applications, or if there's some other reason.
Not original commenter here, and not by first hand experience. BUT. I got this kind of feedback from some communities, and I wanted to understand what companies think of this, I asked some dev that works in a company that sells software to enterprise he says that enterprise still use langchain mostly and they are fine with it. On a personal level I agree with the feedback in that langchain has some drawbacks, but at the same time it's a great way to get started.
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#44[stub] [explained at https://news.ycombinator.com/item?id=44752814 ]
nice. i feel interaction with mcps now is sort of broken, and building on top of the sdk is a pain. being compliant with the specification is a way better take.
i'm curious to see how this scales. and it's a good starting point on reshaping our interaction with basically every single application.
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#45[stub] [explained at https://news.ycombinator.com/item?id=44752814 ]
[flagged]
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#46What is really interesting in this article is that no where in either the github link presented nor on his web site, mcp-use.com, does he actually explain what an "MCP" server is, what it might be used for, the benefits of doing this. It seems he is so far in the weeds with this that it was an after thought to describe what any of this means or might be useful for.
Hey jijji, fair point, I assumed that the hn audience and/or the people interacting with the website would already know about MCP.
If you're not familiar, MCP is an open-source protocol created by Anthropic and later adopted by all major model providers. It defines how LLMs communicate with external applications and services.
More specifically, MCP standardizes the interaction between an MCP server, where the business logic resides, and a client, loosely speaking an LLM that consumes it. The MCP server exposes primitives like tools, resources, and prompts, which the client can use to perform various operations. The communication protocol used is JSON-RPC 2.0, and interaction between the client and server occurs either locally through stdio streams or remotely over streamable HTTP.
Here are some of the good things about it:
Easier integration into agents: From an agent development perspective, MCP simplifies integrating external capabilities. Previously, you'd have to write custom integrations, which is sometimes difficult or limited by the availability of public APIs. Now, you can directly plug in an MCP server, if provided. if you had to write a custom integration, using MCP is beneficial as well, as it separates integration logic from agent logic, making it easy to hot swap any of the two.
Standardized interface and incentives for companies: Because MCP standardizes communication, developers can create MCP servers independently from the specific LLM or agent consuming them. This compatibility with clients like ChatGPT, Claude Desktop, and mcp-use provides a strong incentive for companies to develop MCP servers for their own applications. This is great because they are the ones that know best how to do this (and can).
Widespread Adoption: A protocol's value heavily depends on its adoption, and MCP is sticking real well. Companies, developers, and major model providers are mostly on board with MCP.
I'd love to know if somebody has other positive points or negative points about mcp and can share it here. Some are across the thread already.
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#47[stub] [explained at https://news.ycombinator.com/item?id=44752814 ]
nice. i feel interaction with mcps now is sort of broken, and building on top of the sdk is a pain. being compliant with the specification is a way better take. i'm curious to see how this scales. and it's a good starting point on reshaping our interaction with basically every single application.
Hey thanks for the comment (xmcp in the house)! I can certainly agree with the sdk being a pain, why do you feel that the interaction is broken ? in which way ?
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#48[stub] [explained at https://news.ycombinator.com/item?id=44752814 ]
Good, I have not dig into the code, just one question: how to deal with other stuff supplied by MCP server, I mean besides tools, server also supplied "resources", "prompt" and other functionality, I saw some struggle here(https://github.com/vincent-pli/mcp-cli-host/blob/main/docs/r...) and here(https://github.com/vincent-pli/mcp-cli-host/blob/main/docs/p...),
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#49Not sure what is going on, but I see a lot of 1-karma-point HN users hyping this.
Yeah I don't even see the point of this. There's enough MCP clients now and the whole point of MCP is to make tools available to any LLM that can use tools.