Code2Postman MCP
Related Servers
Alternatives to Code2Postman MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConverts REST API code (like NestJS controllers or FastAPI endpoints) to Postman collections and environments, helping developers automatically sync their API endpoints with Postman.212 npmMIT
- 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 gradedqualityCmaintenanceAnalyzes API codebases from GitHub and Bitbucket repositories to generate Postman collections, business reports, and detailed code insights. Supports multiple frameworks including FastAPI, Spring Boot, Flask, Express, and OpenAPI/Swagger specifications.MIT
- AlicenseNot gradedqualityAmaintenanceSync your API code into Postman collections — body, params, auth, responses, tests, and examples — with zero manual fill, straight from Claude Code.1MIT
- FlicenseBqualityDmaintenanceGenerates API documentation in Confluence from Swagger/OpenAPI specs or NestJS controller files, including automatic Postman collection generation.9-
- AlicenseNot gradedqualityBmaintenanceAnalyzes API requirements and source code, evaluates existing Postman test coverage, and generates or updates test automation with an optional draft pull request on GitHub.8 npmMIT
TDQS
Scored across 14 tools
Most tools have distinct purposes, e.g., adding items to root vs folder, managing variables vs events. The generic file tools (read_file, get_tree_directory) are clearly separate from Postman-specific tools, so agents can distinguish between them.
Naming is inconsistent: some tools use 'postman_collection' (e.g., add_postman_collection_item) while others omit it (e.g., add_item_to_folder). Verbs vary (add, create, read, delete, update, get) without a consistent pattern, mixing snake_case and multi-word names.
14 tools cover the core workflows of creating and managing Postman collections from code. The count is well within the 3-15 range and each tool serves a specific purpose without redundancy.
The set covers creation, reading, and deletion of items, variables, and folders, but lacks update operations for items and variables, and does not support deleting folders or variables. Some lifecycle steps are missing.