Use AI agents with the Postman API
The Postman Model Context Protocol (MCP) server enables AI agents like Claude, Cursor, and VS Code to help you manage your Postman resources, including workspaces, collections, specifications, mocks, and monitors. The server translates your natural language commands into API workflows behind the scenes. With MCP, you can build AI agents and complex workflows on top of LLMs using the tools and context provided by the servers.
The Postman MCP server is also available in the Postman MCP server GitHub repository.
Before you begin
You need a Postman account to use the MCP server. To use API key authentication, generate a Postman API key. An API key is required for the local server and the EU remote server, and optional on the US remote server. Keep this key secret and store it as an environment variable or your host’s secret store, not in shared files.
Communication methods
Communication between the Postman API and the AI agent happens through the following methods:
-
Remote Server — Securely links the agent to the server over streamable HTTPS, without requiring any extra agent setup. Great for using the Postman MCP server with your preferred IDE or AI agent. It supports several tool configurations to better serve different use cases.
-
Local Server — Runs the MCP server locally on the agent machine with STDIO. Requires downloading and running the source code yourself or spinning up a local Docker image. Local servers also support different tool configurations to support different use cases.
Use the remote server if your host doesn’t support local servers, you want the quickest setup, or you work mainly with public APIs. Use the local server for local API testing, internal APIs, specific security or network requirements, or if you prefer to build the server from source.
For a complete list of the Postman MCP server’s tools, see the Postman MCP server collection.
Tool configurations
Both the remote and local servers offer the same tool configurations, so you can load only the tools you need. Loading fewer tools lowers token usage and helps your agent choose the right tool.
- Minimal (default) — Essential tools for core Postman operations. Best for getting started or working with a single collection, workspace, or environment.
- Code — Tools to search public and internal API definitions and generate idiomatic client code. Best for consuming APIs or giving your agent context about APIs.
- Full — All available Postman API tools (100+). Best for advanced collaboration and Postman Enterprise features.
For the specific endpoint URLs (remote) and command-line flags (local), see Set up a remote server and Set up a local server.
EU support
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, andhttps://mcp.eu.postman.com/minimal. - For the STDIO public package, use the
--region euflag to specify the Postman API EU region, or set thePOSTMAN_API_BASE_URLenvironment variable directly.
OAuth isn’t supported for the EU Postman MCP server. The EU remote server only supports API key authentication.
Use cases
- Code synchronization — Effortlessly keep your code in sync with your collections and specifications.
- 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 specifications from your code and use them to generate Postman Collections.
The Postman MCP server supports both remote servers through streamable HTTP and local servers with STDIO. Postman also offers servers as an npm package and as a Docker image.
Authentication
For the best developer experience and fastest setup, use OAuth on the remote server. OAuth is fully compliant with the MCP Authorization specification and doesn’t require manual API key configuration.
The EU remote server and the local server support only Postman API key authentication.
Get started with agents
Get set up and running with your remote or local Postman MCP server. Then, explore best practices and tips for getting the most out of its features.