Repository navigation
Consumers + registries: the MCP aggregation plane agents actually need #517
vgmartinez
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Most teams discover MCP by wiring two or three servers into an IDE, then hit the same wall: upstream keys on every laptop, each agent gets a different
tools/list, and the chat-completions path does not share identity or budgets withtools/call.An LLM proxy covers provider routing. An agent gateway also needs an MCP aggregation plane under the same consumer model.
Pattern that has held up for us:
tools/listfiltering before the model or tool runs.I wrote a short technical note on that consumers + registries shape:
https://neuraltrust-victor.hashnode.dev/consumers-and-registries-the-mcp-aggregation-plane-agents-actually-need
TrustGate is the self-hosted Go Agent Gateway (Apache-2.0) we are building around it — OpenAI-compatible proxy plane + MCP aggregation under one consumer identity:
https://github.com/NeuralTrust/TrustGate
If you are already drowning in MCP configs and laptop API keys, the 60-second quickstart on the repo is the fastest way to poke holes in the model. Feedback welcome — especially where the registry/consumer split breaks for your setup.
Disclosure: CTO at NeuralTrust (building TrustGate).
All reactions