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

## 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](https://clip.qa/blog/amp-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 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.

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



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

1. In clip.qa, copy the report as Markdown and paste it into an Amp thread. This needs no setup.
2. To 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.
3. Amp has a CLI, so the clip.qa CLI (npm @clip-qa/cli) is another route in a terminal.

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

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

## Why clip.qa for Amp users

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.

## FAQ

**Q: How do I use clip.qa with Amp?**
A: 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.

**Q: Does Amp fix every bug from a report?**
A: No. Amp gets the steps, screenshots and device context it needs to attempt a fix, and you review its work.

**Q: Is clip.qa affiliated with Amp?**
A: No. clip.qa is independent, with no partnership. The report is plain Markdown, so it works with any agent.

---

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