Repo Test Architect
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_repositoryA | 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_adaptersA | List registered language adapters available to audit repositories. |
| list_project_detection_rulesA | List deterministic project marker rules and ignored directories used during project detection. |
| detect_projectsB | Detect project roots and matching adapters inside a repository. |
| audit_projectsA | 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_auditsA | 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_candidatesA | Rank candidates from an existing project-audits/v1 artifact while preserving project identity. analyze_repository already includes this result. |
| generate_project_test_planA | Generate a project-aware plan from an existing project-audits/v1 artifact. analyze_repository already includes this result. |
| collect_project_findingsA | Collect concise top findings from an existing project-audits/v1 artifact. analyze_repository already includes this result. |
| analyze_project_test_placementA | Analyze project-aware test placement from a project-audits artifact. |
| collect_project_statsB | Collect local deterministic project audit stats for coverage, counts, risk and signal distributions, framework distribution, and adapter usage. |
| audit_repoA | 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_graphA | 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_planB | Generate a deterministic test plan from an audit graph. |
| get_plan_execution_hintsA | Derive provider-neutral execution, context, parallel-safety, and repository-reasoning hints from a plan without invoking models or subagents. |
| explain_targetB | Explain one audit target by stable target id. |
| rank_test_candidatesA | Rank testable audit targets by risk reduction and maintenance cost. |
| analyze_test_placementB | Analyze existing test placement from an audit graph and return advisory placement findings. |
| generate_selected_testA | Return a structured deferred result. This tool does not generate or write test code while native generation remains disabled. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RepoAssay/repo-test-architect'
If you have feedback or need assistance with the MCP directory API, please join our Discord server