vitest-dev / vitest-dev/vitest
MCP server for test results and coverage
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17.1k
- Forks
- 2k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 92
Description
Clear and concise description of the problem
I'm often already running vitest when I'm developing and it would be nice if Vitest could provide the results and the coverage to the AI tools via MCP server. We already have the location of the output, the reporters and config. Or even the VSCode extension could provide it (though I personally run it separately anyways).
Suggested solution
Allow MCP configuration for major editors (VSCode, Intellij, Cursor) to check the output and validate whether the recently generated code works or not, whether the lines are covered or not and whether it can use any of the errors to continue fixing it.
Alternative
Also providing more documentation and instructions for AI would be helpful. Perhaps generating instruction files, based on your configuration, this could also help AI make its own MCP server too, if the instruction file would show where the output is located and how to read it. Though perhaps we need a different kind of Reporter that writes output in a way that AI is better at processing, if it is necessary to provide better communication.
Additional context
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue mentions Vitest reporters and configuration, existing output locations, and a possible VSCode extension, but names no files, tests, or entry points. Start by mapping how reporters expose test and coverage output; the requested MCP scope and a concrete definition of done still need clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai, devtools, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100