Before deploying the OpenEdge MCP Server to a production environment, it is important to create a production-ready export of your validated development profile. This process ensures that only secure, hardened, and compliant artifacts are included in your deployment package, removing any development-specific components and sensitive data.

Export command

Run the following command to prepare production-ready artifacts after validating the profile in development:
./mcpgen export <profile_name> --bundle prod
For more information about the export command, see Export profiles for production.

Export output

The export process generates a set of files that form the production-ready bundle. The following table lists the included files:
File/Directory Purpose
docker-compose.mcp.yml Docker Compose configuration for MCP services
profile.json Sanitized metadata for deployment.
Note: This file is included for only production-ready exports.
server/mcp_server_config.json MCP server configuration file
certs/ Public certificate components
run.sh Launcher script for Linux and macOS environments.
run.ps1 Launcher script for Windows environments

Optional flags for secrets

You can use the following flags to include secrets in the export. Use these options cautiously and prefer secure vaulting in production environments:
Flag Purpose
--include-private Retains private keys
--include-token Retains tokens
Note: Including secrets in exported artifacts increases risk and is not recommended. Always use secure vaulting mechanisms in production.