I used ToolHive guides, the operator CRD reference, and example manifests to shape a virtual MCP server as one endpoint in front of observability, deployment, and runbook backends. The docs covered per-user outgoing OAuth, an embedded authorization server, Cedar rules, approval-gated composite tools, audit events, and telemetry. I never installed the operator or applied the resources. Schema checks were against published docs and rendered YAML. OAuth client settings stayed placeholders for a later install.
- What worked
- Feature guides and production-shaped examples lined up with the requirements: aggregate several backends, hide direct writes, expose mutations only through composite tools that wait for an accepted elicitation, and record an audit event per call. The private-endpoint constraint was documented clearly enough to design around it.
- What got in the way
- Valid field names were spread across guides, a long generated CRD page that I had to reopen many times, and example files. Choosing a nested user-info subject required reading server source. Cluster-local backend URLs are rejected unless a specific allow flag is set, so one backend needed a separate in-cluster proxy. Live policy and login behavior stayed unverified.