NestJS MCP Integration

Reusing your Types and Guards

Writing a custom MCP server usually means abandoning your carefully crafted NestJS guards, interceptors, and DTO validations. You end up maintaining two separate APIs.

By using @nestjs/swagger, the types you already wrote compile perfectly to OpenAPI. wmcp.sh reads that spec, converting it directly into Claude or LangChain tool-use schemas while relying on your actual Nest server to process the traffic safely.

Extracting MCP tools from Nest

// TypeScript - NestJS Controller
import { Controller, Post, Body, UseGuards } from '@nestjs/common';
import { ApiTags, ApiOperation, ApiBearerAuth } from '@nestjs/swagger';

@ApiTags('agent')
@Controller('tasks')
export class TaskController {
  
  @Post()
  @UseGuards(JwtAuthGuard)
  @ApiBearerAuth()
  @ApiOperation({ summary: 'Create new task' })
  create(@Body() createTaskDto: CreateTaskDto) {
    return this.taskService.create(createTaskDto);
  }
}

// Agents will now prompt: "Create new task" mapping precisely to CreateTaskDto
curl -X GET "https://wmcp.sh/api/v1/tools?url=https://your-nest-app.com/api-json&tag=agent"

Feature translation via OpenAPI

Common questions.