newman-ai-mcp
Related Servers
Alternatives to newman-ai-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables running Postman collections using Newman for conducting API tests and obtaining detailed result analysis via a standardized interface.184MIT
- AlicenseNot gradedqualityCmaintenanceExposes 11 agent-native QA tools over stdio so coding agents can discover a project, analyze risk, select the smallest relevant test set, generate and dry-run tests, triage failures, propose tiered heals, analyze flakes, generate quality reports, and evaluate release readiness. Planning and healing tools stay read-only or propose-only, while execution defaults to dry-run, keeping agent actions safe and evidence-backed.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to import and export Postman collections, author and execute API requests, run collection tests with pm.* scripts, manage environments and request history, and inspect legacy Postman data through 23 structured tools.5MIT
- AlicenseNot gradedqualityBmaintenanceTurns AI coding agents into senior QA engineers by generating black-box test matrices, manual test plans, UI/UX checklists, Page Object Model automation, API contract tests, and STLC strategies, plus sandboxed local test execution and defect triage from raw logs. Eight tools cover exploratory charters, WCAG audits, and Jira-ready bug reports, all with injection-proof command handling.12 npm2MIT
- AlicenseBqualityDmaintenanceAutomatically generates Postman collections from code directories by analyzing API endpoints and parameters, enabling easy testing, documentation, and sharing.143MIT
- FlicenseBqualityCmaintenanceTurns a Postman collection into a set of MCP tools served over stdio, so an AI agent can invoke the underlying HTTP API with resolved variables, inherited auth, and per-tool safety hints. It also lints the collection for agent-readiness and can spawn the server to verify read-only calls actually succeed.22-
TDQS
Scored across 9 tools
Most tools target distinct lifecycle stages (inspect, validate, import, generate tests, run, report, CI/CD, dataset, diagnose). The main overlap is run_newman_collection vs generate_newman_report, which both execute a collection; the descriptions distinguish them (control vs. report artifact), but an agent could still hesitate. inspect vs validate is also close but clarified as map-only vs static checks.
All nine tools follow a consistent snake_case verb_noun pattern (run_*, generate_*, inspect_*, validate_*, import_*, analyze_*). Naming is predictable and self-describing across the whole surface.
Nine tools is well within the ideal 3-15 range for a Postman/Newman workflow server. Each tool covers a distinct phase (author, validate, import, run, report, CI/CD, diagnose) and none feels redundant.
The surface covers generation, inspection, validation, execution, reporting, CI/CD, test data, and failure diagnosis — a full lifecycle. Minor gaps: there is no tool to apply/persist the corrected script that analyze_newman_failure suggests, and no explicit collection-editing or environment-management operation.