No user-submitted related servers found.
Scored across 42 tools
Most tools are resource/action specific, but the spec and collection lifecycle has overlapping operations such as generateSpecFromCollection, generateCollection, getGeneratedCollectionSpecs, getSpecCollections, syncCollectionWithSpec, and syncSpecWithCollection. Descriptions help, but an agent can easily misselect among these closely related tools.
Names are consistently camelCase and mostly follow predictable verb-noun patterns such as createCollection, getWorkspace, updateMock, and runCollection. Minor deviations exist, including putCollection/putEnvironment instead of update*, and getAllSpecs versus other get* variants.
The 42-tool surface is large for an agent-facing MCP server and includes many fine-grained operations across collections, specs, mocks, environments, and workspaces. While Postman is a broad product, this count feels heavy and increases selection burden.
The surface covers many create/get/update workflows across major Postman entities, but delete operations are conspicuously absent for collections, requests, responses, environments, mocks, specs, and workspaces. Agents can perform core creation and reading tasks but will hit dead ends for cleanup and full lifecycle management.