No user-submitted related servers found.
Scored across 42 tools
Most tools map clearly to a specific resource and action (collections, environments, mocks, specs, workspaces). A few directionally confusing pairs exist, such as syncCollectionWithSpec vs syncSpecWithCollection and getSpecFile vs getSpecDefinition, but their descriptions provide enough context to avoid frequent misselection.
The set mostly follows a verb_noun pattern with get/create/update prefixes. The main inconsistency is putCollection and putEnvironment using put instead of update, plus a few slightly awkward names like createCollectionResponse and getGeneratedCollectionSpecs, but overall the convention is recognizable and predictable.
42 tools is well above the 25+ threshold and feels heavy for an MCP tool set, even accounting for Postman's broad domain. While each tool may map to a real API endpoint, the surface would be more navigable with a leaner set or more consolidated operations.
The server covers create/get/update for many entities, but delete operations are almost entirely absent for collections, environments, mocks, specs, and workspaces. There are also highly specialized file and sync operations while basic lifecycle endpoints are missing, leaving significant gaps for common workflows.