Library Generator

Generates a shared library for code reuse across apps. Supports four library types: generic, plugin, adapter, and tool-register.

Usage

nx g @frontmcp/nx:lib my-lib

Options

Option	Type	Default	Description
`name`	`string`	—	Required. The name of the library
`directory`	`string`	`libs/<name>`	The directory of the library
`libType`	`generic` \| `plugin` \| `adapter` \| `tool-register`	`generic`	The type of library to generate
`publishable`	`boolean`	`false`	Generate a publishable library with package.json
`importPath`	`string`	`<scope>/<name>`	The npm scope/import path. Defaults to the workspace’s npm scope (from the root `package.json` name, e.g. `@acme/source` → `@acme/<name>`), or the bare name when the workspace has no scope
`tags`	`string`	—	Comma-separated tags for the project

The generator refuses an import path that tsconfig.base.json already maps, by its exact key or a wildcard such as @acme/*, or one that names a package the workspace depends on (such as @frontmcp/sdk), so a new library never shadows existing code. Pass --importPath with another name.

Library Types

Generic (default)

A plain TypeScript library with a class and barrel export:

nx g @frontmcp/nx:lib shared-utils --libType generic

libs/shared-utils/src/
├── shared-utils.ts       # Sample class
├── shared-utils.spec.ts  # Starter spec
└── index.ts              # Barrel export

Plugin

A FrontMCP plugin library extending DynamicPlugin. The class is the one the plugin generator writes:

nx g @frontmcp/nx:lib my-plugin --libType plugin

libs/my-plugin/src/
├── my-plugin.plugin.ts       # @Plugin class
├── my-plugin.plugin.spec.ts  # Starter spec
└── index.ts

Adapter

A FrontMCP adapter library extending DynamicAdapter. The class is the one the adapter generator writes:

nx g @frontmcp/nx:lib my-adapter --libType adapter

libs/my-adapter/src/
├── my-adapter.adapter.ts       # @Adapter class
├── my-adapter.adapter.spec.ts  # Starter spec
└── index.ts

Tool Register

A multi-tool library that exports an array of tools:

nx g @frontmcp/nx:lib github-tools --libType tool-register

libs/github-tools/src/
├── github-tools.tools.ts       # Tool classes + exported array
├── github-tools.tools.spec.ts  # Starter spec
└── index.ts

Usage in an app, in a workspace whose root package.json is named @acme/source (the default import path is @acme/<name>; pass --importPath to override):

import { GithubToolsTools } from '@acme/github-tools';

@App({
  id: 'my-app',
  tools: [...GithubToolsTools, ...OtherTools],
})
class MyApp {}

Project Setup

Every library type gets the same project files:

File	Purpose
`project.json`	`test` runs the starter spec with `@frontmcp/nx:test`; `typecheck` runs `tsc --noEmit` on `tsconfig.lib.json` and `tsconfig.spec.json`
`tsconfig.json`	CommonJS with `moduleResolution` `node10` on TypeScript 5 and `bundler` on TypeScript 6+, decorators, and JavaScript output even when the base config is a TS-solution one (`composite`, `emitDeclarationOnly`)
`tsconfig.lib.json` / `.spec.json`	Sources and specs
`jest.config.cjs`	Maps the `tsconfig.base.json` path aliases so cross-project imports resolve in tests

The generator registers the import path in tsconfig.base.json as a relative path, "@frontmcp/my-lib": ["./libs/my-lib/src/index.ts"], which TypeScript accepts with or without a baseUrl. Apps import the library through that alias, and nx build <app> bundles it, so a library needs no build target of its own (a workspace that registers @nx/js/typescript still infers one from tsconfig.lib.json). A publishable library gets one, since it is built on its own.

tsconfig.json sets "nx": { "addTypecheckTarget": false } so that, in a workspace that registers the @nx/js/typescript plugin, Nx uses the project’s own typecheck target instead of inferring a tsc --build one.

Publishable Libraries

Generate a library with a package.json for npm publishing:

nx g @frontmcp/nx:lib my-plugin --libType plugin --publishable --importPath @my-org/plugin-cache

On top of the project files every library gets, a publishable library has:

File	Purpose
`project.json`	A cached `build` target that runs `tsc -p tsconfig.lib.json` in the library folder, writing JavaScript and declarations to `libs/my-plugin/dist`
`package.json`	Named after `--importPath`, with `main` / `types` set to `./dist/index.js` / `./dist/index.d.ts` and `files: ["dist"]`. It depends on `tslib` and, for the `plugin`, `adapter` and `tool-register` types, on `@frontmcp/sdk`, at the ranges the workspace `package.json` uses

Build the library, then publish it from its folder:

nx build my-plugin
npm publish libs/my-plugin --access public

Get Started

Generators

Executors

Usage

Options

Library Types

Generic (default)

Plugin

Adapter

Tool Register

Project Setup

Publishable Libraries

​Usage

​Options

​Library Types

​Generic (default)

​Plugin

​Adapter

​Tool Register

​Project Setup

​Publishable Libraries

Usage

Options

Library Types

Generic (default)

Plugin

Adapter

Tool Register

Project Setup

Publishable Libraries