NestJS MCP Server Module

What is NestJS MCP Server Module?

A NestJS module that exposes tools, resources, and prompts for AI from your NestJS applications using the Model Context Protocol (MCP). It lets you define MCP components in a NestJS-native way with full dependency injection support.

How to use NestJS MCP Server Module?

Install the package and its peer dependencies via npm, import McpModule.forRoot() in your NestJS module, then define tools using the @Tool decorator with Zod-based parameter validation and automatic discovery.

Features of NestJS MCP Server Module

• Expose NestJS methods as MCP tools with automatic discovery and Zod validation
• Multi-transport support: HTTP+SSE, Streamable HTTP, and STDIO
• Serve static and dynamic content through MCP resource and resource template systems
• Define reusable prompt templates for AI interactions
• Guard-based authentication with OAuth and built-in or external authorization servers
• Interactive tool calls with user input elicitation and full HTTP request access

Use cases of NestJS MCP Server Module

• Build enterprise-ready MCP servers from existing NestJS codebases
• Expose NestJS service methods as AI-callable tools with automatic validation
• Serve static or parameterized resources (e.g., files, API data) through MCP
• Define reusable prompt templates for consistent AI interactions

FAQ from NestJS MCP Server Module

What dependencies are required?

@rekog/mcp-nest, @modelcontextprotocol/sdk, and zod@^4. For the built-in authorization server with a database store, also install @nestjs/typeorm and typeorm.

What transport protocols are supported?

HTTP+SSE, Streamable HTTP, and STDIO. Server examples for each are provided in the documentation.

How does authentication work?

The module provides guard-based authentication with OAuth support, using either a built-in authorization server (beta) or an external authorization server like Keycloak or Auth0.

Where can I find examples and documentation?

Full guides are in the docs/ directory, and working examples live in the playground/ directory of the repository.