postman-mcp-server
Related Servers
Alternatives to postman-mcp-server
No user-submitted related servers found.
Related Servers
- 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.15 npmMIT
- AlicenseBqualityBmaintenanceConnects AI agents to Postman workspaces, collections, API specifications, and environments for API testing, management, and client code generation.427,743 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create, manage, and interact with Postman collections, workspaces, environments, and API requests directly from conversations.52 npm5MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that provides seamless integration with the Postman API, enabling AI assistants and applications to interact with Postman workspaces, collections, requests, environments, and folders programmatically.1915 npm31MIT
- AlicenseBqualityDmaintenanceEnables running Postman collections using Newman for conducting API tests and obtaining detailed result analysis via a standardized interface.128 npm84MIT
- AlicenseAqualityDmaintenanceIntegrates Postman with Cursor IDE to manage collections and requests through natural language. It features specialized tools for automatically migrating API endpoints and metadata directly from .NET controller code into Postman collections.852 npmMIT
TDQS
Scored across 99 tools
With 99 tools, many CRUD operations for different entities (API, collection, environment, etc.) exist, but descriptions generally clarify their purpose. Some overlapping concepts like 'add_api_collection' vs 'create_collection' could cause confusion, but overall distinct.
Most tools follow a consistent 'verb_noun' pattern (e.g., create_api, delete_api), but a few deviations like 'add_pan_element', 'resolve_comment_thread', and 'sync_collection_with_schema' break the pattern.
99 tools is excessively high for a single server, even considering Postman's broad scope. Many tools could be consolidated (e.g., using parameters instead of separate tools), making it hard for agents to navigate.
The tool surface covers all major Postman resources (APIs, collections, environments, mocks, monitors, schemas, webhooks, etc.) with full CRUD, plus forks, merges, roles, tags, comments, and PAN management. No obvious gaps.