Configure environment variable overrides
- Last Updated: December 23, 2025
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
This section explains the essential environment variables that can override configuration settings in the OpenEdge MCP Server. Environment variables are intended for last-mile operational adjustments or runtime injection. For production environments, prefer using explicit JSON configuration files under version control to ensure reproducibility.
The following table summarizes the essential environment variables and their
descriptions:
| Environment variable | Description |
|---|---|
MCP_SERVER_CONFIG |
Specifies the path to the configuration JSON file, which can be absolute or relative. |
SERVICE_ACCOUNT_PUBLIC_KEY |
Provides an inline PEM for the service account public key. |
SERVICE_ACCOUNT_PUBLIC_KEY_FILE |
Specifies the path to a PEM file containing the service account public key. |
MCP_USE_SSE |
Forces SSE transport for legacy client support. |
OPENAPI_DUMP_SPEC |
Writes the enriched OpenAPI specification to a file for debugging purposes. |
OPENAPI_LOG_ANNOTATIONS |
Controls logging of enrichment annotations. |
OPENAPI_LOG_ANNOTATIONS_VERBOSE |
Enables verbose annotation logging with per-operation and tag details. |
DOWNSTREAM_CERTS_DIR |
Specifies the directory for downstream CA bundles and optional client cert/key for mTLS. |
TLS_CERTS_DIR |
Provides an alternate path for downstream trust and client TLS assets. |
TLS_P12_PASSWORD |
Password for PKCS#12 bundle if encrypted. |
TLS_KEY_PASSWORD |
Password for encrypted private key if used. |
TOKEN_EXCHANGE_LOGIN_TOKEN |
Authorization header value for token exchange, used with the configured prefix. |
Note: Avoid relying heavily on environment variables for production
reproducibility. Use explicit JSON configuration files under version control to
maintain consistency and traceability.