Skip to content

Promote Configuration with the MCP

The promote_package prompt asks a model to move configuration from one QIE engine to another, for example from a test engine to production, through a configuration package. The AI client needs both engines added as MCP servers, under names you choose. Start it from the server of either engine. Codex does not support prompts, so ask it for the same work in your own words (see Connecting Codex).

Arguments

Argument Required Holds
what Yes The zones to promote, and the objects in each when not all of them.
from Yes The name your AI client gives the MCP server of the engine to promote from.
to Yes The name your AI client gives the MCP server of the engine to promote to.

What the model is asked to do

  1. Read each engine's name and Environment Label with get_instance_info, and stop if either is not the engine you expect.
  2. Export the configuration from the first engine with export_configuration, with sample messages only if you ask for them.
  3. Describe the package on the second engine with describe_package: what it holds and which zones it goes into there. Private keys are never in a package, so the model tells you when the channels use any, and they can be imported on the second engine with import_certificates.
  4. Import the package on the second engine with import_configuration, renaming zones with zoneOverride where the second engine names them differently. QIE asks you to confirm the zones and options before anything is imported.
  5. Report the outcome and the channels that need a restart.

The model does not start, stop or restart any channel until you say so.

Tip

Set the Environment Label on each engine's Model Context Protocol (MCP) page, such as "Test" and "Production". The label is how the model, and you, tell the engines apart before anything is imported.

What the package carries

The package passes through the AI client and its provider on its way from one engine to the other. Secured values in it are protected only as in any export file (see MCP Package Tools). The package is limited by the Package Ceiling (bytes) on each engine's Model Context Protocol (MCP) page.