postman

The Postman MCP server provides an API for managing Postman resources such as workspaces, collections, requests, environments, and folders. It exposes a suite of tools that let an AI assistant or an application list workspaces, inspect and modify collections, add or update HTTP requests, and manage environments with sensitive variables. Typical workflows include creating a workspace, building and updating a collection with requests, organizing items into folders, and configuring environments with default and secret variables. The tools are designed to cover the full lifecycle of Postman assets and enable automation scenarios that previously required manual Postman UI interactions.

To use the server, start it via MCP client configuration (for example using npx postman-mcp). Once running, call the available tools such as list_workspaces, get_workspace, create_collection, add_request, and create_environment through the MCP runtime. Each tool accepts a structured payload (e.g., IDs, names, URLs, headers, body, and environment values) and returns the resulting resource data or confirmation. This enables programmatic workflows like provisioning a new workspace with a collection, injecting environment variables, and adding requests to folders in an automated fashion.

Prerequisites:

• Node.js 18+ installed on your system
• npm or yarn
• A Postman API key with appropriate permissions

Setup and installation steps:

1. Clone the repository:

   git clone https://github.com/SalehKhatri/postman-mcp.git
   cd postman-mcp
   

2. Install dependencies:

   npm install
   

3. Configure environment:

   cp .env.example .env
   # Edit .env and add your POSTMAN_API_KEY
   

4. Build the project (if required by the setup):

   npm run build
   

5. Run in development mode:

   npm run dev
   

Notes and tips:

• Environment variable: POSTMAN_API_KEY must be set with a valid Postman API key. Treat this key as sensitive data.
• If you encounter API rate limits, consider staggering requests or implementing retry/backoff logic in your application.
• The MCP server exposes operations for workspaces, collections, requests, environments, and folders; ensure you pass correct IDs and structure when calling tools.
• When running in production, consider securing the environment and restricting access to the MCP server to trusted clients.
• You can also run the MCP server via standard command: npx postman-mcp or node path/to/postman-mcp/dist/index.js depending on your setup.