Original Summary

I've been building an MCP Gateway called Yūsetu and would love some feedback from people who are actually using MCPs. Stupidly Simple and Straight Forward MCP Gateway. The basic idea is pretty simple: put multiple MCPs behind a single endpoint and make them easier to manage. One thing I wanted to solve differently: Don't have a hosted MCP? Just give Yūsetu the Git repo. If an MCP is only available as a GitHub repository, Yūsetu can run it inside the gateway and expose it alongside your other MCPs. It also currently does some tool/context optimization and I'm seeing 30%+ token savings , with higher savings on less-optimized MCP servers. Currently it has: Multiple MCPs → one endpoint Run MCPs directly from Git repositories Tool discovery & execution Token/context optimization API key authentication Self-hosting I'm planning things like tool grouping, team support, per-key tool restrictions, and MCP downtime alerts, but I don't want to blindly build features nobody needs. Yūsetu is open source, MIT licensed, and will always be free to use . GitHub: https://github.com/builtbyaakash/yusetu I'm mainly looking for feedback at this stage. If you use MCPs regularly, what would make a gateway like this genuinely useful to you? What am I missing? What would you change? What would stop you from using it? I'd especially appreciate the brutally honest feedback. 😄   submitted by   /u/YardComprehensive186 [link]   [comments]

  • 情报分类：服务器与云资源
  • 分类依据：内容涉及服务器、云资源或网络线路
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/16 21:27:49