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.
The paste workflow
Record, review, paste.
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
clip.qa's AI drafts steps to reproduce, expected vs actual behavior when the recording shows a defect, and device context — formatted as LLM-ready markdown for Claude Code to read. Review the draft first.
3. Paste into Claude Code
Copy the report. In your terminal, start a Claude Code session and paste. Claude Code can inspect the report and propose changes for developer review.
4. Review and ship
Claude Code writes the fix. You review the diff, approve, and ship. You stay in the loop at every step.
MCP Integration
Let Claude Code read clip.qa reports.
\nRun claude mcp add clip-qa-team --transport http https://mcp.clip.qa/mcp in Claude Code and complete OAuth in your browser. Claude Desktop uses a separate setup; see the official MCP setup docs. The agent can read a report and propose changes for your review.\n
claude mcp add clip-qa-team --transport http https://mcp.clip.qa/mcp in Claude Code.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 MCP configuration 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, A report can include details visible in the recording, such as: 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 the report is drafted from the recording and may need review. 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.