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 ?
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!
Love this! Finally someone breaking open the MCP ecosystem for real dev use. mcp-use looks like the right balance between power and simplicity. The agent abstraction + tool discovery is super smart.
Also, hacking an IKEA curtain with MCP is an all-time flex.
Curious if you’re planning to build infra on top or keep it strictly dev tools?
Yes we plan to do more infrastructure work for sure, the idea is that larger teams will need a centralized place where they can configure their MCPs, monitor them, and define access control rules, create agents with specific permissions and capabilities. The old infrastructure (in the dev tool sense) does not really lend itself well to this new use cases.
We are building in this direction and we plan to open source this aspect as well, for now we are working closely with few large companies to first understand their pains deeply.
Really great work! We’ve been integrating LLMs into production chat-based workflows for a while, and mcp-use has given us the biggest DX boost we’ve seen all year. It strips away the boilerplate of the official SDK, so spinning up a new MCP backend becomes almost a copy‑paste job.
From a company perspective that’s huge: adding a new chatbot feature that used to take a couple of sprints and a lot of glue code can now be done in hours instead of weeks.
That is awesome to hear, that is exactly what we had in mind when writing the library, any feedback or improvements that could reduce the work from hours to minutes now ?
Thank you for sharing this!
At Product Weaver we love how mcp-use makes our life easier when accessing MCP servers like Jira, Linear, Notion and many others. We like the clean code we can write, as it's vital for maintaining it.
Ad maiora!
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...),
Interesting project! Today, AI projects move progress forward. Good luck to you!
Thanks :)
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 ?
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!
Love this! Finally someone breaking open the MCP ecosystem for real dev use. mcp-use looks like the right balance between power and simplicity. The agent abstraction + tool discovery is super smart.
Also, hacking an IKEA curtain with MCP is an all-time flex.
Curious if you’re planning to build infra on top or keep it strictly dev tools?
Thanks so much! The ikea was such a cool thing do to, here is the video btw https://www.reddit.com/r/mcp/comments/1jxdi4g/i_wrote_an_mcp...
Yes we plan to do more infrastructure work for sure, the idea is that larger teams will need a centralized place where they can configure their MCPs, monitor them, and define access control rules, create agents with specific permissions and capabilities. The old infrastructure (in the dev tool sense) does not really lend itself well to this new use cases.
We are building in this direction and we plan to open source this aspect as well, for now we are working closely with few large companies to first understand their pains deeply.
Really great work! We’ve been integrating LLMs into production chat-based workflows for a while, and mcp-use has given us the biggest DX boost we’ve seen all year. It strips away the boilerplate of the official SDK, so spinning up a new MCP backend becomes almost a copy‑paste job.
From a company perspective that’s huge: adding a new chatbot feature that used to take a couple of sprints and a lot of glue code can now be done in hours instead of weeks.
That is awesome to hear, that is exactly what we had in mind when writing the library, any feedback or improvements that could reduce the work from hours to minutes now ?
Thank you for sharing this! At Product Weaver we love how mcp-use makes our life easier when accessing MCP servers like Jira, Linear, Notion and many others. We like the clean code we can write, as it's vital for maintaining it. Ad maiora!
!!! Thank you so much, love to hear that !!!
Love this! This is super helpful!
Thanks!!
This is super cool! Building with MCP is such a hassle right now, this is a game changer.
thankss! I appreciate you
[flagged]
No
belli e bravi
grazie mille!