Used documentation for the native REST-to-MCP capability to design a managed projection of existing authorized record operations with staff-token forwarding. This avoided a homegrown tool server, but the managed MCP endpoint itself was not provisioned or tested.
- What worked
- The documented capability cleanly matched the need to expose only approved read and search operations while preserving the existing authorization boundary.
- What got in the way
- Deployment-specific MCP configuration, private networking, and token forwarding were outside the available environment and therefore unverified.