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

Goose installs, runs, edits and tests code on your machine, with the model you choose. clip.qa gives it a report written from a recording of the bug on your phone.

## About Goose

Goose is an open-source (Apache-2.0) agent from Block, available as a CLI and a desktop app. It adds abilities through MCP-based extensions, over stdio and Streamable HTTP, and its developer extension runs commands. Its README says it can install, execute, edit and test with any LLM.


[Read the Goose bug-report workflow](https://clip.qa/blog/goose-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 Goose.

### 3. Add clip.qa as a Goose extension
Add the clip.qa MCP server as an extension in Goose, then ask it for the latest report. Or paste the Markdown report into a session.

### 4. Review what Goose changes
Goose gets the steps and context it needs to attempt a fix and test it. You review the diff before you keep it.

## Add clip.qa to Goose

Goose extensions are MCP servers, and it accepts both local processes and Streamable HTTP. Follow the Goose extensions guide for the exact steps. Block 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. Add a Streamable HTTP extension that points at https://mcp.clip.qa/mcp, or a local extension that runs the package @clip-qa/mcp-server with your clip.qa API key.
2. Goose runs commands through its developer extension, so the clip.qa CLI (npm @clip-qa/cli) is another route.
3. Or paste the Markdown report into a Goose session with no setup.

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

## Choose Goose on its own if

- You want a local agent that works with any model you pick.
- The task is code you can describe, not a bug you saw on a device.
- You want a desktop app and a CLI for the same agent.

## Why clip.qa for Goose users

Goose gives you freedom over the model and the tools. clip.qa gives that freedom something concrete to work on. For a solo developer or a small team, one recording replaces the paragraph of steps you would otherwise type.

## FAQ

**Q: How do I add clip.qa to Goose?**
A: Add it as an MCP extension: Streamable HTTP at https://mcp.clip.qa/mcp, or a local process running @clip-qa/mcp-server with your API key. The Goose extensions guide covers the steps. You can also paste the Markdown report.

**Q: Does Goose fix the bug on its own?**
A: Goose gets the steps, screenshots and device context it needs to attempt a fix. It will not solve every bug, so run the tests and read the diff.

**Q: Is clip.qa made by Block?**
A: No. clip.qa is independent of Block, with no partnership. Goose supports MCP, and that standard protocol is the connection.

---

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