Set up a remote Postman MCP server
The remote Postman MCP server is hosted by Postman over streamable HTTP and provides the easiest method for getting started.
The remote server supports OAuth for the best developer experience and fastest setup, and doesn’t require an API key. OAuth provides stronger security and access control compared to a static API key. It’s MCP specification-compliant, including Dynamic Client Registration (DCR), OAuth metadata, and PKCE.
The EU remote server 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).
Use cases
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.
Supported configurations
The remote Postman MCP server offers the following tool configurations through streamable HTTP:
- Minimal — (Default) Only includes essential tools for basic Postman operations, available at
https://mcp.postman.com/minimalandhttps://mcp.eu.postman.com/minimalfor 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/codeandhttps://mcp.eu.postman.com/codefor 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/mcpandhttps://mcp.eu.postman.com/mcpfor EU users.
Cursor
Click the button to install the remote Postman MCP server in Cursor:
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.
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 installation
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 this, 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:
Start the server. When prompted, enter your Postman API key.
API key
Use the following JSON block to use the API key installation method:
Start the server. When prompted, enter your Postman API key.
Claude Code
On the US server, Claude Code automatically uses OAuth for the best installation experience. To use an API key (required for the EU server), add the --header flag.
OAuth
To use the OAuth installation method for US servers, run the following command in your terminal:
Minimal
Code
Full
API key
To use the API key installation method if required and for EU servers (mcp.eu.postman), run the following command in your terminal:
Minimal
Code
Full
Codex
To install the remote server in Codex, use one of the following methods, depending on your authentication and region.
OAuth
Use this method with the US server for the best installation experience. OAuth requires no manual API key setup.
Minimal
Code
Full
API key
If you’re using the EU server (mcp.eu.postman), a local server, or prefer API key authentication, use the API key method. Set the POSTMAN_API_KEY environment variable and invoke the MCP server using npx.
Minimal
Code
Full
Manual installation
To manually install the MCP server in Codex, create a ~/.codex/config.toml config file, then copy the following config into the file:
Windsurf
To install the MCP server in Windsurf, copy the following JSON config into the .codeium/windsurf/mcp_config.json file. This configuration uses the remote server, which automatically authenticates with OAuth.
Antigravity
To install the MCP server in Antigravity, click Manage MCP servers > View raw config. Then, copy the following JSON config into the .mcp_config.json file. This configuration uses the remote server, which automatically authenticates with OAuth.
GitHub Copilot CLI
You can add the MCP server to your Copilot CLI either with OAuth (recommended) or an API key.
Use the Copilot CLI to interactively add the MCP server:
For more information, see the Copilot CLI documentation.
Manual installation
Copy the following JSON config into the ~/.copilot/mcp-config.json file:
API key
Use the following method to install if API key authentication is required for EU servers (mcp.eu.postman):