Integrate Postman with AI for API Management

The Postman MCP Server implements the Model Context Protocol to connect AI agents and coding assistants directly to your Postman workspaces, collections, specifications, and environments. Named hosts include Claude Code, Cursor, VS Code Copilot, GitHub Copilot CLI, and Gemini CLI. Instead of switching between your editor and Postman, the assistant works against your Postman data in place. The server is also published as an npm package, so it can run locally as well as against Postman's hosted remote endpoint.

Four tool configurations control how much of the Postman API the agent sees. Minimal is the default and includes only essential tools for basic operations, which suits changing a single element such as a collection, workspace, or environment. Code adds tools that generate well-organized client code from public and internal API definitions. Full exposes every available Postman API tool, over 100 in total, for advanced collaboration and Enterprise features. Learn searches the Postman Docs for guides, tutorials, and reference content, which helps an agent look up API concepts.

Use it when you want an assistant to act on Postman assets without leaving your editor. Use cases include:

• API testing: continuously test your API with your Postman collection. Use the local server for local APIs, because the remote server has no network access to your workstation.
• Code synchronization: keep your code in sync with your Postman Collections and specs.
• Collection management: create and tag collections, update documentation, add comments, or act across many collections at once.
• Workspace and environment management: create workspaces and environments and manage environment variables.
• Automatic spec creation: create specs from your code and generate collections from them.
• Client code generation: produce client code that consumes APIs and follows project conventions.

Do not choose the remote server for testing APIs that only run on your machine. Do not expect OAuth in the EU region or with the local server: those support only Postman API key authentication.

The tool surface depends on the configuration you pick, from the essential Minimal set up to the 100+ tools in Full. Code mode focuses on client code generation, and Learn mode focuses on documentation search. A Postman MCP Server collection lets you browse the complete list of tools across all configurations and test connections to the Full and Minimal remote servers and the local server. The EU region is supported for remote and local servers through separate EU endpoints, a region flag for the STDIO package, or the POSTMAN_API_BASE_URL environment variable.

For the fastest setup, use OAuth on the remote server at mcp.postman.com. OAuth follows the MCP Authorization specification and needs no manual API key configuration. Add the endpoint URL to any OAuth-compatible MCP host. Changing the path from minimal to code or mcp selects Code or Full mode. For EU or API key authentication, pass an Authorization Bearer header containing your Postman API key.

To run the server locally, use the npm package and set POSTMAN_API_KEY as an environment variable. Add the code or full flag for those modes:

npx @postman/postman-mcp-server

Postman publishes per-agent setup instructions for Claude Code, Claude Desktop, Cursor, VS Code, Codex, Antigravity CLI, GitHub Copilot CLI, and Kiro. Docker is available for local use, with its own setup guide in the repository.

It is for developers who already keep their APIs in Postman and want an AI assistant to read and change those assets: engineers consuming APIs who need generated client code, teams keeping collections and specs aligned with their codebase, and Enterprise users who need the broader Full toolset. It also suits agent builders who want an assistant that can look up Postman documentation. Bug reports and tool requests go through GitHub Issues, since the tool definitions and server implementation are synced from Postman's internal source and changes under the source folder cannot be merged in the public repository.