Alimenter votre agent
Installation de l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
Pas encore de version packagée dans le registre. Suivez le README du dépôt.
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerA NestJS module to effortlessly expose tools, resources, and prompts for AI, from your NestJS applications using the Model Context Protocol (MCP).
With @rekog/mcp-nest you define tools, resources, and prompts in a way that's familiar in NestJS and leverage the full power of dependency injection to utilize your existing codebase in building complex enterprise ready MCP servers.
CustomTransportStrategy, so tools/resources/prompts are real @MessagePattern handlers — guards, pipes, interceptors, and exception filters apply to them nativelytransports arrayinitialize + sessions) and the stateless 2026-07-28 revision, concurrently — with no change to your tool code2026-07-28 — one handler serves both erasAre you interested to build ChatGPT widgets (with the OpenAI SDK) or MCP apps?
Find out how to do that with @rekog/MCP-Nest in this repository MCP-Nest-Samples
[!TIP] You can easily learn about this package using the
chattab in Context7. Better yet, connect the Context7 MCP server to allow your AI agents to access the documentation and implement MCP-Nest for you.
npm install @rekog/mcp-nest \
@modelcontextprotocol/server \
@modelcontextprotocol/core \
@modelcontextprotocol/node \
zod@^4
The built-in authorization server now lives in a separate package. If you use it, install it alongside @rekog/mcp-nest:
npm install @rekog/mcp-nest-auth
If you additionally use the TypeORM store for the authorization server, install the following optional peer dependencies as well:
npm install @nestjs/typeorm typeorm
MCP-Nest runs as a NestJS microservice transport strategy. Tools, resources,
and prompts live on @McpController() classes (so NestJS guards, pipes,
interceptors, and exception filters apply to them), and the strategy serves them
over one or more transports (Streamable HTTP, STDIO).
// greeting.controller.ts
import { McpController, Tool, McpContext } from '@rekog/mcp-nest';
import { Ctx, Payload } from '@nestjs/microservices';
import { z } from 'zod';
@McpController()
export class GreetingController {
@Tool({
name: 'greeting-tool',
description: 'Returns a greeting with progress updates',
parameters: z.object({ name: z.string().default('World') }),
})
async sayHello(
@Payload() { name }: { name: string },
@Ctx() ctx: McpContext,
) {
await ctx.reportProgress({ progress: 50, total: 100 });
return { content: [{ type: 'text', text: `Hello, ${name}!` }] };
}
}
// app.module.ts
import { Module } from '@nestjs/common';
import {
McpStrategy,
MCP_STRATEGY,
StreamableHttpTransport,
} from '@rekog/mcp-nest';
import { GreetingController } from './greeting.controller';
// The strategy is the whole configuration — there is no McpModule.
export const mcp = new McpStrategy({
name: 'my-mcp-server',
version: '1.0.0',
transports: [
new StreamableHttpTransport(),
],
});
@Module({
controllers: [GreetingController],
// Optional: only needed if a provider injects the strategy (e.g. for
// runtime/dynamic tool registration).
providers: [{ provide: MCP_STRATEGY, useValue: mcp }],
})
export class AppModule {}
// main.ts
import { NestFactory } from '@nestjs/core';
import { AppModule, mcp } from './app.module';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
mcp.setHttpAdapter(app.getHttpAdapter()); // needed for HTTP transports
app.connectMicroservice({ strategy: mcp });
await app.startAllMicroservices(); // mounts the MCP transports
await app.listen(3000); // also serves your normal HTTP routes
}
void bootstrap();
Order matters: call
startAllMicroservices()beforelisten()so the MCP HTTP routes are mounted before the server starts accepting connections.
That /mcp endpoint is dual-era: it answers both the 2025-era protocol
(initialize handshake + sessions) and the stateless 2026-07-28 revision,
concurrently, from the same @Tool methods. ctx.reportProgress(...) above
reaches a 2026-07-28 client as-is — every modern request can stream progress
back even though it is sessionless. A 2025-era client needs a session-aware
transport for it (new StreamableHttpTransport({ statefulMode: true }) or
StdioTransport); on the legacy stateless default it is a no-op. See
Protocol Revisions.
For an STDIO-only server, skip the HTTP adapter and use
NestFactory.createMicroservice(AppModule, { strategy: mcp }) with
transports: [new StdioTransport()] and disable logging (stdout is reserved for
the protocol).
McpModule.forRoot(options) to McpStrategy + @McpController2026-07-28 from one endpointThe examples directory contains working examples for all features.
Refer to examples/README.md for details.
A NestJS module to effortlessly create Model Context Protocol (MCP) servers for exposing AI tools, resources, and prompts.
Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
MCP Nest s'exécute en local via stdio.
Dernière vérification : 2026-10-28. A NestJS module to effortlessly create Model Context Protocol (MCP) servers for exposing AI tools, resources, and prompts.