How do I preserve Cursor MCP settings when moving a project?
Moving a repository should not replace unrelated MCP servers or export account authorization. Carry the Montage remote definition deliberately, preserving the mcpServers structure and validating it in the destination Cursor environment before using private workspace data. Inspect the destination’s complete MCP file before merging one URL entry. Transferring configuration should neither discard neighboring servers nor imply that private grants travel safely with repository files or project settings.
Help me preserve Cursor MCP settings when moving a project. Read the existing .cursor/mcp.json before merging anything from the old project. Complete supported authorization if requested, then inspect signals_status in the new context. No writes.Inspect the destination file
Read the existing .cursor/mcp.json before merging anything from the old project. A destination that already has useful server definitions must not be replaced by a minimal one-server example. A safe merge plan identifies the single montage entry and preserves every unrelated object already present in the destination configuration.
Compare the Montage entry
Check whether the montage key already names the hosted URL. If it differs, determine which definition belongs to this project instead of assuming the older checkout is authoritative. If the two definitions differ, document the intended destination explicitly instead of choosing whichever file was edited most recently.
Merge only registration intent
Retain the documented mcpServers URL shape and omit credentials from the transferred definition. This migration concerns configuration, not importing browser state or changing the application’s source dependencies. Never place private consent material alongside the URL merely because the destination editor has not yet completed its own authentication.
Refresh through Cursor controls
Use the client’s normal configuration refresh and inspect the tools in the destination conversation. A JSON file that parses successfully does not prove the active editor loaded that file. Use the destination conversation’s visible tool inventory as loading evidence, while reserving the stronger access claim for an actual authorized read.
Validate before resuming work
Complete supported authorization if requested, then inspect signals_status in the new context. Do not infer that success there removed access from the original working copy or revoked any existing grant. The migration result should not say the source account was disconnected; configuration transfer alone does not prove remote grant revocation.
Keep the boundaries clear.
- Never place private consent material alongside the URL merely because the destination editor has not yet completed its own authentication.
- The migration result should not say the source account was disconnected; configuration transfer alone does not prove remote grant revocation.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.