Postman MCP Server – API Workspace Automation
Postman's official MCP server gives AI agents structured access to Postman resources and API workflows. Use it to manage workspaces, collections, environments, specifications, mocks, monitors, documentation, and code-oriented API tasks directly from an MCP-compatible client.
Overview
Postman's official MCP server connects compatible AI agents to the Postman API
and a user's Postman resources. It translates natural-language instructions
into structured Postman operations, allowing agents to work with live API
assets instead of relying only on pasted collection files or static model
knowledge.
What the MCP server enables
The server supports operations across Postman resources such as workspaces,
collections, environments, specifications, mocks, monitors, and related API
development assets. Depending on the selected tool configuration and the
permissions of the authenticated account, an AI agent can:
- Create, retrieve, update, tag, and organize Postman collections.
- Create and manage workspaces, environments, and environment variables.
- Generate specifications from code and create collections from specifications.
- Search public or internal API definitions and generate client code in Code mode.
- Work with mocks, monitors, documentation, comments, and other supported resources.
- Coordinate multi-step API workflows from an IDE or AI coding assistant.
When to use it
Use Postman MCP when an agent needs current Postman context or must perform
authorized API-development tasks. Typical workflows include keeping code and
collections synchronized, generating an OpenAPI definition from an application,
creating a collection from a specification, updating environment variables,
documenting requests, managing internal API assets, and automating repetitive
workspace maintenance.
Connection and authentication
Postman hosts remote Streamable HTTP endpoints in three tool configurations:
Minimal at https://mcp.postman.com/minimal, Code at
https://mcp.postman.com/code, and Full at https://mcp.postman.com/mcp.
The US-hosted server supports OAuth with Dynamic Client Registration, PKCE, and
MCP authorization metadata. It also accepts a Postman API key as a Bearer token.
A local stdio server is available through the official
@postman/postman-mcp-server npm package. The local server reads the
POSTMAN_API_KEY environment variable and supports Minimal, Code, and Full
modes through command-line flags. Postman also documents EU endpoints, but
OAuth is not supported there; EU remote and local use requires an API key.
Key considerations
Full mode exposes more than 100 tools and consumes more context than Minimal or
Code mode. Choose the narrowest mode that fits the workflow. API permissions,
account access, and Postman API rate limits still apply. Review all write or
destructive actions before approval, especially updates and deletions. Pass
known resource IDs where possible to reduce extra discovery calls, and keep
API keys in a protected environment variable or secret manager rather than in
configuration files or source control.
Supported Transports
streamable_http
URL: https://mcp.postman.com/mcp
stdio
Command: npx
Args:
-y@postman/postman-mcp-server@latest--full
Frequently Asked Questions
- When should an AI agent use the Postman MCP server?
- Use it when a workflow needs live Postman resources or authorized API development actions, such as managing collections and workspaces, updating environments, generating specifications, creating collections from specs, maintaining documentation, or synchronizing API assets with code.
- What does the Postman MCP server add to an AI agent's capabilities?
- It gives the agent structured access to Postman API tools and current account resources, allowing natural-language requests to become authenticated Postman workflows instead of relying only on static knowledge or manually exported collection files.
- What can an AI agent access or manage through Postman MCP?
- Depending on the selected mode and account permissions, the agent can work with workspaces, collections, environments, variables, specifications, mocks, monitors, documentation, comments, public or internal API definitions, and supported code-generation workflows.
- How is authentication configured for the Postman MCP server?
- The US remote server supports OAuth with Dynamic Client Registration and PKCE, and it also accepts a Postman API key in the Authorization header as a Bearer token. The EU remote server and the local stdio server support API key authentication only. The local package reads POSTMAN_API_KEY.
- Which transport should be used for the Postman MCP server?
- Use Streamable HTTP for Postman's managed remote service and prefer OAuth on the US endpoint. Use stdio with the official npm package for local API testing, internal APIs, or stricter network requirements. Select Minimal, Code, or Full mode according to the required tool set.