Labsco
MCP SERVER · OFFICIAL PROJECT

Postman API

by postmanlabs ↗

Generate a collection from an API specification, run it against an environment for test results, and sync the two back together when either side moves on.

API Specifications & HTTP Tooling✓ Verified
Summary
The round trip between a specification and the requests you actually send stops being manual.

generateCollection builds requests from a specification already in Spec Hub, generateSpecFromCollection goes the other way, and syncCollectionWithSpec and syncSpecWithCollection reconcile them afterwards, so design drift is a call rather than an afternoon. Several of those calls are asynchronous and hand back a polling link instead of a result, so whatever drives them has to check task status rather than assume the work landed. Decide the tool set before you wire it up: Minimal is the default, and Code and Full are a flag on the local command or a different path on the hosted URL.

What it is

Postman's own server over the Postman API: workspaces, collections, environments, mock servers and Spec Hub specifications, reachable as tools. It ships as four tool sets — Minimal by default, plus Code, Full and Learn.

What you get
  • Collections created and replaced against the Postman Collection v2.1.0 schema, with individual requests and saved responses added to them
  • A collection run by ID that returns test results and execution statistics, with an environment for variable substitution
  • Specifications created single- or multi-file in Spec Hub — OpenAPI, AsyncAPI, protobuf, GraphQL and Smithy — with their definitions and individual files read and updated
  • A collection generated from a specification, an OpenAPI 2.0, 3.0 or 3.1 specification generated from a collection, and sync in either direction once they drift
  • Mock servers created in a collection, retargeted to a different environment or server response, and published to public access
  • Workspaces and environments created, replaced and read, including the visibility setting that decides who can open a workspace
  • Search across requests, collections, workspaces, specs, flows, environments and mocks, scoped to your organization, the public Postman network, or both
Requirements

A Postman account. The hosted server at https://mcp.postman.com authorizes over OAuth, so there is no key to place; the local package and the EU servers at https://mcp.eu.postman.com take a Postman API key in POSTMAN_API_KEY instead. Locally it starts as npx @postman/postman-mcp-server, with --code or --full for the wider tool sets and --region eu for the EU region. getTaggedEntities needs an Enterprise plan. Apache-2.0.

Setup effort

One command plus a key — npx @postman/postman-mcp-server, then supply credentials