Repo Test Architect
About
Local-first MCP server that audits repository test architecture and produces evidence-backed findings, rankings, and test plans.
Details
- Author
- RepoAssay
- Downloads
- 1,048
- Categories
- Developer Tools
Jump to
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Repo Test ArchitectCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
{
"mcpServers": {
"repo-test-architect": {
"command": "npx",
"args": [
"--yes",
"repo-test-architect",
"mcp"
]
}
}
}
analyze_repository
Start here for an unfamiliar repository or a general test-architecture review. Detect and audit all project roots once, then return the complete deterministic summary, blockers, findings, ranking, plan, execution hints, verification commands, and stats. Prefer this over audit_repo unless one project root and adapter were explicitly selected.
list_adapters
List registered language adapters available to audit repositories.
list_project_detection_rules
List deterministic project marker rules and ignored directories used during project detection.
detect_projects
Detect project roots and matching adapters inside a repository.
audit_projects
Return raw per-project audit artifacts for all detected supported roots and report unsupported roots. Use when a downstream specialist tool needs project-audits/v1; for a complete first-pass review, prefer analyze_repository.
summarize_project_audits
Summarize an existing project-audits/v1 artifact. Use only when a compact coverage view is needed separately; analyze_repository already includes this result.
rank_project_candidates
Rank candidates from an existing project-audits/v1 artifact while preserving project identity. analyze_repository already includes this result.
generate_project_test_plan
Generate a project-aware plan from an existing project-audits/v1 artifact. analyze_repository already includes this result.
collect_project_findings
Collect concise top findings from an existing project-audits/v1 artifact. analyze_repository already includes this result.
analyze_project_test_placement
Analyze project-aware test placement from a project-audits artifact.
collect_project_stats
Collect local deterministic project audit stats for coverage, counts, risk and signal distributions, framework distribution, and adapter usage.
audit_repo
Audit one explicitly selected project root and return audit/v1. Use only when the caller selected a single adapter or project boundary; adapterId defaults to javascript. For an unfamiliar or complete repository review, use analyze_repository.
get_audit_graph
Validate and return an existing audit/v1 artifact unchanged; this does not scan a repository. Use audit_repo or analyze_repository for repository discovery.
generate_test_plan
Generate a deterministic test plan from an audit graph.
get_plan_execution_hints
Derive provider-neutral execution, context, parallel-safety, and repository-reasoning hints from a plan without invoking models or subagents.
explain_target
Explain one audit target by stable target id.
rank_test_candidates
Rank testable audit targets by risk reduction and maintenance cost.
analyze_test_placement
Analyze existing test placement from an audit graph and return advisory placement findings.
generate_selected_test
Return a structured deferred result. This tool does not generate or write test code while native generation remains disabled.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"repo test architect": {
"repo-test-architect": {
"command": "npx",
"args": [
"--yes",
"repo-test-architect",
"mcp"
]
}
}
}
}McpServers
{
"repo-test-architect": {
"command": "npx",
"args": [
"--yes",
"repo-test-architect",
"mcp"
]
}
}Audit-first test strategy tooling for codebases.
Repo Test Architect builds a deterministic audit graph before asking any model or agent to reason about tests. The goal is to identify repo-native, high-value test work from facts the tool can inspect locally: project roots, framework signals, existing tests, source classifications, blockers, and remaining risk.
- audit JavaScript/TypeScript, PHP, Python, Ruby, and Swift projects through supported adapters
- audit supported, bounded Kotlin/JVM fixtures through the same shared artifact model
- audit conventional Go modules and literal repository-containedgo.workmembers through a supported bounded adapter
- audit conventional Cargo packages and literal repository-contained workspace members through a supported bounded Rust adapter
- audit one conventional SDK-style C# test project or one unique literal production/test project edge, including bounded native xUnit MTP-v2 and MSTest.Sdk v4 ownership, literal and one-hop root-aliased target frameworks, one repository-contained direct*.cscompile include, finite target-conditioned package shapes, bounded nearest-file build and central-package props, exact immutable test-field receivers, stable direct-call results, inlineoutresults, framework exception and collection/string assertions, one-hop test helpers, and guarded well-knownSystemtype collisions, through a supported bounded .NET adapter
- audit one conventional Composer/PSR-4 project with PHPUnit through a supported bounded PHP adapter
- audit one conventional Mix application with exact MixProject/Mixfile, bounded source and Mix-task ownership, literal local ExUnit wrapper discovery, and test-body evidence through a supported bounded Elixir adapter
- detect polyglot project roots and report unsupported ecosystems without hiding them
- produce a complete repository analysis, findings, ranking, plan, execution hints, and verification commands in one audit pass
- classify source files by likely test value and defer low-value direct tests
- rank candidates and generate test plans from the audit graph
- derive provider-neutral execution, context, parallel-safety, and repository-reasoning hints without selecting models or spawning subagents
- analyze conservative test placement findings across project boundaries
- collect project-level stats for coverage, candidate counts, frameworks, commands, and adapter usage
- provide disabled-by-default local MCP diagnostics, safe internal-error report IDs, runtime checks, and inspectable sanitized bundles without external reporting
- expose the same deterministic behavior through CLI commands, a local invoke harness, and a stdio MCP SDK server
- lock behavior with golden snapshots, model-consistency scenarios, package checks, and cross-OS CI
Native test generation is intentionally deferred.generate_selected_testreturns a structured deferred artifact until adapter-specific generation policy and repair-loop fixtures exist.
Repo Test Architect1.0.0-beta.1is available as an opt-in public beta. The unqualified npm command remains on0.3.0while the beta is evaluated. Treat its findings as evidence-backed review input rather than an automatic instruction to change a repository. See thebeta release notes.
npx --yes repo-test-architect doctor npx --yes repo-test-architect analyze .
Try the public beta without changing the default npm channel:
npx --yes repo-test-architect@beta doctor npx --yes repo-test-architect@beta analyze .
Or install the CLI and MCP server binaries:
npm install --global repo-test-architect repo-test-architect doctor repo-test-architect analyze .
Add the local stdio MCP server to an MCP-capable client:
{ "mcpServers": { "repo-test-architect": { "command": "npx", "args": [ "--yes", "repo-test-architect", "mcp" ] } } }
To opt into the public beta, pin the npmbetachannel in the MCP configuration:
{ "mcpServers": { "repo-test-architect": { "command": "npx", "args": [ "--yes", "repo-test-architect@beta", "mcp" ] } } }
The client launches the server locally. Repository source stays on the machine unless the client or another configured tool sends it elsewhere. Connected models receive instructions to start withanalyze_repositoryfor a general repository review. SeeMCP client configandagent install pathsfor global-install, local-checkout, and host-specific guidance.
For a human-readable review of the current repository:
analyzedetects every project root, runs each supported adapter once, and derives the audit summary, top findings, candidate ranking, test plan, execution hints, project stats, and verification commands. Markdown stays compact; JSON preserves the complete evidence bundle:
npx --yes repo-test-architect analyze . --format json npx --yes repo-test-architect analyze . --changed
Runrepo-test-architect --helpfor the short command map orrepo-test-architect <command> --helpfor options. The[CLI referencedocuments the full surface.
For an MCP-connected model, the equivalent default isanalyze_repository. Use narrower tools only when the request asks for one artifact or already supplies an audit artifact.
…
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
