Postman MCP Server
Related Servers
Alternatives to Postman MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create, manage, and interact with Postman collections, workspaces, environments, and API requests directly from conversations.31 npm5MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Postman workspaces, collections, requests, responses, and monitors through the Postman API. Allows users to manage API collections, create and update requests/responses, and execute monitors directly from chat.14 npmMIT

Postmanofficial
AlicenseBqualityAmaintenancePostman’s remote MCP server connects AI agents, assistants, and chatbots directly to your APIs on Postman. Use natural language to prompt AI to automate work across your Postman collections, environments, workspaces, and more.428,327 npm315Apache 2.0- FlicenseNot gradedqualityDmaintenanceAutomatically converts Postman API collections into MCP-compatible tools for AI assistants. Enables users to interact with any API through natural language by generating JavaScript tools from Postman requests.-
- AlicenseNot gradedqualityDmaintenanceEnables uploading and managing Postman collections, environments, and data files for API testing. Integrates with AI hosts via Model Context Protocol for test execution and result management.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to dynamically discover and interact with APIs through Swagger/OpenAPI specifications and Postman collections using a strategic four-tool approach. It streamlines API integration by providing universal tools for endpoint discovery, detailed request information, and authenticated execution.1-
TDQS
Scored across 42 tools
Several inverse operation pairs are easy to confuse, such as syncCollectionWithSpec/syncSpecWithCollection, getSpecCollections/getGeneratedCollectionSpecs, and generateSpecFromCollection/generateCollection. The large set of spec-related getters (getSpec, getSpecDefinition, getSpecFile, getSpecFiles) also creates unclear boundaries that could lead to misselection.
Most tools follow a snake_case verb_noun pattern, but the set mixes create/generate, get/getAll, and update/put (putCollection/putEnvironment vs. update*). The sync and generation pairs use confusingly swapped phrases, making the naming readable but noticeably inconsistent.
42 tools is well beyond the typical 3-15 well-scoped range and falls into the 25+ category. Although Postman covers many resource types, this many tools creates significant selection overhead without clear grouping.
Coverage spans collections, specs, environments, mocks, and workspaces with create/get/update operations. However, there are no delete operations at all—such as deleteCollection, deleteEnvironment, deleteWorkspace, or deleteSpec—which is a notable lifecycle gap that agents cannot work around.