Test
Let your agent detect pytest, Jest, or Vitest in the repo and run tests with structured pass or fail output before you ship.
Overview
io.github.Dave-London/test is a MCP server for the Ship phase that auto-detects pytest, Jest, or Vitest and returns structured test run results to your agent.
What is this MCP server?
- Auto-detects pytest, Jest, and Vitest in the project
- Returns structured test results suitable for agent reasoning
- Published as @paretools/test on npm (v0.8.0) with stdio transport
- Reduces ad-hoc shell test commands in agent loops
- Pairs with Pare search MCP for find-code-then-verify workflows
- npm package @paretools/test version 0.8.0
- Supports three frameworks named in the description: pytest, Jest, and Vitest
- stdio MCP transport per published server schema
Community signal: 128 GitHub stars.
What problem does it solve?
Agents struggle to pick the right test command and interpret messy console output across Python and JavaScript projects.
Who is it for?
Solo builders on polyglot or JS/Python stacks who want one MCP test runner instead of custom scripts per repo.
Skip if: Pure production-only monitoring workflows, repos with exotic runners outside pytest/Jest/Vitest, or teams that forbid agents from executing tests locally.
What do I get? / Deliverables
After registering @paretools/test, your agent can run the detected framework and consume structured pass or fail data before you merge or release.
- Detected framework test execution via MCP
- Structured pass or fail summaries for agents
- Repeatable local regression runs without custom wrappers
Recommended MCP Servers
Journey fit
Running and interpreting automated tests is core Ship work—this MCP sits on the testing subphase rather than idea research or production monitoring. Framework auto-detection and structured test results map directly to pre-release verification, not to code search or uptime dashboards.
How it compares
MCP test runner with framework detection, not a load-testing harness or a static code-review skill.
Common Questions / FAQ
Who is io.github.Dave-London/test for?
It is for developers using AI coding agents who want automated pytest, Jest, or Vitest runs with structured results during ship prep.
When should I use io.github.Dave-London/test?
Use it in Ship/testing after code changes when you need a fast regression check before merge, tag, or deploy.
How do I add io.github.Dave-London/test to my agent?
Install @paretools/test from npm, add the MCP server with stdio transport in your agent config, and ensure project dependencies for your detected framework are installed.