frontmcp.config server settings --- they are injected as environment variables at build time and read by the built-in middleware.
Quick Start
Add security headers tofrontmcp.config.ts:
CSP Configuration
Example Directives
Security Headers
X-Content-Type-Options: nosniff and X-Frame-Options: DENY are applied by default even without explicit configuration. Set them to empty strings to disable.Environment Variables
All settings are injected as environment variables at build time by the deployment adapter:
You can override these at runtime without rebuilding:
Programmatic Access
For built-in HTTP transport targets, FrontMCP applies the configured security headers during HTTP response handling. For custom transport adapters, header application is your adapter’s responsibility — wire equivalent logic into the response pipeline yourself. The internal helper utilities are not part of the public@frontmcp/sdk API; if you need them re-exported, open a feature request rather than importing from repository-internal source paths.
Report-Only Mode
UsereportOnly: true to test CSP rules without blocking content:
Content-Security-Policy-Report-Only header instead of Content-Security-Policy, allowing you to monitor violations before enforcing the policy.
Related
Configuration File
Full configuration reference
Production Build
Build and deploy for production