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.

Cline

clip.qa / Use cases / Cline

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

Cline works in your editor and terminal. clip.qa hands it a report built from a recording of the bug, so you stop retyping steps into the chat.

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 Cline

Cline is an open-source (Apache-2.0) coding agent for VS Code and JetBrains, with a CLI. It edits files, runs commands, builds and tests. Its docs describe adding MCP servers over remote HTTP and over a local process, and the CLI has a cline mcp command.

Read the Cline bug-report workflow

How it works

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

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

3. Add clip.qa to Cline

Add the clip.qa MCP server in Cline's MCP settings and ask it for the latest report, or paste the Markdown report into the chat.

4. Review each change

Cline gets the steps and context it needs to attempt a fix. You review what it changed before you ship.

Connect Cline

Add the clip.qa MCP server to Cline

The Cline docs page on adding and configuring servers shows the config form. The clip.qa values to use are below. The Cline team 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

1Register the remote endpoint https://mcp.clip.qa/mcp, or the local package @clip-qa/mcp-server with your clip.qa API key.

2Cline runs commands, so the clip.qa CLI (npm @clip-qa/cli) is another route.

3Or paste the Markdown report into the Cline chat.

Honest fit

Choose Cline on its own if

You want an agent inside VS Code or JetBrains.
You already have the steps and logs for the bug.
The work is a feature or refactor rather than bug intake.

Cline is a strong editor agent. It cannot watch your phone. clip.qa records the bug where it happened and writes it up, which suits solo developers and small teams shipping AI-built mobile apps.

clip.qa and Cline FAQ

Does clip.qa work with Cline?

Yes through MCP. Cline's docs describe remote HTTP and local servers, so you can use https://mcp.clip.qa/mcp or @clip-qa/mcp-server. clip.qa has no Cline-specific guide yet. Pasting the Markdown report also works.

Will Cline fix the bug?

Cline gets the steps, screenshots and device context it needs to attempt a fix. It does not fix every bug, and you should review its changes.

Is this a partnership with Cline?

No. clip.qa is an independent product and nothing here was built by Cline's makers. It relies on the standard MCP protocol.

Cline edits in your editor. clip.qa catches the bug.

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

Request beta access See all integrations