Use Cases

• API Testing — Continuously test your API using your Postman collection. To be able to test local APIs, use the local server, as the remote server won't have network access to your workstation.
• Code synchronization — Effortlessly keep your code in sync with your Postman Collections and specs.
• Collection management — Create and tag collections, update collection and request documentation, add comments, or perform actions across multiple collections without leaving your editor.
• Workspace and environment management — Create workspaces and environments, plus manage your environment variables.
• Automatic spec creation — Create specs from your code and use them to generate collections.
• Client code generation — Generate production-ready client code that consumes APIs following best practices and project conventions. The code toolset produces code that precisely matches your API definitions, organizes it into an intuitive tree structure mirroring your Postman collections and requests, and leverages example responses to create accurate response types and error handling.

Designed for developers who want to integrate their AI tools with Postman's context and features. Supports quick natural language queries to advanced agent workflows.

Support for EU

The Postman MCP Server supports the EU region for remote and local servers:

• For streamable HTTP, the remote server is available at https://mcp.eu.postman.com/mcp (Full), https://mcp.eu.postman.com/code, and https://mcp.eu.postman.com/minimal.
• For the STDIO public package, use the --region eu flag to specify the Postman API EU region, or set the POSTMAN_API_BASE_URL environment variable directly.
• OAuth isn't supported for the EU Postman MCP Server. The EU remote server only supports API key authentication.

Contents

• Remote server
  • VS Code
  • Cursor
  • Claude Code
  • Codex
  • Windsurf
  • Antigravity
  • GitHub Copilot CLI
• Local server
  • VS Code
  • Cursor
  • Claude
  • Claude Code
  • Codex
  • Windsurf
  • Antigravity
  • GitHub Copilot CLI
  • Gemini CLI
  • Install in Kiro
  • Docker
• Questions and support
• Migration from Postman MCP Server v1 to v2

Remote server

The remote Postman MCP Server is hosted by Postman over streamable HTTP and provides the easiest method for getting started.

The remote server (https://mcp.postman.com) supports OAuth for the best developer experience and fastest setup, and no API key needed. OAuth also provides stronger security and fine-grained access control compared to a static API key. OAuth is MCP specification–compliant, including Dynamic Client Registration (DCR), OAuth metadata, and PKCE.

Note: The EU remote server (https://mcp.eu.postman.com) only supports API key authentication.

MCP hosts that support OAuth can discover and use it automatically for all tools. The remote server also accepts a Postman API key (Bearer token in the Authorization header).

Why use the remote server?

Consider using the remote Postman MCP server if:

• Your MCP host doesn't support local MCP servers.
• You want a quick way to get started with the Postman MCP server.
• You are working with public APIs.

Supported configurations

The remote server supports the following tool configurations:

• Minimal — (Default) Only includes essential tools for basic Postman operations, available at https://mcp.postman.com/minimal and https://mcp.eu.postman.com/minimal for EU users. This offers faster performance and simplifies use for those who only need basic Postman operations.
• Code — Includes tools for searching public and internal API definitions and generating client code, available at https://mcp.postman.com/code and https://mcp.eu.postman.com/code for EU users. This configuration is ideal for users who need to consume APIs or get context about APIs to their agents.
• Full — Includes all available Postman API tools (100+ tools), available at https://mcp.postman.com/mcp and https://mcp.eu.postman.com/mcp for EU users.

Install in Cursor

To install the remote Postman MCP Server in Cursor, click the install button.

If your MCP host supports OAuth, use the https://mcp.postman.com/mcp, https://mcp.postman.com/minimal, or https://mcp.postman.com/code server URL without headers for the fastest setup. Otherwise, ensure the Authorization header uses the Bearer <YOUR_API_KEY> format. Note that OAuth isn’t supported for EU servers.

After installing, ensure that the Authorization header uses the Bearer $POSTMAN-API-KEY format.

To access Full mode, change the url value to https://mcp.postman.com/mcp in the mcp.json file. To access Code mode, change the value to https://mcp.postman.com/code in this file.

Install in Visual Studio Code

To install the remote Postman MCP Server in VS Code, click the install button or use the Postman VS Code Extension.

To access Full mode, change the url value to https://mcp.postman.com/mcp in the mcp.json file. To access Code mode, change the value to https://mcp.postman.com/code in this file.

Manual configuration

You can use the Postman MCP Server with MCP-compatible extensions in VS Code, such as GitHub Copilot, Claude for VS Code, or other AI assistants that support MCP. To do so, add the following JSON block to the .vscode/mcp.json configuration file:

OAuth

Add the following JSON block to use the recommended OAuth installation method:

{
    "servers": {
        "postman": {
            "type": "http",
            "url": "https://mcp.postman.com/minimal"
                // "https://mcp.postman.com/code" for Code mode