home / mcp / postman mcp generator mcp server

Postman MCP Generator MCP Server

Exposes generated Postman API tools as an MPCP server for seamless client integration.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "amit-lakhani-mcp1": {
      "url": "https://mcp.example.com/mcp",
      "headers": {
        "ACME_API_KEY": "<ACME_API_KEY>",
        "WIDGETS_API_KEY": "<WIDGETS_API_KEY>"
      }
    }
  }
}

You have an MCP server that exposes your automated Postman API tools to MCP-compatible clients. It streamlines running your Postman requests as tools accessible via a standard MCP interface, so you can connect from chat clients or automation pipelines and invoke your APIs with simple calls.

How to use

Start the MCP server locally and connect with your MCP client. The server file is mcpServer.js. Run it from your project root to expose your tools to the MCP ecosystem.

How to install

Prerequisites ensure you can run modern Node.js applications and manage dependencies.

# 1) Install Node.js (v18+ is required, v20+ recommended)
# 2) Ensure npm is installed along with Node
```,

Install dependencies for the project from your project root.

npm install

Additional options

Run the server with Server-Sent Events (SSE) support to enable real-time streaming responses.

node mcpServer.js --sse

Alternatively, you can run the server in a standard local development mode by starting the JavaScript file directly with Node. Use an absolute path to the file if needed.

node </absolute/path/to/mcpServer.js>

Notes for testing and integration

To verify that your server operates correctly with a client, connect a supported MCP client and ensure you can list and invoke the generated tools. If you need to test locally via a client, start the server and then use your client’s MCP connection settings to browse available tools and run them.

Security and environment considerations

Environment variables are used to supply API keys for the generated tools. Create or edit the environment file with keys matching your workspaces and ensure the client has access to the keys when invoking tools.

Docker deployment (optional)

For production or isolated environments, you can run the server inside Docker. Build the image and run with an environment file.

docker build -t <your_server_name> .
```

```
docker run -i --rm --env-file=.env <your_server_name>

Connecting to clients (example configuration)

When configuring an MCP client to run the local server, use the stdio command with the Node executable and the path to mcpServer.js as arguments.

{
  "mcpServers": {
    "postman_mcp": {
      "command": "node",
      "args": ["/absolute/path/to/mcpServer.js"]
    }
  }
}