Skip to content

Move a Cline Montage definition without carrying automatic approvals

A Cline definition can include both connection details and execution permissions.

Integrations

How do I move a Cline Montage definition without carrying automatic approvals?

A Cline definition can include both connection details and execution permissions. Transfer the remote endpoint deliberately while reviewing approval state independently, so a simple profile migration does not silently broaden the destination user’s authority over retained workspace records. Connection settings and execution approvals should be separate migration artifacts. Preserve the hosted streamableHttp definition without silently importing automatic write permission or another person’s account storage into the destination Cline environment.

01 / CONFIGUREOne remote endpointUse this client's documented HTTP setup
02 / AUTHORIZEYour workspace accessUse a supported sign-in or credential flow
03 / VERIFYRun signals_statusCheck a real workspace response
Copyable task-specific request
Help me move a Cline Montage definition without carrying automatic approvals. Separate remote settings from automatic approvals in the existing definition. Obtain signals_status in the destination after supported consent. No writes.
01 / Integrations

Inventory the source

Separate remote settings from automatic approvals in the existing definition. The source profile’s trust choices do not settle which operations the destination user should authorize. A migration checklist should list URL and transport separately from tool approval rules so they are not imported as an inseparable bundle.

02 / Integrations

Inspect the destination

Review Remote Servers controls or existing mcpServers entries before merging. Preserve other servers and resolve a montage naming collision rather than replacing an unrelated tool. Compare the destination server’s purpose before merging; a same-name entry may already represent another owner’s deliberate configuration rather than stale debris.

03 / Integrations

Carry remote intent only

Use type streamableHttp with the hosted URL and no exported account secrets. Migrating configuration is not permission to convert the connection into a local process. Do not embed OAuth storage in the transferred definition or replace the remote target with a local launcher to avoid destination consent.

04 / Integrations

Reassess approvals

Leave workspace writes under explicit review instead of blindly copying autoApprove settings. Authentication and execution permission need different acceptance checks after a definition moves. Approval review is not a request to change account permissions; it determines whether the destination task should execute proposed workspace effects automatically.

05 / Integrations

Validate before resuming

Obtain signals_status in the destination after supported consent. Verify its workspace without treating the migrated definition as approval to repeat the source conversation’s earlier remote changes. The destination’s first read should verify its intended account, while any old source conversation remains paused rather than being replayed after migration.

Keep the boundaries clear.

  • Do not embed OAuth storage in the transferred definition or replace the remote target with a local launcher to avoid destination consent.
  • The destination’s first read should verify its intended account, while any old source conversation remains paused rather than being replayed after migration.

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.

Know what social media shows about you.
Start with a question.

Get started
montage