# NestRS > Scalable Rust backend apps with native performance. - **Type:** MCP server - **Install:** `agentstack add mcp-yv17labs-nestrs` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [YV17labs](https://agentstack.voostack.com/s/yv17labs) - **Installs:** 0 - **Category:** [Databases](https://agentstack.voostack.com/c/databases) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [YV17labs](https://github.com/YV17labs) - **Source:** https://github.com/YV17labs/NestRS - **Website:** http://nestrs.dev ## Install ```sh agentstack add mcp-yv17labs-nestrs ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About Scalable Rust backend apps with native performance. ## What it is You write business logic; the framework carries the rest — authn, authz, row-level tenant filtering, per-field masking, transactions, discovery, and lifecycle. Those concerns are transparent to your code and verified at boot, not left to review discipline. A full authenticated, tenant-scoped, transactional, field-masked CRUD resource is an empty `impl` block: ```rust #[controller(path = "/orgs")] #[use_guards(AuthGuard, AuthzGuard)] pub struct OrgsController { #[inject] svc: Arc, } #[crud(service = svc, entity = OrgEntity, output = Org, create = CreateOrg, update = UpdateOrg)] impl OrgsController {} ``` The differentiator is **structural multi-tenant isolation you cannot forget**: row-level filtering, response masking, and transactions become non-optional the moment the security modules are imported. A feature opts *out* by not importing them. In NestJS, Spring, Rails, axum, or Loco, tenant filtering is discipline — a scope you remember, a middleware you apply, a review comment. In NestRS it is structural: the data layer applies it from the caller's ability, and an operation with no declared access posture is refused — at compile time on GraphQL, at boot on HTTP. And it stays lean. On the same hello-world service under identical `wrk` load, NestRS serves **~463k req/s** to NestJS 11's ~18k — **~25×** — in **4–6 MB** of RAM against ~80–120 MB. Our own measurements of the demo API — the full JWT + authz + row-level + masking pipeline, Postgres included — still land around **23k req/s**, **p99 Prefer a local toolchain? See [Getting started → Scaffold and start](https://nestrs.dev/getting-started/#scaffold-and-start). ### Project layout **Two Cargo workspaces**, split along the framework/product line. ``` nestrs/ ├─ crates/ the framework — one nest-rs-* crate per capability │ ├─ nest-rs-core/ IoC container, modules, DI, bootstrap │ ├─ nest-rs-http/ REST controllers & routing │ └─ … (members = ["crates/*"]) ├─ docs/ the nestrs.dev site (Astro Starlight) └─ demo/ the product — its own workspace, consumes the framework ├─ apps/ one runnable binary each (the Publish workspace) │ ├─ auth/ OAuth2 / JWT token issuer │ ├─ api/ REST + GraphQL + OpenAPI, persisted & authorized │ ├─ assistant/ Model Context Protocol server │ ├─ live/ real-time WebSocket gateway │ └─ worker/ background jobs & scheduling (headless) ├─ crates/ │ ├─ features/ product features — port + adapters (users, posts, authn, …) │ ├─ migrations/ shared-database SeaORM migrations (CLI) │ └─ seed/ shared-database demo data (CLI) ├─ Justfile, db.just, test.just, .env*, Dockerfile └─ (members = ["apps/*", "crates/*"]) ``` The **`demo/`** workspace references the framework by relative path (`nest-rs-* = { path = "../crates/nest-rs-*" }`), so it builds against the live framework source. You `cd demo` and drive it as if it were the app's own repository — see [`demo/README.md`](demo/README.md) for running the apps, the command table, the Publish map, and Docker. - **`crates/nest-rs-*/`** — the framework: generic, product-agnostic building blocks. - **`demo/apps//`** — `main.rs` + `module.rs` listing the edge modules the binary serves. - **`demo/crates/features/`** — the product's vertical slices; apps import the edges they serve. Adding an app means a directory under `demo/apps/`; a new feature means a folder under `demo/crates/features/src/`; a new framework capability means a `nest-rs-*` crate under `crates/`. Simple **hello**/**blog** layouts are CLI-scaffolded only — see [Getting started](https://nestrs.dev/getting-started/) and the [tutorial](https://nestrs.dev/tutorial/); they are not checked into this repo. ### Running the apps Everything runnable lives in [`demo/`](demo/) — `cd demo` first, then `nestrs run` (no args lists every recipe). The full command table, the Publish app map, and the Docker build are documented in [`demo/README.md`](demo/README.md). ## Community & contributing NestRS is young, and early contributors shape what it becomes — you don't have to write Rust to help. - 💬 **Ask a question, propose an idea, or just say hi** in [Discussions](https://github.com/YV17labs/NestRS/discussions). - 🐛 **Report a bug or request a feature** through [issues](https://github.com/YV17labs/NestRS/issues/new/choose). - 🌱 **Pick up a** [`good first issue`](https://github.com/YV17labs/NestRS/labels/good%20first%20issue) — [CONTRIBUTING.md](CONTRIBUTING.md) is the short path from idea to merged PR. - 🗺️ **See where it's heading** in the [roadmap](ROADMAP.md). - 🔒 **Found a vulnerability?** Follow [SECURITY.md](SECURITY.md) — please don't open a public issue for it. If NestRS resonates, a ⭐ helps others find it and tells us the direction is worth pushing. ## License MIT — see [LICENSE](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:** [YV17labs](https://github.com/YV17labs) - **Source:** [YV17labs/NestRS](https://github.com/YV17labs/NestRS) - **License:** MIT - **Homepage:** http://nestrs.dev Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** yes - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** yes - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/mcp-yv17labs-nestrs - Seller: https://agentstack.voostack.com/s/yv17labs - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.