Beyond the obvious collection and environment CRUD, it reaches the fork-merge-pull workflow, API schema files, role assignment and the Private API Network — the administrative half people usually do by hand in the web app. Two rough edges are worth knowing up front: environments need the full owner-prefixed uid, and what you can actually call depends on your plan and region.
A server over the Postman API, built from its published OpenAPI specification. It covers workspaces, collections, environments and APIs, plus the sharing and permission layers around them.
- Workspaces listed and opened, with tags read and updated
- Collections listed with filtering and pagination, created in Postman Collection v2.1.0 format, replaced wholesale up to 20 MB, or patched field by field
- Inside a collection: folders, requests and saved responses created, read and updated
- Version control on collections and environments alike — fork, list forks, merge a fork back, and pull parent changes down — plus item transfer between collections
- Environments created, updated with only the variables that changed, and deleted
- APIs created, updated and deleted, with versions, schemas, multi-file schema contents, tags and comments, and a collection synced against its schema
- Asynchronous operations followed through a task status check
- Access and permissions: collection access keys listed and deleted, workspace roles read and updated in batches of up to 50 operations, and collection roles read and updated
- Private API Network elements and folders added, updated, listed and removed
- Webhooks created to trigger a collection with a custom payload, plus billing account details and invoices, and a local health check of the server's own configuration
A Postman API key, generated at https://go.postman.co/settings/me/api-keys and saved as POSTMAN_API_KEY — it is shown once, and it reaches every Postman resource your account has permission for. Install it from npm as @postmanv3/postman-mcp-server, currently 0.2.1, with a postman-mcp-server binary, and run it over stdio. Two things to know before you rely on it: environment endpoints need the full uid in {ownerId}-{environmentId} form rather than the bare environment id, and some endpoints return 403 depending on your region and Postman plan. The project describes itself as under active development, with breaking changes expected.
One command plus a key — npm install -g @postmanv3/postman-mcp-server, then supply credentials