# clip.qa + Claude Code — From Screen Recording to AI-Fixed Bug

## Introduction

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

### 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.

### 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 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

The MCP server connects clip.qa to Claude Desktop and Claude Code. No copy-paste required.

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

Add this to `~/.claude/claude_desktop_config.json`, set your API key from the clip.qa dashboard, then tell Claude Code: "Fix the latest bug from clip.qa" — it fetches the report and writes the fix.

## FAQ

**Q: Does clip.qa work with Claude Desktop?**
A: 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.

**Q: What can Claude Code do with a clip.qa report?**
A: 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 search the codebase for the relevant logic, write a targeted fix, run tests, and explain its reasoning.

**Q: Is the MCP server free to use?**
A: 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.

**Q: How is this different from just describing a bug to Claude Code?**
A: When you describe a bug in your own words, critical context gets lost — device model, exact steps, 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.

---

[See Claude Code integration](https://clip.qa/integrations/claude-code) | [Back to clip.qa](https://clip.qa)