test-inventory-mcp
Related Servers
Alternatives to test-inventory-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to run, debug, and inspect Playwright end-to-end tests, returning structured pass/fail stats, failure diagnostics with actionable fix hints, live DOM inspection, selector validation, visual diffs, and flakiness verdicts instead of raw test output.111,816 npmMIT
- AlicenseAqualityBmaintenanceAllows LLM agents to query Playwright JSON test results for run summaries and failure information.2MIT
- AlicenseBqualityCmaintenanceEnables AI coding agents to perform evidence-based, read-only audits of supported software projects by exposing bounded project inventory and static-analysis findings for discovery, code review, integration tracing, security, and tests. Reports are returned as Markdown or JSON directly in the tool response, with no code executed or files written.821 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to run a project's pytest, unittest, jest, or vitest suites and get back compact structured results with trimmed tracebacks, collection errors kept apart from real failures, and the slowest tests. Agents can then re-run just the failures, expand one failure with local variables, repeatedly execute a single test to judge flakiness, and inspect Python coverage gaps, all under a hard timeout that kills the whole process tree.7MIT
- AlicenseAqualityBmaintenanceEnables AI agents to drive Playwright-based browser automation for UI testing, returning JSON/HTML reports with screenshots without server-side LLM or test scripts. https://easy-ui-mcp.vercel.app/261MIT
- AlicenseAqualityDmaintenanceWraps existing test frameworks (Jest, Vitest, Pytest) and exposes structured, LLM-optimized results via MCP tools with progressive disclosure and diff-aware execution.111MIT
TDQS
Scored across 5 tools
The summary/find/get trio covers counts vs. filtered lists vs. full records, and the descriptions explicitly route the agent between them ("use test_summary for counts and get_tests for every key of a few ids"). scan_diagnostics and diff_inventories are clearly separate operations with no overlap.
All names are snake_case two-token identifiers, which is predictable and readable. The only deviation is test_summary, which leads with a noun while the other four use a verb (find_, get_, scan_, diff_), a minor inconsistency in an otherwise uniform set.
Five tools is well within a healthy range and each one covers a distinct, substantive capability (aggregate counts, filtered listing, full record retrieval, diagnostics, historical diff). No thin wrapper tools and nothing redundant.
The surface covers the read-only inventory lifecycle well: counting, listing, drilling into records, surfacing scan errors, and comparing snapshots. One workaround gap: diff_inventories requires "complete saved JSON scans" but no tool produces or exports such a snapshot, so the diff workflow depends on an out-of-band step.