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

Devin takes tickets and opens pull requests. clip.qa turns a screen recording into a ticket-ready report, so Devin starts from what actually happened on the device.

## About Devin

Devin is Cognition's software engineering agent. Its site describes it writing and testing code, opening pull requests and fixing failed CI. Devin takes work from Slack and Teams, from Linear and Jira tickets, and from GitHub. Its docs list MCP support over remote HTTP and local servers.


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

### 3. Get the report to Devin
Connect the clip.qa MCP server to Devin, or copy the report as Markdown and paste it into a Devin session or into the ticket you assign to Devin.

### 4. Review the pull request
Devin gets the steps, screenshots and device context it needs to attempt a fix and open a PR. You review it. Over MCP, your agent can log the attempt with its commit or PR.

## Three ways to get a clip.qa report to Devin

Native clip.qa integrations for Jira, Linear, Slack, GitHub Issues and Notion are coming soon. Until then, use MCP or paste the report. Cognition 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 clip.qa as an MCP server in Devin's MCP settings: the remote endpoint https://mcp.clip.qa/mcp, or the local package @clip-qa/mcp-server with your clip.qa API key. See the MCP page in the Devin docs.
2. Paste the Markdown report into a Devin session in Slack, Teams or the Devin app.
3. Paste the Markdown report into a Linear or Jira ticket and assign it to Devin.

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

## Choose Devin on its own if

- The task is a backlog item or a failing CI run, not a device bug.
- Your team already routes work to Devin through tickets and Slack.
- You want an agent to own a task end to end in its own environment.

## Why clip.qa for Devin users

Devin is built for teams with a ticket queue. clip.qa fills that queue for a solo developer or a small team: you record the bug on your phone and get a ticket-ready report, without writing it up by hand.

## FAQ

**Q: How do I send a clip.qa report to Devin?**
A: Connect the MCP server (https://mcp.clip.qa/mcp or @clip-qa/mcp-server) in Devin's MCP settings, or paste the Markdown report into a session or ticket. Native Jira and Linear integrations from clip.qa are coming soon.

**Q: Will Devin fix the bug?**
A: Devin gets the steps, logs and screenshots it needs to attempt a fix and open a pull request. It will not fix every bug, so review the PR before you merge.

**Q: Does Cognition endorse clip.qa?**
A: No. clip.qa is an independent product with no partnership with Cognition. Devin supports MCP, and that standard protocol is the connection.

---

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