api-config

MCP server configuration maps environment variables to config fields for identity, transport, auth, storage, and telemetry using a defined priority order. It separates core configuration from server-specific Zod schemas to prevent misconfigurations across nodes and workers.

Lazy parsing for MCP server config uses the parseEnvConfig mechanism to defer schema validation until needed. This prevents startup pollution by ensuring server config values are only parsed when accessed during runtime operations.

Core config handles shared environment variable mappings across nodes, while server-specific schemas define isolated Zod validations. This separation enforces distinct env var names and priority orders to prevent misconfigurations between core and server contexts.

Validating and overriding config values across worker boundaries requires applying server-specific Zod schemas to parse environment variables. This ensures config integrity is maintained when passing settings between different runtime environments and worker processes.

MCP enforces specific environment variable names for transport, auth, identity, storage, and telemetry configurations. These defined names follow a strict priority order to ensure correct environment variable handling and prevent schema pollution.

MCP server config fails from schema pollution when core and server configurations are not properly separated. Using lazy parsing via parseEnvConfig defers validation and prevents startup pollution by keeping server-specific schemas isolated.