Prerequisites
- Node.js:
- Minimum: Version 22 (LTS Maintenance)
- Recommended: Version 24 (Active LTS)
- FrontMCP is developed and tested on Node.js 24
- npm ≥ 10 (pnpm / yarn work too)
- TypeScript project (the init command can set this up)
Option A — Create a new project
Use the built-in project generator. It will create a new folder under your current directory.create command is interactive by default:
--yes (or -y) to skip prompts and use defaults.
CLI Flags
| Flag | Description | Default |
|---|---|---|
--yes, -y | Use defaults (non-interactive) | - |
--target <type> | Deployment: node, vercel, lambda, cloudflare | node |
--redis <setup> | Redis: docker, existing, none | docker |
--cicd / --no-cicd | Enable GitHub Actions | --cicd |
- scaffold a FrontMCP project in
./my-app - configure
tsconfig.jsonfor decorators and modern ESM - generate a
package.jsonwith helpful scripts - create deployment configuration for your target (Dockerfile, vercel.json, etc.)
- generate GitHub Actions workflows (if enabled)
- install required dev dependencies (e.g. TypeScript, tsx, zod, reflect-metadata)
Option B — Add to an existing project
Install the CLI and Node types (FrontMCP bundles compatible@frontmcp/sdk internally—no separate install needed).
init will:
- add/update scripts in your
package.json - ensure your tsconfig.json includes required compiler options
- verify a sensible project layout
Package scripts
Aftercreate or init, you’ll have these scripts:
frontmcp dev— run your server in watch mode (tsx)frontmcp build— compile your entry with TypeScript (outputs to./distby default)frontmcp inspector— launch the MCP Inspector (npx @modelcontextprotocol/inspector)frontmcp doctor— validate Node/npm versions, tsconfig, and project setup
Verify your setup
Run:If anything is missing or misconfigured (Node/npm versions,
tsconfig.json, scripts), doctor will tell you
exactly what to fix.Next steps
- Start developing:
npm run dev - Build for distribution:
npm run build - Explore tools and messages live:
npm run inspect

