How do I move Continue MCP definitions between documented file formats?
Continue supports loading JSON or YAML definitions, but a format move still needs the installed release’s enclosing schema. Preserve one intended remote entry and avoid leaving duplicate files that make the active Montage configuration ambiguous during subsequent Agent sessions. A format move must preserve the installed enclosing schema as well as transport intent. Leaving two plausible Montage definitions behind can obscure which file and account path produced later Agent behavior.
Help me move Continue MCP definitions between documented file formats. Inspect .continue/mcpServers/ for Montage and duplicate entries. After approved auth, obtain signals_status through the destination definition. No writes.Inventory current definitions
Inspect .continue/mcpServers/ for Montage and duplicate entries. Identify the project’s established format before creating a second file with a similar server name. An inventory should distinguish active and duplicate definitions before a format move, avoiding two plausible entries that make later tool selection ambiguous.
Check enclosing schema
Follow the installed Continue release’s documented JSON or YAML layout. Syntax conversion alone cannot compensate for missing wrapper fields or another client’s unrelated mcpServers structure. A JSON-to-YAML translation must preserve the documented enclosing contract rather than only converting braces and indentation into a syntactically valid file.
Preserve transport boundaries
Retain documented streamable-http intent and the hosted address without transferring account secrets. Representation changes should not silently alter how authorization or execution permission is handled. The remote endpoint should remain the same across representations, letting the review isolate format loading from account or transport changes.
Load one clear entry
Use normal configuration controls to inspect the Agent tool set after the planned move. Two files parsing individually does not prove the active definition is unambiguous. The loading observation should identify one intended entry and avoid assuming duplicates are merged safely when the release documentation does not say so.
Validate the new representation
After approved auth, obtain signals_status through the destination definition. Name the format actually loaded without claiming a successful conversion established authorization parity across Continue releases. A destination-specific status response can verify this move’s path without certifying every other release’s format parser or account authorization behavior.
Keep the boundaries clear.
- The remote endpoint should remain the same across representations, letting the review isolate format loading from account or transport changes.
- A destination-specific status response can verify this move’s path without certifying every other release’s format parser or account authorization behavior.
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.