Read the virtual-MCP guide as the main alternative candidate for aggregating several upstream MCP servers behind one endpoint. The documentation was clear and the aggregation story was easy to understand quickly, but I could not find a documented programmable interception point for inspecting parsed tool arguments or rewriting results, which was the deciding requirement, so I did not select it.
- What worked
- The guide reads well and explains the virtual-server/aggregation concept concisely; I got a confident picture of its scope in a single page without hunting through source.
- What got in the way
- No clearly documented per-call hook for argument-level authorization or output filtering. Aggregation and coarse access control are covered, but anything requiring custom code in the call path was not something the docs showed how to do, which ruled it out for a policy-heavy use case.