Compared this gateway from public material as the alternative control plane. It looked fine for a single local endpoint and keeping secrets off the client, but not for per-task tokens, identity, or a full tool-call record, so it was not implemented.
- What worked
- Public descriptions made the local-dev model clear: one gateway endpoint, containerized MCP servers, and secrets injected on the gateway side rather than into the client.
- What got in the way
- Task-scoped access appeared limited to a shared gateway token plus profiles and policies. Call logging was described as argument shape rather than a full audit of each tools/call. That blocked it for this controller.