Execute Vitest tests with structured JSON output and optional log capture. Supports monorepos through workspace configuration. Set the project root before use and specify a test target to prevent full project runs.
MIT
456,957 tools. Updated 2026-08-14 07:04
"Vitest" matching MCP tools:
- Run the project's Vitest tests under a safe shell: fixed arguments, 120s timeout, and capped output. Filter by name pattern or path to narrow the test run.MIT
- Generate test skeletons for public functions in untested modules. Writes Jest, pytest, or vitest stubs alongside source files.MIT
- Run smoke tests automatically before commit or deploy. Detects pytest, jest, vitest, or mocha and executes the test suite from project config.MIT
- Search Forge's stored patterns to find previously learned conventions, failure modes, and successful approaches for project guidance and debugging.MIT
- Execute JavaScript to query Gaffer test and coverage data, analyze project health, debug failures, and identify untested code areas using codemode API functions.MIT
Matching MCP Servers
- AlicenseAqualityDmaintenanceAI-optimized Vitest interface that provides structured test output, visual debugging context, and intelligent coverage analysis for more effective AI assistance with testing.476117MIT
- Alicense-qualityDmaintenanceEnables AI assistants to run Vitest tests and analyze code coverage, supporting test-driven development workflows with tools for test execution and coverage analysis.463MIT
- Execute commands in a terminal window, read structured output, and wait for patterns or quiet periods. Use 'run' for complete command execution with result.MIT
- Automate command-line interactions: send input, read output, and run commands to completion with pattern or exit detection.MIT
- Query real GitHub migration data to identify which packages developers are switching from and to. Validate technology choices using ground-truth analysis of package.json and requirements.txt diffs.MIT
- Save learned patterns like test commands and failure diagnostics to persistent memory for future project runs, preventing duplicate entries to maintain efficiency.MIT
- Submit autonomous tasks for AI to execute continuously until completion criteria are met. Define purpose, desired outcomes, verifiable completion conditions, and project context.MIT
- Analyze test coverage to identify untested lines, functions, branches, and statements. Get actionable insights and recommendations for improving coverage, with automatic exclusion of non-production files.MIT
- Scaffold a production-ready Express.js + TypeScript backend project with your choice of ORM, Zod validation, Swagger docs, Docker, ESLint, Vitest, and more.MIT
- Discover test files matching .test.* and .spec.* patterns recursively. Get structured file info with absolute and relative paths to understand test organization and coverage. Optionally limit search to a specific directory.MIT
- Write and run tests for specified modules, files, or behaviors without modifying production code. Supports custom frameworks and run verification.MIT
- Retrieve the current status and timing details of a previously submitted browser test job. Indicates if job is created, queued, executing, completed, or failed.MIT
- Retrieve a complete test report for finished jobs, including step-by-step results, pass/fail summary, root-cause analysis, and UX improvement insights.MIT
- Run tests (Vitest, Jest, Pytest, Cargo, Go) and get pass/fail results with failure locations. Uses a 30-second cache.MIT
- Run allowlisted verification commands like tests and linters for a task, recording results as review evidence.MIT
- Run test commands and get structured output showing only failures. Detects Jest, Vitest, pytest, cargo-test, and go-test automatically.MIT