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
202,295 tools. Last updated 2026-06-14 12:08
"Vitest" matching MCP tools:
- Verify code changes by running the test suite with auto-detected runner (Pest, PHPUnit, Jest, etc.). Specify filter or path to narrow tests, and get exit code, runner name, and output tail.MIT
- Generate test skeletons for source code using Jest, pytest, or vitest. Writes new test stubs for public functions to scaffold tests in untested modules.MIT
- Run smoke tests to validate project builds and confirm tests pass before commit or deploy. Automatically detects pytest, jest, vitest, or mocha from project configuration.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
- Search Forge's stored patterns to find previously learned conventions, failure modes, and successful approaches for project guidance and debugging.MIT
Matching MCP Servers
- AlicenseAqualityCmaintenanceAI-optimized Vitest interface that provides structured test output, visual debugging context, and intelligent coverage analysis for more effective AI assistance with testing.Last updated438416MIT
- 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.Last updated453MIT
- Execute terminal commands and wait for results. Use the run action to send input, wait for a pattern or quiet period, then return output. For incremental reading or sending, use read/send actions.MIT
- Save learned patterns like test commands and failure diagnostics to persistent memory for future project runs, preventing duplicate entries to maintain efficiency.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
- 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
- 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
- Run tests (Vitest, Jest, Pytest, Cargo, Go) and get pass/fail results with failure locations. Uses a 30-second cache.MIT
- Generate unit tests for any code snippet using Jest, Vitest, or Mocha. Automatically includes boundary cases and mocks.MIT
- Generate a complete Helix-pattern web component scaffold including Lit class, CEM annotations, test stub, Storybook story, and CSS. Auto-detects tag prefix and base class from the library's Custom Elements Manifest.MIT
- Specify the absolute path to the project root directory as a necessary first step to enable all subsequent Vitest testing operations.MIT
- Generates a React component with shadcn/ui patterns, optionally including TypeScript types, Vitest tests, and Storybook stories.MIT
- Generate intelligent tests to achieve 80%+ code coverage for target files using Jest, Vitest, or Mocha frameworks. Includes options for edge cases and accessibility testing.MIT
- Generate test stubs from acceptance criteria in SPEC.md and TASKS.md, with traceability to requirement IDs. Supports six test frameworks: vitest, jest, playwright, pytest, junit, xunit.
- Analyze test coverage metrics for JavaScript/TypeScript repositories to identify gaps and improve testing quality by detecting frameworks like Jest, Vitest, and Cypress.