Created GitOps-style MCP server manifests and an operator guide using the official documentation. Identity, routing, and virtual-server concepts fit the task well, but approval automation was not clearly documented and tenant activation could not be tested.
- What worked
- The documented virtual MCP server, per-user authentication, access-control, approval, and audit concepts covered the requested architecture well. Official type and enum references provided enough detail to build supported manifest shapes.
- What got in the way
- Approval-policy configuration appeared centered on the control-plane UI and lacked a clearly documented configuration-as-code payload. Documentation required HTML inspection and cross-referencing, and the configuration could not be validated against a live tenant.