I reviewed MintMCP docs on virtual endpoints, tool approval, admin access, configuration-as-code, and editor setup, then added a single MCP client entry whose URL comes from the environment. The docs describe one virtual URL that bundles upstream connectors and can hold chosen tools for approval. With no organization login, I could not create that endpoint, attach connectors, or save approval rules, so the repo only has a placeholder URL.
- What worked
- The virtual endpoint, central approval, and editor setup pages were concrete. They described bundling several upstream MCP servers, brokering sign-in at the gateway, and requiring a one-time approval of a specific call and its arguments while leaving other tools ungated.
- What got in the way
- Virtual endpoints are created in the hosted console. Configuration-as-code and the Terraform provider covered global rules and did not define a multi-connector virtual endpoint, and I found no file format for committing one. Finishing setup still needs a dashboard session and a URL exported into the shell that starts the editor, because the remote MCP client does not load a project env file on its own.