Local test execution and coverage summaries for onboarding agents.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON â–¾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for MCP Test Runner, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Documentation Overview
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:
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:
Run verification:
License
MIT
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
Last commit
3mo ago
Most recent push to the default branch.
Directory activity
1 views
Config copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about MCP Test Runner
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/mcp-test-runner)HTML Embed
<a href="https://allmcps.com/mcp/mcp-test-runner"><img src="https://allmcps.com/api/badge/mcp-test-runner?style=directory" alt="MCP Test Runner on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
7/8 checks healthy over the last 45d
29Quality signal: Emerging · 29/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools11/30
Adoption & activity1/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.