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

Grok Bot is xAI's AI teammate. It documents adding custom MCP servers by URL or by running a server command, so your bot can work from a clip.qa report instead of a description of the bug.

## About Grok Bot

xAI describes Grok Bot as an AI teammate that works with connected apps and can take on engineering tasks. Its documentation describes adding custom MCP servers by URL or command. clip.qa is not listed by xAI, and authenticated retrieval of clip.qa reports has not been verified.


[What is Grok Bot?](https://clip.qa/blog/what-is-grok-bot/)

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

### 3. Give your bot the report
Add https://mcp.clip.qa/mcp as a custom MCP server for your Grok Bot, by URL or command, and confirm it retrieves a real report. Until that check passes, paste the report as Markdown.

### 4. Investigate, fix, report back
Ask the bot to investigate from the report, make a scoped change in the repository it can reach, and run its checks. Review the diff yourself before it ships.

## One caveat before you connect

Grok Bot documents custom MCP servers, but clip.qa is not listed by xAI and authenticated retrieval is unverified. Treat the connection as working only after your bot retrieves a real report.



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

1. Add https://mcp.clip.qa/mcp as a custom MCP server for your bot, by URL or command, and complete authentication.
2. Ask the bot to retrieve a real clip.qa report to confirm the connection.
3. If retrieval fails, paste the Markdown report into the conversation instead.

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

## Choose a Grok Bot if

- You want a teammate that works across connected apps, not only code.
- The bug reproduces in your app and needs device context to explain.
- You already run Grok Bot for engineering tasks.

## Why clip.qa for Grok Bot users

A bot can investigate a repository, but 'the settings page is broken' gives it nothing to search for. A clip.qa report carries the recorded steps, console and network context, and device state, so the bot starts from evidence.

## FAQ

**Q: Can Grok Bot connect to clip.qa?**
A: Grok Bot documents custom MCP servers by URL or command, and clip.qa provides https://mcp.clip.qa/mcp. clip.qa is not listed by xAI, so confirm your bot retrieves a real report before relying on the connection; otherwise paste the Markdown report.

**Q: Will it fix the bug on its own?**
A: Grok Bot can take on engineering tasks in the repositories and apps it can reach. Review any proposed change yourself; clip.qa only produces the report and can record the fix attempt.

**Q: Is this an xAI integration?**
A: No. clip.qa is an independent product with no partnership with xAI. The connection is the standard MCP protocol, which you configure yourself.

---

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