MCP-Nest

Why we included this project

For teams already building backend services in NestJS, this module is the shortest route to a production-grade MCP server without learning a second framework. It runs MCP as a NestJS microservice transport strategy, so the tools, resources, and prompts you expose are just your existing handlers, and the guards, pipes, interceptors, and exception filters you already rely on apply to AI calls the same way they do to HTTP requests. Your dependency-injected services and authorization logic carry over instead of being reimplemented for a standalone server. The module also handles the awkward protocol details, serving both the session-based and stateless protocol revisions from a single endpoint and supporting streamable HTTP and STDIO transports. If you need per-tool authorization, OAuth-backed security, or interactive tool calls that prompt the user for input, those are built in rather than added on.