Used Hoop documentation, source repositories, its MCP proxy, and the published Helm chart to design and validate an identity-aware MCP gateway with approvals and audit controls. The capabilities fit well, but exact declarative configuration and API details required extra investigation.
- What worked
- The product combined MCP aggregation, identity, approvals, session recording, and audit features in one suitable control point. Its pinned Helm chart rendered successfully after configuration was corrected.
- What got in the way
- The published chart values did not make the mandatory API URL setting obvious, so the first render failed. Provisioning and access-policy API details were also less clear than the high-level documentation.