How do I move LM Studio remote configuration without exporting authorization?
Transferring LM Studio app settings can carry an address without carrying valid account access. Move only the hosted Montage definition, preserve other plugins and evaluate destination authorization separately instead of exporting secrets with a local model setup or declaring login parity. Treat the transferable artifact as remote registration intent, not a bundle of private access. Destination auth capability and the actual returned workspace need their own checks independently of successful JSON merging or local model setup.
Help me move LM Studio remote configuration without exporting authorization. Read the current app-managed mcp.json and identify the Montage URL entry. If compatible auth exists, obtain signals_status and inspect the workspace. No writes.Inspect the source file
Read the current app-managed mcp.json and identify the Montage URL entry. Separate remote registration from unrelated plugin definitions, model settings and any private authorization material. The transfer inventory should identify only the remote definition and leave local inference settings outside this bounded account-access configuration review.
Read the destination configuration
Use the destination app’s documented controls to inspect existing mcpServers entries before merging. Preserve unrelated tools and resolve a montage collision instead of replacing the entire plugin file. Inspect the destination file in full before a scoped merge so its unrelated plugin entries are not discarded by a minimal one-server example.
Transfer only remote intent
Retain the documented URL-based definition with the complete hosted endpoint. Do not copy headers or token storage into a shared settings bundle as part of a configuration move. A URL-only shareable artifact expresses intent without promising login; secure owner-controlled authorization remains a separate destination precondition where supported.
Requalify destination support
Review the destination release’s auth facilities before attempting private workspace execution. Configuration portability cannot establish that the destination supports the same approved account flow as the source. Do not infer matching auth capability from two LM Studio installations merely because they accept the same mcp.json property names.
Check or retain the blocker
If compatible auth exists, obtain signals_status and inspect the workspace. Otherwise record a completed registration review with blocked execution, not a successful migrated connection or automatic source-account revocation. The migration conclusion should distinguish configuration portability, supported authorization and actual status execution instead of collapsing all three into a generic success claim.
Keep the boundaries clear.
- A URL-only shareable artifact expresses intent without promising login; secure owner-controlled authorization remains a separate destination precondition where supported.
- The migration conclusion should distinguish configuration portability, supported authorization and actual status execution instead of collapsing all three into a generic success claim.
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.