home / mcp / postman mcp server

Postman MCP Server

Exposes Postman API requests as MCP-compatible tools for local use and MCP clients.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "abhishekms1047-postman-mcp-server": {
      "command": "node",
      "args": [
        "/absolute/path/to/mcpServer.js"
      ],
      "env": {
        "ACME_API_KEY": "YOUR_API_KEY",
        "WIDGETS_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

You have an MCP server that exposes your Postman API requests as MCP-compatible tools. It lets you run those tools locally or via an MCP client, test them quickly, and connect the server to an MCP workflow or agent. This guide walks you through using the server, installing dependencies, and deploying or running it in different modes.

How to use

Start by running the MCP server locally to make its tools available to an MCP client. Use node mcpServer.js from the project root to launch. To enable Server-Sent Events (SSE) for streaming updates, start with node mcpServer.js --sse. If you want to run the server inside Docker, follow the Docker deployment steps below.

How to install

Prerequisites: ensure you have Node.js version 18 or newer and npm installed.

From your project root, install dependencies.

Create or update environment variables to authorize requests from each workspace. Example placeholders you will see in your environment file include ACME_API_KEY= and WIDGETS_API_KEY=. These values are used inside the generated tools to set the API key for each request.

Run the following command to install dependencies.

npm install

Run and test the MCP server locally

Start the server with the standard command to expose generated tools to an MCP client.

node mcpServer.js

If you want to test using SSE for streaming updates, run the server with the SSE flag.

node mcpServer.js --sse

Docker deployment (production)

You can deploy the MCP server using Docker for production workloads.

Build the Docker image.

docker build -t <your_server_name> .

Configure Claude Desktop to run the Docker container and load environment variables from a file.

{
  "mcpServers": {
    "<your_server_name>": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "--env-file=.env", "<your_server_name>"]
    }
  }
}

Notes on testing and usage

Use a compatible MCP client to connect to the server and verify that each generated tool responds as expected. Ensure the environment file contains the required keys for each workspace, and that the server is reachable by the client before attempting real usage.

Additional options

If you prefer to run the server via an inline command (for example in a CI or scripted environment), you can invoke the same entry points shown above with the appropriate runner and arguments.