OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

MCP Nest

MCP Nest is a TypeScript library that provides a NestJS microservice transport strategy for building Model Context Protocol servers. It lets developers expose NestJS methods as AI tools and publish application data and reusable prompts, using NestJS dependency injection and existing application code.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

MCP Nest — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use MCP Nest when an existing or planned NestJS backend needs to provide application operations, data or prompt templates to MCP clients. It is particularly relevant when developers want to reuse dependency-injected services and NestJS request-processing features in MCP handlers.

Who it is for

  • TypeScript developers building NestJS applications.
  • Teams connecting existing NestJS services or data to MCP-compatible AI clients.
  • Developers who want MCP handlers to use NestJS guards, pipes, interceptors and exception filters.

Documented uses

  • Expose selected NestJS methods as MCP tools with discovered handlers and Zod parameter validation.
  • Serve application content and data as MCP resources, including parameterized resource templates.
  • Define reusable prompts for AI interactions within a NestJS application.
  • Connect dependency-injected application services to MCP handlers.
  • Choose Streamable HTTP or STDIO as the server transport.
Before you choose

Requirements & limits

The repository is public and identifies the project as MIT-licensed. The documented installation uses npm.

  • Requires a NestJS application and TypeScript development; it is a library, not a hosted server or an end-user AI app.
  • The README documents Streamable HTTP and STDIO transports, so transport choice depends on the intended MCP client setup.
  • Tool parameters can use Zod validation, and handlers can use NestJS guards, pipes, interceptors and exception filters.
  • The built-in authorization server is supplied as a separate package and is labeled beta.
  • The README lists additional optional TypeORM dependencies when using the authorization server's TypeORM store.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up a NestJS MCP server with a greeting tool over Streamable HTTP

Install MCP-Nest, define a greeting tool, configure the HTTP transport, and start the NestJS microservice.

Before you start

  • A NestJS application.
  • The packages @rekog/mcp-nest, @modelcontextprotocol/server, @modelcontextprotocol/core, @modelcontextprotocol/node, and zod@^4.

Steps

  1. Install the listed packages with npm.

  2. Create an @McpController() class with a @Tool() method; define its parameters with a Zod schema and return MCP content from the handler.

  3. Create an McpStrategy configured with a StreamableHttpTransport and register the controller in the NestJS module.

  4. In the bootstrap function, create the Nest application, set the strategy's HTTP adapter, connect the microservice, call startAllMicroservices(), and then call listen().

Expected outcome

A NestJS application starts its MCP transport with the documented greeting tool and mounts the MCP HTTP routes before accepting connections.

Guide limitations

  • The documented bootstrap order is required: startAllMicroservices() must run before listen() so MCP HTTP routes are mounted first.
  • This recipe documents setup and server startup, not a client connection or successful tool invocation.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
rekog-labs/MCP-Nest · Official homepage title · retained in its source language
How we review sourcesSuggest a correction