What's Changed

Synced tools, entrypoint, and tests from postman-mcp-server (#155).

New tools

Mock Server Responses

• createMockServerResponse
• getMockServerResponse
• getMockServerResponses
• updateMockServerResponse
• deleteMockServerResponse

Monitors

• listMonitorExecutions
• listRunsForExecution
• getMonitorRunResults

Tool set changes

• full set: added Mock Server Response tools and new Monitor execution tools. Removed the standalone Context tools group (still available in the code set).
• minimal set: added searchPostmanElements.
• code set: added the new Monitor execution tools; removed searchPostmanElementsInPrivateNetwork.

Other updates

• Refreshed analytics tools (getAnalyticsData, getAnalyticsMetadata).
• Updated spec tools (createSpec, createSpecFile, updateSpecFile, getSpecDefinition, generateSpecFromCollection, syncSpecWithCollection).
• Tweaks to createCollectionRequest, updateCollectionRequest, putCollection, updateMock, searchPostmanElements.
• Template renderer utilities updated (errorTemplateRenderer, templateRenderer).
• Integration tests refreshed (src/tests/integration/direct.test.ts).
• Instructions.md resource updated.

Full Changelog: v2.8.9...v2.9.0

New Features

MCP Instructions Resource

Added a built-in Instructions resource (postman://instructions) that provides MCP clients with comprehensive context about Postman concepts and a structured workflow for API discovery.

• Covers all core Postman elements: workspaces, collections, environments, APIs, mocks, monitors, and tags
• Includes a decision framework for choosing between Private and Public API Network searches
• Provides step-by-step guidance for navigating collections after discovery
• Server instructions now encourage MCP clients to read this resource before answering API-related questions

Improvements

Collection Creation Validation

Added a minLength constraint to the collection name field in createCollection, preventing the creation of collections with empty names.

Code Generation Parameter Resolution

Made the parametersResolution field required in generateCollection with a default value of "Example". The "Schema" strategy is no longer supported by the Postman API and will return an error.

Case-Insensitive Enum Handling

Updated the code generator to normalize uppercase-only enum values case-insensitively. LLM agents frequently submit lowercase values (e.g., "yaml" instead of "YAML", "openapi:3.1" instead of "OPENAPI:3.1"), which previously caused validation failures.

• Affected tools: createSpec, generateSpecFromCollection, updateSpecFile, createCollectionRequest, updateCollectionRequest, and related response tools

Enterprise Plan Notice for Tags

Added a prominent Enterprise plan requirement notice to the getTaggedEntities tool description, so LLM agents understand that a 404 response on Free, Basic, or Professional plans is a plan restriction, not a broken tool.

Improved patchCollection Guidance

Added LLM-facing guidance to patchCollection warning against parallel calls on the same collection and clarifying which collection.variable fields to include.

Bug Fixes & Dependencies

• Fixed patchCollection silently injecting disabled: false into every collection.variable item due to Zod .default() behavior, causing "invalid parameters" API errors. PATCH operations now use .optional() instead of .default() so omitted fields stay absent in the request body.

Full Changelog: v2.8.2...v2.8.4

New Features

Analytics Tools

Two new MCP tools for querying Postman analytics data:

• getAnalyticsData — Retrieve analytics data (e.g., API usage metrics, collection runs) with flexible query parameters.
• getAnalyticsMetadata — Fetch metadata about available analytics dimensions and metrics.

Error Template System

Introduced a Nunjucks-based error template system that provides human-friendly, actionable error messages when API calls return common errors (e.g., 404 Not Found).

• Created error templates for 8 key resources: getCollectionFolder, getCollectionRequest, getCollectionResponse, getEnvironment, getMock, getMonitor, getSpec, and getWorkspace
• Each template gives LLM-friendly guidance on what went wrong and how to resolve it

Improvements

Private API Network (PAN) Endpoint Renaming

Standardized all Private API Network endpoint names to be clearer and more descriptive:

All PAN endpoint descriptions now include explicit warnings that these tools are for Private API Network management only, not for general workspace operations.

Postman API Spec Alignment

Regenerated the MCP server tools from the latest Postman API OpenAPI specification:

• New tools: updateCollectionResponse, addWorkspaceToPrivateNetwork, respondPrivateNetworkAddRequest
• Removed deprecated tools: postPanElementOrFolder, updatePanElementOrFolder
• Updated schemas across multiple collection, workspace, and documentation tools
• Made the collection field optional in mock object schemas (was previously required)
• Significant reduction in spec size from schema deduplication and cleanup

Bug Fixes & Dependencies

• Updated @modelcontextprotocol/sdk to v1.27.1, picking up upstream bug fixes and improvements
• Fixed public repo sync to include new error template files

Full Changelog: v2.7.1...v2.8.1

Full Changelog: v2.8.0...v2.8.1