This is the Postman API mirrored rather than reshaped, which cuts both ways: the coverage is near-total, and the tool list is 99 entries long, so a client with a tight tool budget will feel it. The mirroring also shows in small seams — get_user_info and get_authenticated_user both return the authenticated user, and several calls answer differently depending on the team's plan rather than on what you asked for. Worth knowing before a bulk edit: update_collection replaces the whole collection, up to 20 MB, while patch_collection touches only the fields you send.
A server over the Postman API, 99 tools spanning workspaces, collections, environments, API definitions, mocks, monitors, roles, the Private API Network and billing.
- Collections created, forked to a workspace, merged back with a chosen strategy, patched field by field, and their items transferred into another collection
- The inside of a collection editable directly: folders, requests and saved responses each created, read, updated and deleted
- Environments on the same fork-and-merge model as collections, with updates that carry only the variables you changed
- API definitions with versions, schema files, comments and tags, and sync_collection_with_schema to bring a collection back in line with its schema
- Mock servers created, published or made private again, with call logs filterable by request method, path, response status code and date range
- Monitors created, updated and run, either blocking or async — an async run returns without stats, executions or failures
- Access administered in place: workspace and collection roles in up to 50 operations per call, collection access keys, Private API Network elements, and workspace tags
POSTMAN_API_KEY, and a Postman account whose plan carries what you intend to call — list_workspace_roles returns the roles available on the team's plan, and mock call log retention follows the plan as well. Updating collection roles requires the EDITOR role on that collection.
One command plus a key — npx -y @smithery/cli install postman-api-server --client claude, then supply credentials