home / mcp / postman mcp server

Postman MCP Server

Provides Postman context to AI assistants via remote HTTP or local STDIO servers for workspace, collection, environment, and API management.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "postmanlabs-postman-mcp-server": {
      "url": "https://mcp.postman.com/minimal",
      "headers": {
        "POSTMAN_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

You can connect Postman to AI-assisted workflows with the Postman MCP Server. It lets your AI agents access Postman workspaces, manage collections and environments, evaluate APIs, and automate workflows through natural language queries and commands. This enables seamless integration of Postman context into your automation and coding assistants.

How to use

Use the Postman MCP Server with an MCP-compatible client or extension to interact with your Postman data in natural language. You can pick from remote HTTP servers that Postman hosts or run a local STDIO server for tight editor integration. Start with the Minimal configuration for quick setups, then switch to Full for all tools or Code to focus on API definitions and client code generation.

How to install

Prerequisites you need before installing are:</br>- Node.js installed on your machine if you plan to run a local STDIO server. The specific Node.js version is not required in this guide, but ensure it’s compatible with your environment.

Choose your installation path based on how you want to run the MCP server: remote HTTP servers or a local STDIO server.

Install remote HTTP MCP servers

Remote servers are offered in distinct tool configurations. Pick Minimal for basic operations, Code for API-definition tooling, or Full for all tools.

Remote HTTP MCP servers are available in the following regions and configurations.

Install local STDIO MCP server

If you prefer running the MCP server on your machine for editor integrations, install the local STDIO server. Use the following command variations to select the desired mode.

Configuration and usage notes

You can configure access to Postman MCP services in your editor or tool by pointing to the appropriate MCP URL or by using the npx-based CLI approach. Ensure you provide your Postman API key in the Authorization header when connecting to remote servers. For local setups, you’ll typically provide the API key as an environment variable or prompt.

Examples and practical patterns

- Use Minimal remote servers to quickly start integrating with workspace and collection management. - Switch to Full to enable enterprise features and all available tools. - Use Code to generate client code from API definitions and examples to speed up integration work.

Security considerations

Protect your API key. Use the Authorization: Bearer YOUR_API_KEY header for remote servers and keep keys out of source control. When running locally, supply the key through a secure input or environment variable and avoid exposing it in logs.

Available tools

code

Generates client code from API definitions and internal definitions, organizing it into a tree structure mirroring your Postman collections and requests, with accurate response types and error handling.

minimal

Essential toolset for basic Postman operations, enabling quick access to workspaces, collections, and environments.

full

Complete toolset with all Postman API tools (100+ tools) for advanced collaboration and enterprise features.

searchDefinitions

Tool to search public and internal API definitions to help locate relevant API specs and endpoints.