Chassis

chassis-mcp

An MCP server that scaffolds Chassis backends — a decorator-driven Express 5 + TypeScript starter with an optional database, auth provider and Next.js front end.

It lets an agent go from "build me an API with Postgres and auth" to a project that already typechecks, lints and tests green, without knowing the CLI's flags.

Install

Point your MCP client at the package. No global install needed:

{  "mcpServers": {    "chassis": {      "command": "npx",      "args": ["-y", "chassis-mcp"]    }  }}

Tools

The option list is imported from create-chassis, not restated here, so this server can't advertise a stack the CLI doesn't support. An unsupported value is rejected with the list of valid ones before the CLI runs.

Example

Build me an API with Postgres, JWT auth and a Next.js front end, in ./shop

list_chassis_options       → sees `fullstack`, and that web=true implies a monorepocreate_chassis_project     → { directory: "./shop", preset: "fullstack" }                           ← { monorepo: true, apiRoot: "apps/api", nextSteps: [...] }chassis_conventions        → reads ./shop/AGENTS.md before writing any code

What lands is a workspaces monorepo with apps/api and apps/web, auth wired on both sides, and only the modules that were chosen — declined ones are removed from the source and from package.json.

Notes

• Nothing is overwritten. A non-empty target directory is refused.
• install defaults to false because it's slow; run npm install yourself, or pass install: true.
• Creating a project downloads the template from GitHub, so it needs network access.
• This is not the MCP server inside a generated project (npm run mcp), which exposes that project's API as tools. This one creates projects.

MIT · source · docs