Summary
Gives Claude local test execution and coverage feedback for Python and JavaScript projects. Exposes six tools: run_pytest, run_jest, run_single_test, parse_test_output, get_coverage_summary, and a health check. Built for the wayfinder codebase onboarding agent as the verification layer alongside mcp-repo-mapper and mcp-ast-explorer. Runs pytest with JSON output via pytest-json-report, Jest via npx with JSON flags, and normalizes both into a single TestRunResult schema. Includes subprocess timeouts and POSIX resource limits for CPU and memory. Coverage summaries work through pytest-cov. Reach for this when your agent needs to verify code claims against real test execution instead of guessing from static analysis.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
mcp-test-runner
MCP server for deterministic local test execution and normalized test result reporting.
mcp-test-runner is the verification layer for codebase onboarding agents. It exposes focused MCP tools for running pytest and Jest, parsing test output, and summarizing coverage so downstream agents can mark claims as verified, unverified, or contradicted by real execution.
Codebase Onboarding Stack
mcp-test-runner is the verification layer in a three-server MCP tool stack for Project 6 wayfinder, a codebase onboarding agent.
mcp-repo-mappermaps repository structure, languages, entry points, framework evidence, and Python dependency edges.mcp-ast-explorerprovides symbol-grounded Python definition, signature, reference, call-chain, and class-hierarchy lookups.mcp-test-runnerruns local pytest/Jest checks and coverage summaries so agent claims can be verified against execution.
In wayfinder, this server turns high-risk code understanding claims into verified, unverified, or contradicted evidence from real test execution.
Status
This repository is a Python-first v1 MCP test runner. It supports bounded pytest execution, Jest command execution, single-test targeting, pytest coverage summaries, and normalized pytest/Jest JSON parsing.
The server does not use an LLM. Test results come from subprocess execution and structured parser output.
Tools
| Tool | Purpose |
|---|---|
health() | Returns ok for smoke checks. |
run_pytest(path, test_filter?, timeout_seconds?, cpu_seconds?, memory_mb?) | Run pytest in a bounded working directory and return raw command output. |
run_jest(path, test_filter?, timeout_seconds?, cpu_seconds?, memory_mb?) | Run Jest through npx jest and return raw command output. |
run_single_test(path, test_id, framework?, timeout_seconds?, cpu_seconds?, memory_mb?) | Run one pytest node id or one Jest test-name pattern. |
parse_test_output(stdout, framework) | Normalize test runner JSON output. |
get_coverage_summary(path, framework?, timeout_seconds?, cpu_seconds?, memory_mb?) | Return pytest-cov JSON coverage totals. |
Supported Scope
- Python 3.11+ package.
- FastMCP 2.x server.
- pytest execution with JSON report output via
pytest-json-report. - Jest command execution via
npx jest --json --outputFile. - pytest and Jest JSON normalization into one
TestRunResultschema. - Single pytest node id execution and Jest test-name targeting.
- pytest-cov coverage summary from
.coverage.json. - Subprocess timeout plus POSIX
resource.setrlimitCPU / memory caps.
Current Limitations
- v1 does not use Docker. It uses cwd validation, subprocess timeouts, and POSIX resource limits.
- Resource limits require a POSIX platform that supports
resource.setrlimit. - Jest execution expects Node.js plus project-local or
npx-resolvable Jest. - Jest single-test targeting uses
--testNamePattern; it does not parse Jest file-specific node ids. - Coverage summary is pytest-only in v1.
- Tools return raw command output for execution; call
parse_test_outputto normalize framework JSON.
Local Development
Install dependencies:
uv sync --extra dev
The PyPI distribution name is lovranran-mcp-test-runner because mcp-test-runner is already taken on PyPI. The installed console script remains mcp-test-runner.
Run the MCP server:
uv run mcp-test-runner
Run verification:
uv run ruff check .
uv run mypy
uv run pytest
License
MIT
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →