run-collection
Run a Postman Collection using Newman
LABSCO SUMMARY
The API suite runs where you are changing the API.
A collection someone else wrote and an environment file are the whole input, so the assertions that guard CI can be pointed at a local change mid-conversation. iterationCount repeating the run is how an intermittent failure separates itself from a broken endpoint.
What it is
One tool that executes a Postman collection through Newman, taking the collection, an optional environment and globals, and a number of iterations.
What you get
- A Postman collection executed through Newman and its result returned in the session
- An environment file and a globals file supplied alongside the collection
- The whole run repeated for an iterationCount you set
Requirements
npx on your PATH and a Postman collection to run. No account and no key.
Setup effort
One command — npx -y mcp-postman
USE CASES
01
Checking an API change against the collection that guards it
The collection and its environment file are the whole input, so the assertions that run in CI can be pointed at a local change without leaving the conversation.
02
Separating an intermittent failure from a broken endpoint
iterationCount repeats the whole run, which turns a single red result into evidence about whether it happens every time.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-postman": {
"command": "npx",
"args": [
"-y",
"mcp-postman"
]
}
}
}npx
TERMINAL
npx -y mcp-postman
