Postman MCP Generator

- ✅ An MCP-compatible server (mcpServer.js)
- ✅ Automatically generated JavaScript tools for each selected Postman API request

Before starting, please ensure you have:

Warning: if you run with a lower version of Node,fetchwon't be present. Tools usefetchto make HTTP calls. To work around this, you can modify the tools to usenode-fetchinstead. Make sure thatnode-fetchis installed as a dependency and then import it asfetchinto each tool file.

Run from your project's root directory:

In the.envfile, 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:

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 thetoolsdirectory 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.envfile or tool files to accurately reflect the API's method of authentication.

The MCP Server (mcpServer.js) exposes your automated API tools to MCP-compatible clients, such as Claude Desktop or the Postman Desktop Application. We recommend that you test the server with Postman first and then move on to using it with an LLM.

The Postman Desktop Application is the easiest way to run and test MCP servers. Testing the downloaded server first is optional but recommended.

Step 3: Set the type of the MCP request toSTDIOand set the command tonode </absolute/path/to/mcpServer.js>. If you have issues with using onlynode(e.g. an old version is used), supply an absolute path instead to a node version 18+. You can get the full path to node by running:

To get the absolute path tomcpServer.js, run:

Use the node command followed by the full path tomcpServer.jsas the command for your new Postman MCP Request. Then click theConnectbutton. You should see a list of tools that you selected before generating the server. You can test that each tool works here before connecting the MCP server to an LLM.

You can connect your MCP server to any MCP client. Here we provide instructions for connecting it to Claude Desktop.

Step 1: Note the full path to node and themcpServer.jsfrom the previous step.

Step 2. Open Claude Desktop →Settings→Developers→Edit Configand add a new MCP server:

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

An MCP server for interacting with the Postman API, requiring an API key.

Adds possibility to work with testing management via MCP

An enhanced Apifox MCP service providing comprehensive API management capabilities for Claude Desktop and Cursor.

This MCP Server accepts swagger/postman documents as input. It then generates API & Load test scenarios, executes the tests and generates the execution report.

A Model Context Protocol (MCP) server for creating, managing, and executing Bruno API testing collections. Supports both .bru and .yml (opencollection) formats with built-in security hardening.

Execute Bruno collections using the Bruno CLI, with support for environment files and detailed test results.

An MCP server exposing Hoverfly as a programmable API simulation tool for AI assistants.

A free public REST API for testing and prototyping, powered by JSONPlaceholder.

Postman for MCP — search 156 servers, inspect tools with schema visualizer, test live