Skip to main content
FrontMCP uses a typed configuration file to define project settings, deployment targets, server configuration, and security policies. The file supports TypeScript, JavaScript, and JSON formats with full IDE autocomplete.

Quick Start

Create frontmcp.config.ts in your project root:
The defineConfig() helper is a pass-through that enables IDE type hints and autocomplete.

File Resolution Order

FrontMCP searches for configuration files in this order:
  1. frontmcp.config.ts
  2. frontmcp.config.js
  3. frontmcp.config.json
  4. frontmcp.config.mjs
  5. frontmcp.config.cjs
  6. Fallback: derives minimal config from package.json (name, default node target)
When using JSON format, add "$schema" for autocomplete in VS Code and WebStorm:

Top-Level Fields

Deployment Targets

Each entry in deployments defines a build target with independent settings:

Deployment Target Fields

MCPB-Only Fields

The mcpb target supports additional fields for MCP Bundle metadata:

Server Configuration

HTTP Options

CSP Options

Security Headers

HA Configuration

Multi-Target Example

Deploy the same server to Node.js, distributed, and Vercel:
Build each target independently:

Helper Functions

Production Build

Build and deploy guide

High Availability

Multi-pod deployment with session failover

Security Headers

CSP and security header configuration

Runtime Modes

Standalone, distributed, and serverless modes