Repo Test Architect MCP server

Read from the package source without running it. The installed server may list more.

• analyze_project_test_placement

  Derive advisory test-placement findings across an existing project-audits/v1 artifact while preserving project identity. Use this for multiple audited projects; use analyze_test_placement for one audit/v1 artifact. Does not rescan the repository, execute tests, or create, move, or modify files.

• 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.

• analyze_test_placement

  Derive advisory test-placement findings from an existing single-project audit/v1 artifact. Use this for one audited project; use analyze_project_test_placement for a project-audits/v1 artifact. Does not rescan the repository, execute tests, or create, move, or modify files.

• 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.

• 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.

• collect_project_findings

  Collect concise top findings from an existing project-audits/v1 artifact. analyze_repository already includes this result.

• collect_project_stats

  Aggregate coverage, counts, risk and signal distributions, frameworks, and adapter usage from an existing project-audits/v1 artifact. Use this for separate reporting or comparisons; analyze_repository already includes the same stats. Returns project-stats/v1 without rescanning the repository, executing tests, or writing files.

• detect_projects

  Discover project roots, support status, and matching adapters without auditing source targets. Use this when project boundaries are needed before a specialized workflow; use analyze_repository for a complete review. Reads local repository markers and returns project-detection/v1 without executing tests or writing files.

• explain_target

  Explain the evidence, risk, testability, and recommendation for one target in an existing audit/v1 artifact. Use this after audit_repo or audit_projects when one target needs detail beyond the audit summary. Returns target-explanation/v1 without rescanning the repository, executing tests, or writing files.

• generate_project_test_plan

  Generate a project-aware plan from an existing project-audits/v1 artifact. analyze_repository already includes this result.

• generate_selected_test

  Return a structured deferred result. This tool does not generate or write test code while native generation remains disabled.

• generate_test_planwrite action

  Create a deterministic plan/v1 from an existing single-project audit/v1 artifact. Use this after audit_repo, optionally selecting one exact plan item; use generate_project_test_plan for multiple audited projects. Does not rescan the repository, execute tests, or generate or write test code.

• 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.

• get_plan_execution_hints

  Derive provider-neutral execution, context, parallel-safety, and repository-reasoning hints from a plan without invoking models or subagents.

• 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.

• rank_project_candidates

  Rank candidates from an existing project-audits/v1 artifact while preserving project identity. analyze_repository already includes this result.

• rank_test_candidates

  Rank testable audit targets by risk reduction and maintenance cost.

• 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.

• Code scan279 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 10 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Repo Test Architect: common questions

Is Repo Test Architect MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the Repo Test Architect safety report

How do I install Repo Test Architect?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Repo Test Architect need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Repo Test Architect maintained?

The last commit was 11 days ago (2026-09-10). The latest release is v1.0.0-beta.2.

What can I use instead of Repo Test Architect?

Servers from other publishers that do the same job: Kin MCP server.