home / mcp / postman mcp server

Postman MCP Server

An MCP server that provides access to Postman.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "delano-postman-mcp-server": {
      "command": "node",
      "args": [
        "/path/to/postman-api-server/build/index.js"
      ],
      "env": {
        "POSTMAN_API_KEY": "CHANGEME"
      }
    }
  }
}

You can manage and automate Postman resources through the Postman MCP Server. It exposes Postman collections, environments, APIs, and related features as MCP endpoints you can control from your MCP client, enabling AI-assisted workflows, automation, and structured access to your Postman workspaces.

How to use

Connect your MCP client to the Postman MCP Server using the local stdio configuration described below. You will run the server locally and point your client at the same process, so responses are immediate and tailored to your Postman resources. Use the server to create, read, update, and delete collections, environments, and APIs, manage comments and versioning, and configure authentication with an API key. When you operate across workspaces, environments, and APIs, you can leverage webhooks and enterprise features for automated workflows.

Typical usage patterns include starting the MCP server in the background or in your development environment, then issuing high-level actions from your MCP client to perform tasks such as creating a new collection, updating an environment, or forking a collection. Ensure you provide your Postman API key securely and avoid exposing it in version control.

How to install

Prerequisites you need before installation are Node.js installed on your machine.

Steps to install and run the server locally:

# Option A: install via Smithery for Claude Desktop
npx -y @smithery/cli install postman-api-server --client claude

# Local development flow
git clone https://github.com/delano/postman-api-server.git
cd postman-api-server

pnpm install
pnpm run build
pnpm run watch

Configuration for local execution

To run the MCP server locally as a stdio MCP server, use the following configuration. It starts the server with Node and points to the built index file. Replace the path with your actual build output path and provide your API key.

{
  "mcpServers": {
    "postman": {
      "command": "node",
      "args": [
        "/path/to/postman-api-server/build/index.js"
      ],
      "env": {
        "POSTMAN_API_KEY": "CHANGEME"
      }
    }
  }
}

Available tools

collectionsCRUD

Create, retrieve, update, and delete Postman collections; manage folders, requests, and responses; support for forking, merging, and commenting.

environmentsCRUD

Manage environments with full create, read, update, and delete operations.

apisCRUD

Create, retrieve, update, and delete API definitions; manage multi-file schemas, tags, and comments.

webhooks

Create webhooks to trigger collection runs with custom payloads.

privateApiNetwork

Manage a private API network for organizing elements and folders.

enterpriseFeatures

Advanced role controls and SCIM support for enterprise environments.