Nestjs Api To Postman Collection
LocalAbout Nestjs Api To Postman Collection
Nestjs Api To Postman Collection is an MCP tool and CLI for NestJS developers who need Postman collections from existing controllers. It derives routes, types, request details, and authentication configuration from code without requiring documentation annotations.
Key features
- 01Generate Postman collections from controllers
- 02Detect request and response types
- 03Include authentication configuration
- 04Capture routes, methods, and parameters
- 05Run through MCP or CLI
Use cases
- 01Create a Postman collection for a NestJS API
- 02Refresh collections after endpoint changes
- 03Generate API examples without adding decorators
MCP support
It exposes a tool that analyzes a NestJS controller and generates an importable Postman collection. MCP-compatible assistants can invoke it with the controller file path, project path, and collection name.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMENestJS to Postman Collection Generator (MCP)
A Model Context Protocol (MCP) tool that automatically converts your NestJS controllers into importable Postman API collections. This eliminates the need to manually create Postman collections or implement complex swagger documentation directly within your code.
Features
- 🚀 Automatic API Collection Generation: Transform NestJS controllers into complete Postman collections with a single command
- 🔍 Intelligent Type Detection: Automatically detects request and response types to generate meaningful examples
- 🔐 Auth Integration: Identifies authentication guards and adds appropriate auth configurations
- 📊 Complete Endpoint Documentation: Captures routes, methods, request bodies, and query parameters
- 🧩 Clean Integration: Works without modifying your NestJS codebase (no decorators or comments needed)
- 🔌 MCP Integration: Works as an AI tool with any Model Context Protocol compatible assistant
Installation
- Clone the repository:
git clone https://github.com/ChiragKr04/nestJS-api-postman-MCP.git
cd nestJS-api-postman-MCP
- Install dependencies and build the project:
npm install
npm run build
Usage
As an MCP Tool
This tool is designed to work with any AI assistant that supports the Model Context Protocol. After installation, you need to configure your MCP-compatible AI assistant to use this tool.
Configuration
For Claude Desktop
Add the following configuration to your Claude Desktop settings:
{
"mcpServers": {
"Nest-Js-MCP-Postman-Generator": {
"command": "node",
"args": [
"/path/to/your/clone/nestJS-api-postman-MCP/dist/main.js",
"start"
]
}
}
}
For GitHub Copilot/Cursor/Windsurf/Other VS Code based AI tools
Add the following configuration to your VS Code settings.json:
{
"mcp": {
"servers": {
"Nest-Js-MCP-Postman-Generator": {
"command": "node",
"args": [
"/path/to/your/clone/nestJS-api-postman-MCP/dist/main.js",
"start"
]
}
}
}
}
Note: Replace
/path/to/your/clone/with the actual path where you cloned the repository.
Usage
Once configured:
- Just ask the AI to generate a Postman collection for your NestJS controller
- The AI will use this tool to analyze your controller and generate the collection
Example prompt:
Generate a Postman collection for my user.controller.ts file in my NestJS project.
Direct Command Line Usage
The tool also provides a command-line interface for direct usage:
# Generate using the CLI
node dist/main.js generate /path/to/nestjs/project -o collection.json -n "My API Collection"
API Reference
When used as an MCP tool, the following parameters are available:
| Parameter | Type | Description |
|---|---|---|
controllerFilePath | string | Path to the NestJS controller file (relative to project root) |
projectPath | string | Path to the NestJS project (containing tsconfig.json) |
collectionName | string | Name for the generated Postman collection |
Why Use This?
No More Manual Updates
Each time you change your API endpoints, your Postman collection automatically stays in sync.
Clean Code
Unlike Swagger/OpenAPI decorators that clutter your codebase with documentation:
// No more of this annotation clutter
@ApiOperation({ summary: 'Create a new user' })
@ApiBody({ type: CreateUserDto })
@ApiResponse({ status: 201, description: 'User created successfully' })
@ApiResponse({ status: 400, description: 'Bad Request' })
@Post()
create(@Body() createUserDto: CreateUserDto) {
return this.userService.create(createUserDto);
}
Accurate Documentation
The tool analyzes your actual code including:
- Route paths from controller decorators
- HTTP methods from method decorators
- Request body types from parameter decorators
- Query parameters and their types
- Authentication requirements
Example Output
The generated Postman collection will look like this:
{
"name": "User API",
"item": [
{
"name": "POST /api/users (createUser)",
"request": {
"method": "POST",
"header": [
{
"key": "Content-Type",
"value": "application/json"
}
],
"url": {
"raw": "{{baseUrl}}/api/users",
"host": ["{{baseUrl}}"],
"path": ["api", "users"],
"query": []
},
"body": {
"mode": "raw",
"raw": "{\n \"email\": \"[email protected]\",\n \"password\": \"password123\",\n \"name\": \"John Doe\"\n}"
},
"description": "Generated from createUser in UserController."
}
}
]
}
Requirements
- Node.js 16+
- A NestJS project with TypeScript
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
This project is licensed under the ISC License - see the LICENSE file for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.