Overview

Servercn is an MIT-licensed backend component registry for Node.js and TypeScript, built by Akkal Dhami and contributors. It applies the shadcn/ui approach to the server: instead of UI components, its CLI copies backend modules such as OAuth, file upload, rate limiting, logging and email into a project as source, with no runtime dependency or lock-in.

The registry is split into 29+ components, 11+ foundations (starter projects), 4 blueprints (feature modules), 7 database providers and 4 schemas. Express.js has full support, Next.js App Router backends are supported, and NestJS support is in progress. Projects start with npx servercn-cli init, and modules are added incrementally with npx servercn-cli@latest add [component-name].

Features

Backend components: API error and response handlers, JWT utilities, auth middleware, role-based access control, rate limiter, security headers, structured logger, Swagger docs and Zod request validation.
Auth and OAuth: Google, GitHub and combined OAuth, password hashing, token and OTP utilities.
Integrations: Email via Nodemailer, Resend or Mailtrap, file uploads to Cloudinary or ImageKit, and node-cron background jobs.
Foundations: Express starters with Mongoose, Prisma (MongoDB, MySQL) and Drizzle (MySQL, PostgreSQL, Neon), plus stateful, stateless and hybrid auth starters.
Blueprints: Hybrid, stateful and stateless authentication modules and a banking application.
Schemas: Models for authentication, a banking app, a blog and a todo app.
Non-destructive installs: Existing files are respected and only missing pieces are added.

Tech stack

Node.js, TypeScript
Express.js, Next.js (NestJS in progress)
MongoDB, PostgreSQL, MySQL via Mongoose, Prisma or Drizzle
Zod