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.

OpenClaw

clip.qa / Use cases / OpenClaw

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

OpenClaw builds fast and can run your repo, your commands and your MCP servers. clip.qa is the piece before all that: a recording of the real bug, turned into a report with steps, logs and device context.

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 OpenClaw, the open-source agent project

OpenClaw is an open-source AI agent project. Its documentation describes tools for shell execution and configured MCP servers, so an OpenClaw agent can read files, run commands and apply code changes in a repository you give it. The specific clip.qa connection has not been tested by either project.

How it works

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

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 your OpenClaw agent.

3. Hand the report to your agent

Add https://mcp.clip.qa/mcp as a remote MCP server in your OpenClaw configuration, or paste the report as Markdown into the session. Until you confirm the authenticated connection retrieves a real report, use the pasted report.

4. Let it investigate and fix

Your agent reads the report, searches the code, makes a scoped change and runs the checks it has. It can log the fix attempt back on the report through the MCP write tools. You review the diff.

Connect OpenClaw

Two ways to give an OpenClaw agent the report

OpenClaw documents shell execution and configured MCP servers. Neither project has tested the clip.qa connection, so confirm retrieval of a real report first.

The full OpenClaw QA guide

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

1Add the remote MCP server https://mcp.clip.qa/mcp to your OpenClaw MCP configuration and complete authentication, then confirm the agent retrieves a real report.

2Or run the local server with an API key: npx @clip-qa/mcp-server.

3If retrieval is not confirmed, paste the Markdown report into the agent session instead.

Honest fit

Choose OpenClaw if

You want an open-source agent you host and configure yourself.
The agent should run commands, not just read reports.
Your team already runs OpenClaw for repo work.

OpenClaw can code. It cannot watch over your shoulder when an AI-built app breaks on your phone. clip.qa is that witness: record the bug, get a report with steps, console, network and device context, and let your agent work from evidence instead of a sentence.

clip.qa and OpenClaw FAQ

Can OpenClaw read a clip.qa report?

Yes, through the MCP server at https://mcp.clip.qa/mcp or by pasting the Markdown report. OpenClaw documents MCP and shell tools; the clip.qa connection is untested by either project, so confirm report retrieval in your setup first.

Can it fix the bug for me?

OpenClaw agents can make code changes and run commands in a repository you give them. clip.qa does not change code; it produces the report the agent works from, and can record the fix attempt on the report.

Is this an OpenClaw integration?

No. clip.qa is an independent product with no partnership with the OpenClaw project. The connection is standard MCP, which you configure yourself.

OpenClaw codes. clip.qa catches what slips through.

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

Request beta access See all integrations