What it does

Exposes Postman collections, environments, and request history to the agent. The underrated use is reading an existing environment to learn the base URL and auth scheme instead of guessing them. Official and scoped, but treat your collection as production data — it often contains real keys.

Install

Terminal

npx -y @postman/postman-mcp-server

Client configuration

Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.

mcp.json

{
  "mcpServers": {
    "postman": {
      "command": "npx",
      "args": [
        "-y",
        "@postman/postman-mcp-server"
      ]
    }
  }
}

Use it for

Reading collections and environments while debugging an API

Skip it if

Running a full test suite; that belongs in CI

When to use it

Reach for this when the task needs api inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.

Other TypeScript servers

Filesystem — Gives an agent scoped read, write, and search access to directories you explicitly allow
Memory — A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
Sequential Thinking — Gives the model a scratchpad for structured, revisable reasoning: numbered thoughts that can branch, revise, and conclude

Postman MCP