Healix

End-to-end AI test generation and QA automation, from your IDE.

Healix is a monorepo containing two packages:

• testbot-mcp/ — @healix/mcp (v2.0.0), an MCP server installed in developer IDEs. It orchestrates the full testing pipeline: auto-detect → explore → generate → execute → analyze → dashboard.
• webapp/ — A Next.js 16 / React 19 webapp deployed on Vercel. Hosts all AI calls (OpenAI server-side), the Supabase-backed dashboard, artifact storage, and the Inngest async generation pipeline.

Users only need a HEALIX_API_KEY. All AI calls are proxied server-side through the webapp — no OpenAI key needed on user machines.

Quick Start

1. Install the MCP server

npm install -g @healix/mcp

2. Configure your IDE

Add to your MCP settings (~/.cursor/mcp.json, Claude Code, or Windsurf):

{
  "mcpServers": {
    "healix": {
      "command": "npx",
      "args": ["@healix/mcp"],
      "env": {
        "HEALIX_API_KEY": "your-healix-api-key"
      }
    }
  }
}

Get your API key from the Healix dashboard → API Keys.

3. Run a test

In your IDE prompt:

“Test my app using the healix mcp”

The pipeline runs automatically:

1. Config UI — local HTTP form collects test type, base URL, start command, PRD file (optional), and role credentials
2. Auto-detect — port, framework, and start command inferred from the project when not supplied
3. Browser exploration — browser-use (Python subprocess) discovers real flows; falls back to a zero-dependency Playwright heuristic explorer if browser-use is unavailable
4. PRD/AC parse — structured acceptance-criteria extraction via /api/parse-prd; AC-less apps use exploration flows directly
5. Test generation — GPT-powered multi-agent fan-out via /api/generate-tests; each test tagged [REQ:F#.S#.AC#]
6. Credential injection — per-role Playwright storageState written to .healix/auth-state-{role}.json
7. Tiered execution — three Playwright projects run in sequence:
   • Tier A (tierA-public) — unauthenticated / public flows
   • Tier B (tierB-auth-{role}) — one project per role; marked blocked if login fails (A + C still run)
   • Tier C (tierC-backend) — API/backend contract tests
8. Artifact upload — screenshots, videos, and Playwright traces uploaded to Supabase Storage
9. Ingest — results POSTed to /api/test-runs/ingest
10. Dashboard deep-link — opens the run page with tier pills, failure analysis, and artifacts

MCP Tools

Configuration