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

## 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](https://clip.qa/blog/cline-mcp-bug-reports/)

## How it works

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

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



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

1. Register the remote endpoint https://mcp.clip.qa/mcp, or the local package @clip-qa/mcp-server with your clip.qa API key.
2. Cline runs commands, so the clip.qa CLI (npm @clip-qa/cli) is another route.
3. Or paste the Markdown report into the Cline chat.

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

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

## Why clip.qa for Cline users

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.

## FAQ

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

**Q: Will Cline fix the bug?**
A: 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.

**Q: Is this a partnership with Cline?**
A: No. clip.qa is an independent product and nothing here was built by Cline's makers. It relies on the standard MCP protocol.

---

[Request beta access](https://clip.qa/apps) | [Back to clip.qa](https://clip.qa)