Pare Test
Run the repo’s test suite through MCP with auto-detected pytest, Jest, Vitest, or Mocha and get typed pass/fail JSON for agent-driven ship checks.
Overview
io.github.Dave-London/pare-test is an MCP server for the Ship phase that auto-detects pytest, Jest, Vitest, or Mocha and returns typed JSON test results.
What is this MCP server?
- Auto-detects pytest, Jest, Vitest, or Mocha and runs the appropriate test command
- Returns typed JSON summarizing failures, counts, and status for agents
- stdio @paretools/test npm package at version 0.8.1
- Supports polyglot solo stacks that mix Python APIs and JavaScript frontends
- Complements pare-python lint tools in a ship-ready agent workflow
- Server version 0.8.1
- Supports four frameworks: pytest, Jest, Vitest, Mocha
- Package @paretools/test, stdio MCP transport
Community signal: 128 GitHub stars.
What problem does it solve?
Agents struggle to choose the right test command and to interpret sprawling test runner output across mixed Python and JavaScript repos.
Who is it for?
Builders who want one MCP entry for multi-framework test runs and agent-readable results before deploy or merge.
Skip if: Projects with exotic custom test harnesses the detector cannot recognize, or teams that only run tests in remote CI without local agent loops.
What do I get? / Deliverables
With @paretools/test configured, your agent gets framework-aware test runs and structured failure data for quicker pre-ship verification.
- Auto-detected test runs with typed JSON status and failure details
- Agent-ready pre-ship test verification without manual log parsing
Recommended MCP Servers
Journey fit
Automated test execution and interpretation belong to shipping safely before merge or release, even when tests are written earlier. Testing is the canonical shelf because the server’s purpose is framework detection and structured test run output, not authoring tests in isolation.
How it compares
Test-runner MCP with JSON summaries, not a test authoring skill or hosted CI product.
Common Questions / FAQ
Who is io.github.Dave-London/pare-test for?
It is for solo developers using MCP agents who need automatic test framework detection and structured results on local or agent-driven test runs.
When should I use io.github.Dave-London/pare-test?
Use it in the ship phase when you want the agent to execute pytest, Jest, Vitest, or Mocha and act on pass/fail JSON before releasing or merging.
How do I add io.github.Dave-London/pare-test to my agent?
Install @paretools/test via npm, add the stdio MCP server to your client config, and ensure the project's test runner and dependencies are installed locally.