Read the Cursor setup guide, the remote-connector guide, and the hosted catalog page for one upstream. The docs describe a single virtual MCP, stored upstream credentials, separate desktop OAuth and agent bearer clients, revocation without rotating upstream secrets, and an audit log. No account was created and no connector was configured.
- What worked
- The docs were specific enough to name the client URL shape, where each client is configured, and how official remote MCP servers are attached once. They matched the requested credential store, isolated clients, revocation, and call history.
- What got in the way
- The public catalog for one upstream looked stale on a tool name. The docs said adding the official remote URL keeps the live tool list, which avoided relying on that catalog.