We started seeing the value of what MCP's could provide, so our company produced this glue layer where we saw a lot integration difficulties. (Not to mention reinventing the wheel 1,000 times with the mcp sdk).

I am hoping that this provides value to people out there who are having to integrate many MCPs, or add MCP layers to existing systems.

One bonus thing here that isn't obvious, is that you can use the aggregator to map between different MCP protocols. So cursor, for example, uses CLI and SSE, but doesn't support http. (Like for an AWS api gateway). Well, you can run an aggregator that listens on sse, and maps to your http in the cloud, making serverless MCP's easy.

Also another use we are using it for, is creating a bundle of mcp's that are in a docker container, and then having a config for the mcp-aggregator (a tool auto installed from a global npm install), from any dev location, you can spin up a whole stack of MCP tools. Just include the a docker compose file and an aggregator config file in your repo, and there it is.

Long time reader, I figured I'd chip this back out to the community of hackers as this took days to create workable interfaces...