Install
$ agentstack add mcp-dvd90-chassis ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
🏎️ Chassis
A lightweight, decorator-driven Express + TypeScript backend starter. Clone, run, ship.
📖 Documentation · Getting started · create-chassis on npm
Chassis gives you NestJS-style controller ergonomics on plain Express 5 — in a handful of small files you can actually read. Zero configuration required: the server boots standalone, and every integration switches on only when you add its environment variable. Scaffold with a preset or pick à la carte — a database (Mongo, Postgres, or SQLite, ORM included), an auth provider (Auth0, JWT, or Clerk), an optional Next.js front end, Sentry, an MCP server, and x402 payments — and the CLI ships only what you chose.
export class UserController extends Routable {
constructor() {
super('/users');
}
@route('get', '/:id')
async show(req: Request) {
const user = await findUser(req.params.id);
if (!user) throw new AppError(ERROR_CODES.NOT_FOUND, 'User not found');
return req.resHandler.ok(user);
}
@protectedRoute('post', '/', [validate({ body: createUserSchema })])
async create(req: Request) {
return req.resHandler.created(await createUser(req.body));
}
}
Export the class from src/controllers/index.ts — that's the whole wiring.
Quick start
npm create chassis my-api -- --yes # zero prompts: Postgres + JWT + Sentry + Docker
npm create chassis my-app -- --preset fullstack --yes # the same, plus a Next.js front end
npm create chassis my-api # interactive — pick a preset
npm create chassis my-api -- --db postgres --auth jwt --mcp # à la carte
npm create chassis my-api -- --bare # nothing — standalone build
Or use the template directly:
git clone https://github.com/dvd90/chassis.git my-api
cd my-api && npm install && npm run dev
That's it — no database, no env file, no accounts needed. Open http://localhost:8000/status.
New here? Follow the [step-by-step getting-started guide](docs/getting-started.md) — zero to a tested API in ~10 minutes.
For AI agents
Every path is non-interactive: --yes and --bare never prompt, and the CLI skips prompts automatically whenever stdin isn't a TTY. One command produces a project that already typechecks, lints and tests green.
- llms.txt — the project, its
conventions and its docs index, in one fetch
- llms-full.txt — every
documentation page, concatenated
- [AGENTS.md](AGENTS.md) — the conventions to follow when writing code in a
Chassis project, and the definition of done
Generated projects carry AGENTS.md, CLAUDE.md, llms.txt and an add-resource skill, so whichever agent opens one writes code that matches the rest of the codebase rather than fighting it.
Features
- TypeScript 5 + Express 5 — strict types, async errors caught automatically
- Decorator routing —
@route/@protectedRouteon controller methods, controllers auto-mount - Consistent responses —
req.resHandler.ok() / .notFound() / .validation()with structured logging - Request correlation — every request gets a
callId(or propagatesx-call-id), echoed in responses and logs - Typed, validated config — zod-checked environment via
src/config; the app refuses to boot on bad config - Zod input validation —
validate({ body, query, params })middleware with structured 400s - Pick-your-stack scaffolder — presets or à la carte: database + ORM (Mongo/Postgres/SQLite), auth (Auth0/JWT/Clerk), a Next.js front end, Sentry, MCP, x402 — the CLI prunes everything else so
package.jsoncarries only what you chose - Opt-in integrations — every module enables by env var, never required
- Payment-gated routes —
@paidRoute('get', '/report', '$0.01')via the x402 protocol (opt-in) - Optional Next.js front end —
--webadds an App Router app and makes the project an npm-workspaces monorepo (apps/api+apps/web); the auth provider you picked is wired on both sides - MCP server — expose your API to AI agents as MCP tools (
npm run mcp, opt-in) - Health endpoints —
/healthz(liveness) and/readyz(readiness, checks enabled integrations) - Graceful shutdown — drains connections and closes integrations on SIGTERM/SIGINT
- Vitest + supertest — fast tests against the pure app factory, no server or DB needed
- DB-aware code generator —
npm run gen userscaffolds a controller + test wired to your ORM (Drizzle or Mongoose) - Production Docker — multi-stage build, non-root user, plus docker-compose with your database for dev
- CI + Renovate — GitHub Actions verify pipeline and automated dependency updates
- AI-agent ready — ships
AGENTS.md,CLAUDE.md,llms.txt, and anadd-resourceskill so agents write code that matches the conventions (see below)
AI-agent ready
Most people scaffolding a backend today have an AI agent in the loop. Chassis is built so that agent-written code reads like hand-written code — because the framework gives agents rails and a verifiable finish line:
AGENTS.md+CLAUDE.mdship in every project — Claude Code, Cursor, Copilot, and Codex pick them up automatically and follow the conventions (thin controllers,resHandlerresponses,throw AppError, config in one place).- One obvious place for everything means agent output converges on the same shape a maintainer would write — that's what keeps it readable.
npm run verify(strict TypeScript + ESLint + tests) is a deterministic quality gate agents iterate against until green..claude/skills/add-resourceturns "add a books resource" into one consistent, checklisted operation.llms.txtgives doc-fetching tools a compact map of the conventions.
Nothing to install — it's all in the scaffold. See [AGENTS.md](AGENTS.md).
Scripts
| Command | What it does | | --------------------------------- | ------------------------------------------- | | npm run dev | Start with hot reload (tsx watch) | | npm test / npm run test:watch | Run the vitest suite | | npm run verify | Typecheck + lint + test (CI runs this) | | npm run build / npm start | Compile to dist/ and run production build | | npm run gen | Generate a controller + test | | npm run lint / npm run format | ESLint / Prettier |
Enabling integrations
Copy .env.example to .env. Each integration turns on when its variables are set — and stays completely dormant otherwise:
| Integration | Enable by setting | What you get | | ----------- | --------------------------------- | --------------------------------------------------------- | | MongoDB | MONGODB_URI | Mongoose connection, readiness check, graceful disconnect | | Auth0 | AUTH0_DOMAIN + AUTH0_AUDIENCE | JWT verification on every @protectedRoute | | Sentry | SENTRY_DSN | Automatic error reporting from the central error handler |
Using a different IdP? Call setAuthProvider([...yourMiddleware]) at boot and @protectedRoute uses it — see src/core/auth.ts.
Project structure
src/
├── config/ # zod-validated env → typed config + feature flags
├── core/ # the framework: Routable, decorators, responses, errors, validation
├── middleware/ # callId correlation, dev request logging
├── integrations/ # opt-in modules: mongo, auth0, sentry
├── controllers/ # your endpoints — exported classes auto-mount
├── __tests__/ # vitest + supertest
├── app.ts # pure app factory (no I/O — trivially testable)
└── server.ts # boot: integrations → listen → graceful shutdown
Documentation
Read them at dvd90.github.io/chassis — searchable, one page. The source lives in [docs/](docs/README.md) and the site is generated from it, so the two can never disagree:
- [Getting started](docs/getting-started.md) — step-by-step tutorial
- Guides — [building an API](docs/guides/building-an-api.md) · [authentication](docs/guides/authentication.md) · [deployment](docs/guides/deployment.md)
- Concepts — [architecture](docs/architecture.md) · [modules & integrations](docs/modules.md)
- Reference — [configuration](docs/reference/configuration.md) · [core API](docs/reference/core-api.md) · [CLI & scripts](docs/reference/cli.md)
- [Maintainers guide](docs/maintainers.md) — publishing, releases, keeping the template fresh
Docker
docker compose up --build # API + MongoDB
docker build -t my-api . # production image only
License
[MIT](LICENSE)
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dvd90
- Source: dvd90/chassis
- License: MIT
- Homepage: https://dvd90.github.io/chassis/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.