postman

An MCP server that provides access to Postman.

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio delano-postman-mcp-server node /path/to/postman-api-server/build/index.js \
  --env POSTMAN_API_KEY="CHANGEME"

How to use

The Postman MCP Server exposes the Postman API through an MCP-compatible endpoint, enabling you to manage Postman collections, environments, APIs, and related resources via MCP tooling. It is designed to work with Claude Desktop, Cline, and (where supported) Zed, allowing you to query and orchestrate your Postman resources through natural language or structured prompts. To get started, supply your Postman API key to the server environment so authentication for Postman resources is established, and configure the MCP client (Claude Desktop or Cline) with the server’s endpoint and tool definition. The server supports operations for CRUD management of collections, environments, and APIs, along with authentication, webhooks, and enterprise features for more advanced usage.

How to install

Prerequisites:

Node.js installed on your system
Access to a command-line interface

Steps:

Clone the repository: git clone https://github.com/delano/postman-api-server.git cd postman-api-server
Install dependencies (using pnpm as per the repository): pnpm install
Build the server: pnpm run build
Run in development mode with auto-rebuild (watch mode): pnpm run watch

Optional (for MCP integration):

Ensure Node.js is accessible and that the build output path is correct in your MCP configuration (build/index.js).
Export your Postman API key as an environment variable or provide it in your MCP client configuration.

Additional notes

Environment variables and configuration:

POSTMAN_API_KEY: Your Postman API key. Do not commit keys to version control. Provide this in the server environment or MCP client config as shown in the example.
If updating the server tooling, restart Claude Desktop or the MCP client to pick up updated tool definitions.

Common issues:

Invalid API key or insufficient Postman permissions can cause API calls to fail; verify the key has access to the required resources.
Ensure the build output path in your MCP configuration matches where the compiled server file (index.js) resides after pnpm run build.

Configuration tips:

In Claude/Desktop or Cline, reference the same server configuration shape shown in the README example to ensure compatibility with MCP tool definitions.