
Chassis
io.github.dvd90Published by GitHub account dvd90v0.1.2Updated Oct 24, 2026
Scaffold an Express 5 + TypeScript backend: database, auth, optional Next.js front end.
Overview
Chassis scaffolds Express 5 + TypeScript backends, letting an assistant create a typed, linted project with a chosen database, auth provider and optional Next.
- What you can do
- List the available presets, databases, auth providers and add-ons, validated against the underlying CLI's supported options before anything runs. Scaffold a new backend project into a new or empty directory and report its layout, API root and next commands. Read the generated project's coding conventions for controllers, responses, errors, validation and definition of done. Optionally produce a fullstack workspaces monorepo with an API and Next.js front end, auth wired on both sides and declined modules removed.
- When to use it
- Use it when you want an assistant to go from a stack description such as an API with Postgres and auth to a project that already typechecks, lints and tests green, without knowing the CLI's flags. It is for starting new projects, not for working with an existing codebase.
- Requirements
- Runs as a local stdio process, typically launched with npx, so Node.js and npm are needed. Network access is required because project creation downloads the template from GitHub. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Chassis in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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:
Where that file lives
- Claude Desktop —
claude_desktop_config.json - Claude Code —
claude mcp add chassis -- npx -y chassis-mcp - Cursor —
.cursor/mcp.json - VS Code —
.vscode/mcp.json
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
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.
installdefaults tofalsebecause it's slow; runnpm installyourself, or passinstall: 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.
Source: mcp-server/README.md at commit fae8662
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts