Nest MCP Server

Expose NestJS methods, resources, and prompts as MCP tools using dependency injection.

Data last scanned yesterday · Reviewed 3 weeks ago

557 tools★ 694TypeScriptMIT

Overview

The Nest MCP Server provides a framework for integrating NestJS applications with the Model Context Protocol. By functioning as a CustomTransportStrategy, it allows developers to treat tools, resources, and prompts as standard NestJS message patterns, enabling the use of existing guards, pipes, interceptors, and exception filters. The server supports both HTTP and STDIO transports and offers concurrent support for multiple protocol versions. It includes features for interactive tool elicitation, per-tool authorization, and dependency injection, allowing for deep integration with your current application architecture.

Our verdict

This server carries a high risk level with a security score of 55/100. A primary concern is the lack of a read-only mode, as every installation defaults to full write access, which could pose risks if not strictly configured. Given that it is community-maintained rather than official, users should carefully audit their authorization guards and per-tool permissions before deployment.

Native support for NestJS guards, pipes, and interceptors
Dependency injection integration throughout all MCP components
Supports both STDIO and streamable HTTP transports
Zero direct dependencies reduce the supply-chain surface

No read-only mode by default
Community-maintained project lacks official vendor support
Currently missing a defined homepage link

Setup

Claude Desktop

{
  "mcpServers": {
    "mcp-nest": {
      "args": [
        "-y",
        "mcp-nest-workspace"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
greet-user	Returns a personalized greeting in the user's preferred language	low
inspect-request	Reads the parsed JSON-RPC request	low
log-demo	Emits log messages while running	low
greet-user-meta	Greeting whose definition carries extra metadata	low
process-data	Processes data with progress updates	medium
greet-user-structured	Returns a structured greeting with metadata	low
greet-user-interactive	Interactive greeting with language selection	medium

Compatibility

Client	Local	Docker	Remote	Read-only
ChatGPT
Claude Desktop
Cursor
VS Code
Windsurf

Frequently asked questions

›Does this MCP server support standard NestJS features?

Yes, because it runs as a NestJS microservice transport strategy, tools and resources act as MessagePattern handlers that support standard NestJS guards, pipes, interceptors, and exception filters.

›Can I use multiple transport types simultaneously?

Yes, you can configure the MCP server to support both streamable HTTP and STDIO by including them in the transports array within your McpStrategy configuration.

›What authentication options are available?

The server supports guard-based security, OAuth, and both built-in and external authorization servers like Keycloak or Auth0.

›Are there specific dependency requirements for the authorization features?

Yes, the built-in authorization server requires the separate @rekog/mcp-nest-auth package, and if you use the TypeORM store, you must also install @nestjs/typeorm and typeorm.

›Does the server require specific MCP protocol versions?

The server concurrently supports the 2025-era protocol with session handling and the stateless 2026-07-28 protocol revision without requiring changes to your tool code.