clip.qa is a mobile app that turns screen recordings into structured bug reports. Record a bug on your phone, and clip.qa's AI generates steps to reproduce, device context, and environment details. Reports export to Jira, Linear, GitHub Issues, or as LLM-ready markdown for AI coding tools like Claude Code and Cursor. No SDK required — works on any app.

What is Vibe QA — and why does it matter?

Vibe QA is quality assurance for apps built with AI coding tools — a practice that emerged alongside vibe coding (using AI assistants like Claude Code, Cursor, and Copilot to build apps rapidly). Because vibe-coded apps ship faster than traditional QA can keep up, Vibe QA uses AI-native tools to close the loop: capture bugs visually, generate LLM-ready reports automatically, and feed them back to the same AI tools that built the app. clip.qa is the first dedicated Vibe QA tool.

Does clip.qa work with OpenClaw projects?

Yes. clip.qa works with any app built with OpenClaw or any other AI coding framework. Record a bug in your OpenClaw app, generate a structured report, and feed it to your OpenClaw agent — which can then implement the fix autonomously.

How is clip.qa different from Jam?

Jam is a browser-only Chrome extension — it works on web apps but has no mobile support. clip.qa is mobile-first: it records any native iOS or Android app using the device's built-in screen recording, with no SDK or code changes required. clip.qa also exports LLM-ready structured reports that AI coding tools like Claude Code and Cursor can parse and act on directly.

Do I need to install an SDK or add code to my app?

No. clip.qa works without any SDK integration. It uses your phone's native screen recording, so it works on any app — including competitor apps you're testing, OpenClaw projects, and apps you don't have source access to.

How much does clip.qa cost?

clip.qa offers a free tier with 30 bug reports per month, all auto-summarized by AI. Team is $12.99/month or $129/year for unlimited reports and 200 AI-assisted reports per month. Enterprise pricing is custom with unlimited everything, SAML/SSO, audit logs, and priority support.

What platforms does clip.qa support?

clip.qa is available on iOS with Android coming soon. Bug reports can be exported to any platform — Jira, Linear, GitHub Issues, or directly as prompts for Claude, Cursor, and other AI coding tools.

clip.qa / Use cases / Claude Code Integration

Screen recording to AI-fixed bug.

clip.qa is the missing QA layer for Claude Code users. Record a bug on your phone, get a structured report, paste into Claude Code — or install the MCP server and let Claude Code pull reports directly from your bug queue.

The full loop: phone in hand to fixed and shipped — without leaving your terminal.

See Claude Code integration Get clip.qa free

The paste workflow

Record, report, paste. Bug fixed in minutes.

1. Record the bug on your phone

Open clip.qa on iOS or Android. Screen-record the bug in your app. Device model, OS version, and app context are captured automatically — you don't type anything.

2. clip.qa generates a structured report

One tap. clip.qa's AI produces steps to reproduce, expected vs actual behavior, device context, and environment details — all formatted as LLM-ready markdown that Claude Code can parse without ambiguity.

3. Paste into Claude Code

Copy the report. In your terminal, start a Claude Code session and paste. Claude Code reads the full context — no re-explaining, no manual steps-to-reproduce — and writes a targeted fix.

4. Review and ship

Claude Code writes the fix. You review the diff, approve, and ship. The entire loop — bug found to bug fixed — takes minutes, not hours.

MCP Integration

Even better: let Claude Code pull reports directly.

The MCP server connects clip.qa to Claude Desktop and Claude Code. No copy-paste. Claude Code fetches the report, writes the fix, and commits — you just record the bug.

claude_desktop_config.json

{
  "mcpServers": {
    "clip-qa": {
      "command": "npx",
      "args": ["-y", "@clip-qa/mcp-server"],
      "env": { "CLIP_QA_API_KEY": "your-key" }
    }
  }
}

1 Add the config above to ~/.claude/claude_desktop_config.json

2 Set your CLIP_QA_API_KEY from your clip.qa dashboard

3 Tell Claude Code: "Fix the latest bug from clip.qa" — it fetches the report and writes the fix

Full Claude Code MCP setup guide

Claude Code integration FAQ

Does clip.qa work with Claude Desktop?

Yes. The @clip-qa/mcp-server package works with both Claude Desktop and Claude Code. Add the MCP config to claude_desktop_config.json and Claude Desktop can access your bug queue directly. You can also paste reports manually — the structured markdown format works in any Claude interface.

What can Claude Code do with a clip.qa report?

With a clip.qa report, Claude Code has the complete picture: what the bug is, what device and OS it appeared on, the exact steps to reproduce it, and what the expected behavior should have been. Claude Code can use this to search the codebase for the relevant logic, write a targeted fix, run tests, and explain its reasoning — all without you having to describe the bug in your own words.

Is the MCP server free to use?

Yes. @clip-qa/mcp-server is free and open source on npm. MCP access to your bug reports is included in all clip.qa plans, including the free tier. You need a clip.qa API key (available from your dashboard) to authenticate the server.

How is this different from just describing a bug to Claude Code?

When you describe a bug in your own words, critical context gets lost — you forget the device model, you misremember the exact steps, you skip the environment details. clip.qa's AI generates the report from the actual recording, so every field is accurate and complete. Claude Code performs significantly better with a structured, complete report than with a casual description typed from memory.

Claude Code builds it. clip.qa catches what slips through.

Free to start. MCP server included. Works with Claude Desktop and Claude Code.

See Claude Code integration Get clip.qa free