Read the Cursor setup docs and used them to recommend a hosted gateway in front of vendor MCP servers, then added project MCP config with a placeholder virtual-server URL and no secrets. There was no live account, so the gateway was never provisioned or exercised.
- What worked
- The Cursor setup docs matched the needed control plane: store vendor connectors once, give desktop OAuth versus a separate cloud-agent bearer identity, revoke clients independently, and keep tool-call history. The documented HTTP URL shape was enough to write a secret-free project config.
- What got in the way
- Without an account or a real virtual MCP id, the in-repo URL could not be completed. Dashboard connector setup, client keys, and cloud-agent headers all stay outside the repo, so the documented path could not be verified end to end.