postman-mcp-server
Postman MCP Server
MCP exposes workspace resources directly to an agent. Existing collections, specs, examples, and environments provide maintained API knowledge; fetching the relevant entity preserves that context when a local CLI workflow is not available. For repository edits and Git review, prefer the local workflows in api-engineer when available.
Each tool definition exposed to the model consumes context whenever it is
included in a request. Prefer the smallest available toolset that covers the
task; expanding to every tool can crowd out the API evidence needed to reason.
When exposed, call getEnabledTools to inspect the active toolset before
diagnosing a missing operation. Otherwise use the host's discovered tools and
report that limitation. Do not infer availability from reference tool names or
assume a client can switch a route pinned to a specific MCP endpoint.