[stub] [explained at https://news.ycombinator.com/item?id=44752814 ]
Love this! This is super helpful!
Show HN: Mcp-use – Connect any LLM to any MCP
11–20 of 75 posts
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#12Since you're in the current YC batch, why is this a Show HN instead of a Launch HN?
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#13I get the client part, great job!
However, the agent is really just a wrapper of Langchain AgentExecutor. This doesn't seem like something someone would want to put into production.
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#14Do you do anything to deal with the model performance degradation caused by having too many MCP tools? Would be cool to see a smart MCP router added here
We did! Basically we have a meta layer between the Agent and the MCP servers you give to the clients.
We call this server manager, basically instead of exposing all the tools from all the servers at once to the agent we only expose 4 meta tools: - list servers() - connect to server(server_name) - search_tool(query) - disconnect from server(server_name)
So that the agent can dynamically connect to specific servers without flooding its context with all the tools.
The search tool basically performs semantic search over all the tools from all the servers returning the top N results (tools) and the server they belong to so that the agent can connect to the right server.
A demo of this is here https://www.reddit.com/r/mcp/comments/1k598v9/give_your_agen... where I hid a useful tool in a sea of useless ones (10 useful, 3000 useless) and the agent was able to find and use the right one.
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#15I get the client part, great job! However, the agent is really just a wrapper of Langchain AgentExecutor. This doesn't seem like something someone would want to put into production.
Valid feedback, we did not put as much work on the agent as we did for the client and MCP side yet, but we plan to write a cleaner more composable MCPAgent as well.
Actually I would be super happy to hear what you consider a standard here, something like https://openai.github.io/openai-agents-python/ ?
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#16Re: Show HN: Mcp-use – Connect any LLM to any MCP
#17[stub] [explained at https://news.ycombinator.com/item?id=44752814 ]
Super cool project — love the direction you're taking with simplifying MCP integration and tooling! The search layer between agent and servers is a clever abstraction to reduce cognitive + compute load. Also appreciate the IKEA curtain flex
Would love to see how this evolves toward more dynamic infra setups. Keep it up!
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#18Since you're in the current YC batch, why is this a Show HN instead of a Launch HN?
I answered this question in a similar case a few months ago: https://news.ycombinator.com/item?id=43111524. If you read that and still have a question that isn't answered there, let me know!
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#19Huge 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 servers) are insecure, vibe coded, basically terrible.
Four: There needs to be way more focus on quality versus quantity. It’s easy to connect LLMs to MCP servers, it’s not a problem companies are willing to spend much money on, the issue is ensuring LLMs call the right tools 98%+ of the time with the right parameters.
Five: There are tons and tons of existing projects for connecting LLMs to 1000s of MCP servers, it’s not a novel project, has no technical moat, and importantly, doesn’t solve a super valuable problem.
The better question to ask or problem to solve is this, given a high value problem, how do you get high values of accurate tool use, first time, while providing security and protection against side effects, jail breaking, random issues etc.
Most companies using “mcp” have a model which is using one or two tools (max) at a time and struggling making it work consistently. Giving them a meta tool to connect to 1000s of (mostly useless) tools isn’t helpful and won’t be taken seriously.
Re: Show HN: Mcp-use – Connect any LLM to any MCP
#20> 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.