Postman MCP Server

Official Postman MCP server. Lets AI agents manage workspaces, collections, environments, specs, mocks, and monitors through the Postman API.

Developer Tools by Postman OAuth2 or API Key (Bearer Token) active

Connect (Remote Server) GitHub Docs npm: @postman/postman-mcp-server

Overview

The Postman MCP Server is the official integration between Postman and the Model Context Protocol, maintained by Postman (postmanlabs). It lets AI agents like Claude, Cursor, and VS Code interact with your Postman account using natural language to manage workspaces, collections, environments, API specifications, mocks, and monitors via the Postman API.

The server is available in two flavors. A remote, provider-hosted server at https://mcp.postman.com (with an EU endpoint at https://mcp.eu.postman.com) supports OAuth and Bearer-token auth and requires no local install. A local STDIO server is published as the npm package @postman/postman-mcp-server and is also offered as a Docker image; the local server requires a Postman API key.

The server ships in three configurations: Minimal (default, around 37 essential tools for core workspace/collection/environment operations), Full (100+ tools covering advanced collaboration and Enterprise features), and Code (focused on searching public and internal API definitions and generating client code from them). Tool names use camelCase in v2.x (for example createCollection, getWorkspaces, deleteEnvironment).

Tools

Tool	Description
`createCollection`	Create a new Postman collection in a workspace.
`getWorkspaces`	List Postman workspaces the authenticated user can access.
`deleteEnvironment`	Delete a Postman environment by ID.
`Collection management tools`	Create, read, update, delete, fork, merge, tag, and document Postman collections.
`Workspace management tools`	Create and administer workspaces, members, and roles.
`Environment & variable tools`	Manage environments and their variables across workspaces.
`API specification tools`	Create, update, and version OpenAPI and other spec definitions in Postman.
`Mock server tools`	Create and configure mock servers based on collections.
`Monitor tools`	Create and manage Postman monitors that run collections on a schedule.
`Code generation tools (Code mode)`	Search public and internal API definitions and generate idiomatic client code from them.

Setup Guide

Remote server (recommended)

The hosted server at https://mcp.postman.com supports OAuth (no API key needed) and Bearer-token auth. Paths select the configuration: /minimal, /full, or /code. An EU endpoint is available at https://mcp.eu.postman.com (API key only).

Claude Code (Minimal, OAuth):

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

VS Code (.vscode/mcp.json):

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

Swap /minimal for /full or /code to change the tool set.

Local server (STDIO)

Requires Node.js and a Postman API key from https://postman.postman.co/settings/me/api-keys.

Claude Code (Full mode):

claude mcp add postman --env POSTMAN_API_KEY=YOUR_KEY -- npx @postman/postman-mcp-server@latest --full

VS Code / Cursor (mcp.json):

{
  "servers": {
    "postman": {
      "type": "stdio",
      "command": "npx",
      "args": ["@postman/postman-mcp-server", "--full"],
      "env": {
        "POSTMAN_API_KEY": "${input:postman-api-key}"
      }
    }
  }
}

Useful flags: --full, --minimal, --code for mode selection; --region eu (or POSTMAN_API_BASE_URL) to target the EU API; --quiet to suppress logs (helpful for Windsurf on Windows).

Prerequisites

A Postman account
A Postman API key (for the local server and the EU remote server)
Node.js installed (for the local STDIO server) or Docker

Use Cases

Scaffold a new Postman workspace, seed it with collections and environments, and document each request from a single agent prompt.
Generate or update OpenAPI specs in Postman from natural-language descriptions and keep them versioned.
Spin up mock servers from existing collections so frontend or partner teams can build against contracts before the real API is ready.
Bulk-tag, fork, or merge collections across workspaces during API refactors or migrations.
Use Code mode to search the Postman API Network for an API definition and have the agent generate idiomatic client code for it.

Example Prompts

"Create a new Postman workspace called 'Billing v2' and add a collection with CRUD requests for invoices."
"List all my workspaces and show the collections in the one named 'Internal APIs'."
"Update the 'staging' environment to point baseUrl at https://api.staging.acme.com."
"Generate a mock server from the 'Payments' collection and return the mock URL."
"Search the Postman API Network for the Stripe API and generate a TypeScript client for the Charges endpoints."

Pros

Officially built and maintained by Postman under the postmanlabs GitHub org.
Provider-hosted remote server with OAuth means zero local setup for most users.
Three configurations (Minimal, Full, Code) let you trade off tool count and token usage against feature breadth.
Supports US and EU regions plus local STDIO and Docker deployments.

Limitations

Full mode exposes 100+ tools, which can consume a lot of context tokens; Minimal is the safer default.
The EU remote server and local server require a Postman API key (no OAuth there).
Advanced collaboration and Enterprise tools in Full mode require a corresponding Postman plan.

Alternatives

Bruno plus community MCP wrappers for an open-source, Git-friendly API client alternative.
Hoppscotch MCP community integrations for lightweight API testing from agents.
Direct use of the Postman API through a generic OpenAPI MCP server if you only need a subset of endpoints.