@nestjs-mcp/server weekly downloads statistics

MCP Server NestJS Module Library <!-- omit in toc -->

---

Overview <!-- omit in toc -->

NestJS MCP Server is a modular library for building Model Context Protocol (MCP) servers using NestJS. It provides decorators, modules, and integration patterns to expose MCP resources, tools, and prompts in a scalable, maintainable way. This project is a wrapper for the official @modelcontextprotocol/sdk and is always kept compatible with its types and specification.

---

Table of Contents <!-- omit in toc -->

• Installation
• Quickstart
• What is MCP?
• Core Concepts
  • Server
  • Resource
  • Tool
  • Prompt
• Module API
  • McpModule.forRoot
  • McpModule.forRootAsync
  • McpModule.forFeature
• Module Usage
  • 1. Global Registration with McpModule.forRoot
  • 2. Feature Module Registration with McpModule.forFeature
• Capabilities
  • Resolver Decorator
  • Prompt Decorator
  • Resource Decorator
  • Tool Decorator
    • Tool Annotations
    • ToolOptions Variants
  • McpContext Argument
• Dynamic Capabilities
  • Static toggle
  • Capability gate
  • What the client sees
  • Fail-closed, in five cases
  • Rules you must know before using this
  • This is not a replacement for guards
• Guards
  • Global-level guards
  • Resolver-level guards
  • Method-level guards
  • Guard Example
  • MCP Execution Context
  • Guards with Dependency Injection
• Statelessness
• Transport Options
• MCP 2026-07-28 features
• Migrating from 1.x to 2.x
• Inspector Playground
• Examples
• Changelog
• License
• Contributions

---

Installation

npm install @nestjs-mcp/server @modelcontextprotocol/sdk zod
# or
yarn add @nestjs-mcp/server @modelcontextprotocol/sdk zod
# or
pnpm add @nestjs-mcp/server @modelcontextprotocol/sdk zod

---

Quickstart

Register the MCP module in your NestJS app and expose a simple tool:

import { Module } from '@nestjs/common';

import { CallToolResult } from '@modelcontextprotocol/sdk/types';

import { Resolver, Tool, McpModule } from '@nestjs-mcp/server';

@Resolver()
export class HealthResolver {
  /**
   * Simple health check tool
   */
  @Tool({ name: 'server_health_check' })
  healthCheck(): CallToolResult {
    return {
      content: [
        {
          type: 'text',
          text: 'Server is operational. All systems running normally.',
        },
      ],
    };
  }
}

@Module({
  imports: [
    McpModule.forRoot({
      name: 'My MCP Server',
      version: '1.0.0',
    }),
  ],
  providers: [HealthResolver],
})
export class AppModule {}

---

What is MCP?

The Model Context Protocol (MCP) is an open protocol for connecting LLMs to external data, tools, and prompts. MCP servers expose resources (data), tools (actions), and prompts (conversational flows) in a standardized way, enabling seamless integration with LLM-powered clients.

• See the Anthropic announcement for more background.

---

Core Concepts

Server

The MCP Server is the main entry point for exposing capabilities to LLMs. It manages the registration and discovery of resources, tools, and prompts.

Resource

A Resource represents structured data or documents that can be queried or retrieved by LLMs. Resources are typically read-only and are identified by a unique URI.

• Learn more: MCP Resources documentation

Tool…