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 drafts a report with steps to reproduce and device context for you to review. Reports export as markdown for AI coding tools like Claude Code and Cursor, or to paste into any tracker. Jira, Linear, Slack, GitHub Issues and Notion integrations are coming soon. No SDK required in the app you test.

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 built for Vibe QA.

Does clip.qa work with OpenClaw projects?

Yes. clip.qa produces a structured report your agent, including OpenClaw, can read through MCP or a pasted prompt.

How is clip.qa different from Jam?

Jam has a Chrome extension, a Mac app and an iOS app, plus AI summaries and an MCP server. No Android app is documented. clip.qa records on iOS, Android and in Chrome (beta, request access), with no SDK in the app you test. clip.qa's MCP also records each fix attempt (pending, succeeded, failed) with its commit or PR, and can diff reports.

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 (subject to OS limits such as FLAG_SECURE).

How much does clip.qa cost?

Free: 30 bug reports and 30 AI-assisted reports a month. Team ($12.99/mo or $129/yr, billed per creator seat, viewers free): unlimited bug reports, 200 AI-assisted reports and 50 share links a month. Enterprise pricing is custom; confirm current quotas and features with sales. Audit logs and priority support are listed; SAML/SSO is coming soon.

What platforms does clip.qa support?

The clip.qa web dashboard is available now; the iOS app, Android app and Chrome extension are in beta (request access at hello@clip.qa). Bug reports can be copied as markdown into any tracker (Jira, Linear, GitHub Issues; native integrations coming soon) or used directly as prompts for Claude, Cursor, and other AI coding tools.

Amp

clip.qa / Use cases / Amp

clip.qa for Amp: send bug reports your agent can fix

Amp edits code and runs your tests. clip.qa gives it a report made from a recording of the bug on your phone, so it starts from the real steps.

The clip.qa iOS app, Android app and Chrome extension are in beta. Request access on the apps page.

Request beta access See all integrations

The agent

About Amp

Amp (ampcode.com) is a coding agent with a CLI called amp. Its site describes it editing code and running tests and builds, and it lists MCP among its features. Its manual does not spell out which MCP transports it accepts, so check the manual before you connect a server.

Read the Amp bug-report workflow

How it works

From a bug on your phone to a fix attempt in Amp

1. Record the bug on your own device

Use the clip.qa iOS or Android app (beta, request access), or the Chrome extension (beta, request access), to screen-record the bug. No SDK goes into the app you test.

2. Review the AI draft

clip.qa turns the recording into a report: title, severity, kind, suspected root cause, steps to reproduce, and expected vs actual behavior when the recording shows a defect, plus key-moment screenshots and device context (OS, device, memory, thermal). It is a draft, so check it before you hand it to Amp.

3. Hand the report to Amp

Paste the Markdown report into an Amp thread, or connect the clip.qa MCP server if your Amp setup accepts it.

4. Review the change

Amp gets the steps and context it needs to attempt a fix and run your tests. You review the diff before it ships.

Use Amp

Give Amp a clip.qa report

Pasting works everywhere. For MCP, follow the MCP section of the Amp manual. The clip.qa details are below. Amp's makers did not build this connection.

clip.qa connection details

Remote MCP server:  https://mcp.clip.qa/mcp
Local MCP server:   npm @clip-qa/mcp-server
CLI:                npm @clip-qa/cli

1In clip.qa, copy the report as Markdown and paste it into an Amp thread. This needs no setup.

2To use MCP, add https://mcp.clip.qa/mcp (remote) or the package @clip-qa/mcp-server with your clip.qa API key, in the form the Amp manual shows.

3Amp has a CLI, so the clip.qa CLI (npm @clip-qa/cli) is another route in a terminal.

Honest fit

Choose Amp on its own if

You want a terminal agent that edits code and runs your tests.
The bug is in logic you can reproduce without a device.
Your team wants an agent that wakes on CI failures.

Amp is good at turning a clear description into a change. clip.qa is how you get a clear description when the bug lives on a phone: you record it, review the AI draft and hand it over.

clip.qa and Amp FAQ

How do I use clip.qa with Amp?

Paste the Markdown report into an Amp thread. If your Amp setup accepts MCP servers, you can add https://mcp.clip.qa/mcp or @clip-qa/mcp-server; the Amp manual does not state which transports it supports, so check it before you connect.

Does Amp fix every bug from a report?

No. Amp gets the steps, screenshots and device context it needs to attempt a fix, and you review its work.

Is clip.qa affiliated with Amp?

No. clip.qa is independent, with no partnership. The report is plain Markdown, so it works with any agent.

Amp writes the change. clip.qa captures the bug.

Record the bug, review the AI draft, then send it to your agent. Free plan available.

Request beta access See all integrations