Releases: postmanlabs/postman-mcp-server
v2.1.1
What's Changed
- docs: update README.md by @garciasdos in #35
- feat: publish npm package on release by @garciasdos in #36
Full Changelog: v2.0.1...v2.1.1
v2.0.1
What's Changed
- chore: docs for v2.0.0 by @garciasdos in #32
- fix: enabledResources within dist folder by @garciasdos in #33
- [PSTAPI-766] Update README file by @akinard-postman in #34
Full Changelog: v2.0.0...v2.0.1
v2.0.0
This release of the Postman MCP server syncs tools and infrastructure from postman-mcp-server, standardizes tool naming conventions, and introduces configurable resource filtering for better performance and flexibility.
New features
- Resource Filtering System — Added the
--fullflag and minimal tool configurations to enable you to choose between comprehensive (106 tools) or focused (37 tools) API access.
Improvements
- Standardized Tool Naming — Converted all tool names from kebab-case to camelCase for consistency (for example,
create-collectiontocreateCollection). - Enhanced Logging — Added tool count and configuration mode indicators to startup logs for better debugging visibility.
- Test Infrastructure — Updated integration tests to use camelCase tool names and added the
--fullflag for comprehensive testing. - Path Resolution — Fixed import path issues in compiled distribution files.
- Performance and stability — Reduced the default tool count from 106 to 37 for faster startup and reduced memory footprint.
Bug fixes
- Corrected path resolution for
enabledResourcesimport in distribution build. - Resolved test timeout issues by increasing test timeout to 30 seconds for workspace workflows.
Breaking changes
-
Tool Name Format — All tool names have changed from kebab-case to camelCase format. Update any existing integrations accordingly:
create-collectiontocreateCollectionget-workspacestogetWorkspacesdelete-environmenttodeleteEnvironment- …and similarly for all other tools.
-
Default Tool Set — By default, only minimal (37) tools are now available. Use the
--fullflag to access all 106 tools.
Upgrade notes
Review your tool invocations and update them to use the camelCase naming convention. Add the --full flag when starting the server to access to all available tools.
v1.2.1
What's Changed
- fix(docs): http <> https calls by @garciasdos in #24
- Update README.md for mention of 128 tool limit in VS Code by @akinard-postman in #26
- chore: sync tools from postman-mcp-server by @mcpopenapibot[bot] in #25
New Contributors
- @akinard-postman made their first contribution in #26
Full Changelog: v1.2.0...v1.2.1
v1.2.0
What's Changed
- feat: add environments crud tests by @garciasdos in #22
- refactor: version
dist/folder by @garciasdos in #23
Full Changelog: v1.1.0...v1.2.0
v1.1.0
What's Changed
- Handle windows requirements by @kaheidt in #20
- feat: add integration tests by @garciasdos in #21
New Contributors
Full Changelog: v1.0.1...v1.1.0
v1.0.0
What's Changed
- feat: first setup by @garciasdos in #1
- fix: update HTTP server URL and authorization method in README example by @garciasdos in #2
- feat: improve stdio setup by @davidespihernandez in #3
- fix: md by @akira28 in #4
- chore: use latest postman-api-oas by @garciasdos in #5
- refactor: simplify Docker and README instructions for STDIO server by @garciasdos in #6
- refactor: clean SSE version by @garciasdos in #7
- refactor: point to mcp.postman.com by @garciasdos in #8
- feat: add MCP HTTP streamable server installation instructions by @davidespihernandez in #10
- feat: add link the the public MCP collection to readme by @davidespihernandez in #13
- chore: sync tools from postman-mcp-server by @mcpopenapibot[bot] in #14
- chore: sync tools from postman-mcp-server by @mcpopenapibot[bot] in #15
New Contributors
- @garciasdos made their first contribution in #1
- @davidespihernandez made their first contribution in #3
- @akira28 made their first contribution in #4
- @mcpopenapibot[bot] made their first contribution in #14
Full Changelog: https://github.com/postmanlabs/postman-api-mcp/commits/v1.0.0