About Postman Agent Generator
Postman Agent Generator produces a Node.js MCP server with JavaScript tools generated from selected Postman API requests. It is intended for exposing those API operations to MCP-compatible clients.
Key features
- 01Generated MCP server
- 02Tools generated from API requests
- 03API-key environment variables
- 04Tool listing via CLI
- 05SSE and Docker options
Use cases
- 01Expose selected Postman requests to an MCP client
- 02Inspect generated tool descriptions and parameters
- 03Configure API credentials for generated tools
MCP support
The project generates an MCP-compatible server that exposes its API tools to clients such as Claude Desktop and the Postman Desktop Application.
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 READMEPostman Agent Generator
Welcome to your generated agent! 🚀
This project was created with the Postman Agent Generator, configured to Model Context Provider (MCP) Server output mode. It provides you with:
- ✅ An MCP-compatible server (
mcpServer.js) - ✅ Automatically generated JavaScript tools for each selected Postman API request
Let's set things up!
🚦 Getting Started
⚙️ Prerequisites
Before starting, please ensure you have:
- Node.js (v16+ required, v20+ recommended)
- npm (included with Node)
📥 Installation & Setup
1. Install dependencies
Run from your project's root directory:
npm install
🔐 Set tool environment variables
In the .env file, you'll see environment variable placeholders, one for each workspace that the selected tools are from. For example, if you selected requests from 2 workspaces, e.g. Acme and Widgets, you'll see two placeholders:
ACME_API_KEY=
WIDGETS_API_KEY=
Update the values with actual API keys for each API. These environment variables are used inside of the generated tools to set the API key for each request. You can inspect a file in the tools directory to see how it works.
// environment variables are used inside of each tool file
const apiKey = process.env.ACME_API_KEY;
Caveat: This may not be correct for every API. The generation logic is relatively simple - for each workspace, we create an environment variable with the same name as the workspace slug, and then use that environment variable in each tool file that belongs to that workspace. If this isn't the right behavior for your chosen API, no problem! You can manually update anything in the .env file or tool files to accurately reflect the API's method of authentication.
In the .env file, add the following environment variables for InsightSentry tools:
INSIGHTSENTRY_API_KEY=your_api_key_here
INSIGHTSENTRY_BASE_URL=https://insightsentry.p.rapidapi.com
INSIGHTSENTRY_WS_URL=wss://stream.insightsentry.com/quote
The INSIGHTSENTRY_API_KEY is your RapidAPI key for accessing the InsightSentry API.
The INSIGHTSENTRY_BASE_URL is the base URL for REST API endpoints.
The INSIGHTSENTRY_WS_URL is the WebSocket URL for real-time data streams.
🛠️ List Available Tools
List descriptions and parameters from all generated tools with:
node index.js tools
Example:
Available Tools:
Workspace: acme-workspace
Collection: useful-api
list_all_customers
Description: Retrieve a list of useful things.
Parameters:
- magic: The required magic power
- limit: Number of results returned
[...additional parameters...]
🌐 Running the MCP Server
The MCP Server (mcpServer.js) exposes your automated API tools to MCP-compatible clients, such as Claude Desktop or the Postman Desktop Application.
A) 🖥️ Run with Postman
The Postman Desktop Application is the easiest way to run and test MCP servers.
Step 1: Download the latest Postman Desktop Application from https://www.postman.com/downloads/.
Step 2: Read out the documentation article here for the next steps.
B) 👩💻 Run with Claude Desktop
To integrate with Claude Desktop:
- Find node path:
which node
- Find
mcpServer.jspath:
realpath mcpServer.js
- Open Claude Desktop → Settings → Developers → Edit Config and add your server:
{
"mcpServers": {
"<server_name>": {
"command": "<absolute_path_to_node>",
"args": ["<absolute_path_to_mcpServer.js>"]
}
}
}
Restart Claude Desktop to activate this change.
Additional Options
🐳 Docker Deployment (Production)
For production deployments, you can use Docker:
1. Build Docker image
docker build -t <your_server_name> .
2. Claude Desktop Integration
Add Docker server configuration to Claude Desktop (Settings → Developers → Edit Config):
{
"mcpServers": {
"<your_server_name>": {
"command": "docker",
"args": ["run", "-i", "--rm", "--env-file=.env", "<your_server_name>"]
}
}
}
Add your environment variables (API keys, etc.) inside the
.envfile.
🌐 Server-Sent Events (SSE)
To run the server with Server-Sent Events (SSE) support, use the --sse flag:
node mcpServer.js --sse
🐳 Dockerfile (Included)
The project comes bundled with the following minimal Docker setup:
FROM node:22.12-alpine AS builder
WORKDIR /app
COPY package.json package-lock.json ./
RUN npm install
COPY . .
ENTRYPOINT ["node", "mcpServer.js"]
➕ Adding New Tools
Extend your agent with more tools easily:
- Visit Postman Agent Generator.
- Pick new API request(s), generate a new agent, and download it.
- Copy new generated tool(s) into your existing project's
tools/folder. - Update your
tools/paths.jsfile to include new tool references.
💬 Questions & Support
Visit the Postman Agent Generator page for updates and new capabilities.
Visit the Postman Community to share what you've built, ask questions and get help.
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.