Automated QA with Claude Code

One command. Claude tests your app before every deploy.

Step 1: Install

$npx -p @recursiv/cli recursiv mcp install claude-code

Prompts for your email, creates your account, and configures everything. Done in 30 seconds.

If your dev server runs on a port other than 3000, set RECURSIV_TUNNEL_PORT in the generated .mcp.json:

1"env": {
2 "RECURSIV_API_KEY": "sk_live_...",
3 "RECURSIV_TUNNEL_PORT": "3001"
4}

Already have an API key? Just create .mcp.json with {"mcpServers":{"recursiv":{"command":"npx","args":["-y","@recursiv/mcp"],"env":{"RECURSIV_API_KEY":"sk_live_..."}}}}

Step 2: Tell Claude to QA your app

Start your dev server, then tell Claude:

“QA my app — test the landing page, sign up flow, and navigation”

Claude deploys QA agents through a secure tunnel to your localhost. They open your app in a real browser, navigate through flows, and report back what’s broken — with screenshots.

Then Claude fixes the issues and retests. You don’t touch the browser.

Make it permanent

Want Claude to QA automatically on every UI change? Add this to CLAUDE.md:

1## QA
2Before completing UI work, call browser_use_run_task to test the app.
3Fix issues and retest until clean. Max 3 loops.

Now Claude will never say “done” without testing first.

How it works

The MCP opens a secure outbound tunnel from your machine to Recursiv. QA agents travel through it to reach your localhost. No ports exposed, no tools to install, nothing to configure.

  • localhost → agents reach your dev server through the tunnel
  • deployed URL → tell Claude the URL and agents go there directly

Tools available

ToolWhat it does
browser_use_run_taskAutonomous browser agent — navigates, clicks, fills forms, reports findings
browser_screenshotScreenshot of any page
browser_inspect_pagePage structure — headings, buttons, links, forms
run_visual_auditCompare against stored baselines, catch regressions

Works with

Next.js, Vite, Remix, Astro, SvelteKit, Nuxt, Express, Hono — any framework that serves over HTTP.