App Generator

Generates a FrontMCP application with an entry point, app class, sample tool, and full project configuration.

Usage

nx g @frontmcp/nx:app my-app

Options

Option	Type	Default	Description
`name`	`string`	—	Required. The name of the application
`directory`	`string`	`apps/<name>`	The directory of the application
`tags`	`string`	—	Comma-separated tags for the project

Generated Files

apps/my-app/
├── src/
│   ├── main.ts               # Server entry point
│   ├── my-app.app.ts         # @App class
│   └── tools/
│       ├── hello.tool.ts     # Sample @Tool
│       └── hello.tool.spec.ts # Starter spec, so `nx test` has a test to run
├── project.json               # Nx project config with targets
├── package.json               # Minimal manifest so `frontmcp build` runs in the project root
├── tsconfig.json
├── tsconfig.lib.json
├── tsconfig.spec.json
└── jest.config.cjs            # swc transform, @frontmcp/testing setup, tsconfig path aliases

Generated Code

src/my-app.app.ts

import { App } from '@frontmcp/sdk';
import HelloTool from './tools/hello.tool';

@App({
  id: 'my-app',
  name: 'MyApp',
  tools: [HelloTool],
})
export class MyAppApp {}

src/main.ts

import 'reflect-metadata';
import { FrontMcp } from '@frontmcp/sdk';
import { MyAppApp } from './my-app.app';

@FrontMcp({
  info: { name: 'MyApp', version: '0.1.0' },
  apps: [MyAppApp],
})
export default class Server {}

src/tools/hello.tool.spec.ts

import HelloTool from './hello.tool';

describe('HelloTool', () => {
  it('greets the caller by name', async () => {
    // execute() holds the tool's logic; build the tool without the request context the server injects.
    const tool: HelloTool = Object.create(HelloTool.prototype);

    await expect(tool.execute({ name: 'Ada' })).resolves.toEqual({ message: 'Hello, Ada!' });
  });
});

Nx Targets

The generated project.json includes these targets:

Target	Executor	Description
`build`	`@frontmcp/nx:build`	Compile to dist/
`dev`	`@frontmcp/nx:dev`	Development mode with watch
`serve`	`@frontmcp/nx:serve`	Run application server
`test`	`@frontmcp/nx:test`	Run Jest tests
`typecheck`	`nx:run-commands`	`tsc --noEmit` on `tsconfig.lib.json` and `tsconfig.spec.json`
`inspector`	`@frontmcp/nx:inspector`	Launch MCP Inspector

TypeScript Configuration

tsconfig.json is what frontmcp build compiles, so it sets what a FrontMCP build needs regardless of the workspace’s base config:

module: commonjs, with moduleResolution: node10 on TypeScript 5 and bundler on TypeScript 6+ (which deprecates node10). Under node10, an inherited customConditions is reset to null.
rootDir at the workspace root, so code imported from libraries compiles too.
composite, declarationMap and emitDeclarationOnly set to false, so a TS-solution base config (create-nx-workspace --preset=ts) still emits JavaScript.
"nx": { "addTypecheckTarget": false }, so a workspace that registers @nx/js/typescript uses the typecheck target above instead of an inferred tsc --build.

Example

# Create app with tags
nx g @frontmcp/nx:app analytics --tags "scope:analytics,type:app"

# Start development
nx dev analytics

Get Started

Generators

Executors

Usage

Options

Generated Files

Generated Code

Nx Targets

TypeScript Configuration

Example

​Usage

​Options

​Generated Files

​Generated Code

​Nx Targets

​TypeScript Configuration

​Example

Usage

Options

Generated Files

Generated Code

Nx Targets

TypeScript Configuration

Example