From 9726a690e6c23a9540a87725946f662c09fd57bf Mon Sep 17 00:00:00 2001 From: Christos Gkoros Date: Tue, 14 Apr 2026 10:49:11 +0300 Subject: [PATCH] fix(postman): always pass environmentId to runCollection regardless of API target The previous steering instruction "Use the environment for local testing if it exists" caused the agent to skip passing environmentId when the target API was remote (e.g. AWS API Gateway, staging, production). This left environment variables like {{base_url}} unresolved, causing all requests to fail. Also clarified the "server must be running" check: it only applies to local servers, not remote APIs. Fixes postmanlabs/postman-mcp-server#130 --- postman/steering/steering.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/postman/steering/steering.md b/postman/steering/steering.md index 51c6508..7574eaa 100644 --- a/postman/steering/steering.md +++ b/postman/steering/steering.md @@ -20,7 +20,7 @@ inclusion: always - You are not allowed to use curl or any other API clients except Postman. - A Collection ID is required - Read the .postman.json file if it exists. -- Use the environment for local testing if it exists. An Environment ID is required -- The server must be running first +- Always pass the environment ID to `runCollection` if one is available, regardless of whether the target API is local or remote. Environment variables must be resolved for tests to work correctly. +- If the target API is a local server, ensure it is running before executing the collection. For remote APIs (e.g. staging, production, cloud endpoints), skip this check. - After running, display a summary of the results and a breakdown by endpoint - If any endpoint is failing, offer to investigate and fix the error