Postman MCP Server: Tools, Setup and Security

The Postman MCP Server connects AI agents and coding assistants to your Postman workspaces, collections, specifications and environments. Postman publishes it as a hosted remote server and as an npm package you run locally.

Checked against: Postman MCP Server README and Postman's remote server docs on 28 October 2026. eSEOspace did not install or test this server.

At a glance

What it can do

Postman organizes the server into tool configurations:

• Minimal (default): essential tools for changing a single element, such as a collection, workspace or environment.
• Code: tools that generate client code from public and internal API definitions.
• Full: all Postman API tools, "100+ tools," for advanced collaboration and Enterprise features.
• Learn: searches Postman's documentation.
• Context Graph: listed in the remote docs with its own endpoint.

Postman's listed use cases include testing APIs with your collections, keeping code in sync with collections and specs, managing workspaces and environment variables, creating specs from code and generating client code.

Postman does not print the tool names in the README. It points to a public Postman MCP Server collection that lists every tool across configurations.

How to connect it

Remote endpoints by mode, from Postman's docs:

For Claude Code with OAuth:

claude mcp add --transport http postman https://mcp.postman.com/minimal

For VS Code, in .vscode/mcp.json:

{
    "servers": {
        "postman": {
            "type": "http",
            "url": "https://mcp.postman.com/minimal"
        }
    }
}

VS Code's MCP server docs still support .vscode/mcp.json "for compatibility" but label it deprecated in the guided setup flow, as of October 2026. Servers that prompt for values with ${input:...} aren't forwarded to Copilot harness sessions.

For the local server, set POSTMAN_API_KEY and run:

npx @postman/postman-mcp-server

Add --code or --full for those modes, or --region eu for the EU region. Postman also documents Cursor, Codex, GitHub Copilot CLI, Kiro and Docker.

Security notes

• Pick the smallest mode. Minimal is the default for a reason. Full mode exposes 100+ tools, which widens what the AI can change.
• Protect API keys. Postman's docs say to keep your API key "out of shared or committed files." The EU server and local server require one.
• Telemetry. Product telemetry is on by default for the remote server.
• Network reach. The local server can call APIs on your machine or private network. That is useful for testing but also means the AI can reach internal endpoints.

The MCP project's security best practices also cover risks such as token passthrough, confused deputy attacks and scope minimization.

Postman environments often hold secrets such as API tokens for other services. Read secrets and credential leakage and SSRF in MCP, and see the MCP Security Center.

Alternatives

• Playwright MCP server for end-to-end browser tests rather than API tests.
• GitHub MCP Server to keep specs and code changes in pull requests.
• Context7 MCP server for up-to-date library docs while writing client code.

Next step

Start with the Minimal mode and a test workspace, then expand once you see what the agent does. Our guide on how to choose MCP servers has a short checklist, and the MCP server directory lists more developer tools.

Frequently asked questions