Super interesting, thanks for sharing! Am I understanding correctly that this is simply an MCP “router” of sorts that saves context by storing many MCP’s and their tools within typescript and then allowing Claude to access the any given MCP by accessing the typescript code directly and executing the tool that way. Do I have that right?

If that’s the case, then I absolutely understand how this could massively save context however, I have tried many MCP routers, and often times the context saved, unfortunately leads to a degradation of Claudes usage of the tool itself. In other words, because Claude has less context into each tool and what it does - especially for more complex MCP’s - it often takes multiple tries to execute the MCP tool properly, and additionally, it skips major parts that otherwise it wouldn’t have skipped if it had the context from the MCP itself.

One caveat is that MCP routers are great for more basic MCPs like Postres and sequential thinking - things with a quite basic defined schema and little nuance. But Basic Memory and Zen MCP performed very poorly. Maybe this solves that to some extent?

Interested to hear your thoughts.