Export profiles for production

./mcpgen export <profile_name> [options]

The exported runtime profile directory under exports/<profile_name>/ contains only the essential files required for running the MCP server in production. Development-specific files, such as temporary assets or client convenience scripts are excluded to ensure a clean, secure, and minimal deployment package. After the export, you have:

• A directory named exports/<profile_name>/ containing the production-ready profile.
• Optionally, a compressed tarball (profile-<profile_name>.tar.gz) if you use the --tar flag or the export-tar command. This tarball is useful for distribution or deployment across environments.

The following table lists the available flags for the export command, describing their purpose and any important usage notes:

Flag	Purpose	Production guidance
--output DIR	Specifies the destination root directory. The default root directory is ./exports.	Ensure this directory is excluded from version control.
--bundle PRESET	Defines the content preset: dev, prod, or strict-prod.	Use prod or strict-prod for production deployments.
--include-private	Retains private keys in the export.	Avoid unless performing secure backup or migration.
--include-token	Includes the generated service account JWT.	Rotate the token soon after import if used.
--include-context	Copies referenced context/ files.	Ensures enrichment parity across environments.
--include-prompts	Copies prompt markdown files.	Required if prompts influence workflows.
--prod	Strips development artifacts and tightens permissions.	Mandatory for any non-development export.
--tar	Creates a compressed tarball of the export.	Useful for distribution.

Use the export-tar command to create a compressed archive of the exported profile.

./mcpgen export-tar <profile_name>

This command performs an export and packages the profile as profile-<profile_name>.tar.gz.