# clip.qa for Hermes Agent: send bug reports your agent can fix Hermes Agent runs in your own environment and connects to the tools you give it. clip.qa gives it the one thing it cannot see: what the bug looked like on a real phone. ## About Hermes Agent Hermes Agent is an open-source (MIT) agent from Nous Research. It runs shell commands through six terminal backends (local, Docker, SSH, Modal, Daytona and Vercel Sandbox) and connects to external MCP servers, as its MCP Integration doc describes. It also reaches you through messaging gateways such as Telegram, Discord and Slack. ## 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 Hermes Agent. ### 3. Connect clip.qa as an MCP server Hermes Agent documents external MCP support. Test the clip.qa transport, authentication and retrieval of a real report before relying on this path. Otherwise, paste the Markdown report into a chat. ### 4. Let it attempt the fix, then review Hermes Agent gets the steps, screenshots and context it needs to attempt a fix in its backend. You review the result before anything ships. ## Give Hermes Agent a clip.qa report Hermes Agent's MCP Integration doc covers external servers and supported transports. It does not verify this clip.qa connection: test the configured transport and authentication by retrieving a real report. Nous Research 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. Use the Hermes Agent MCP Integration instructions to configure https://mcp.clip.qa/mcp or the local package @clip-qa/mcp-server with your clip.qa credentials, then test authenticated retrieval of a real report. 2. Hermes Agent runs shell commands, so you can also test the clip.qa CLI (npm @clip-qa/cli) in its documented environment. 3. Or send the Markdown report straight into a Hermes Agent conversation. The clip.qa iOS app, Android app and Chrome extension are in beta. Request access on the apps page. ## Choose Hermes Agent on its own if - You want an agent that lives on a server and talks to you in your chat apps. - The work is automation or research, not a bug you saw on a device. - You already have a written, reproducible report. ## Why clip.qa for Hermes Agent users Hermes Agent is strong at running things and staying reachable. It has no eyes on your phone. clip.qa records the bug on the device and writes it up, so a solo developer shipping a mobile app can hand the agent a report instead of a vague message. ## FAQ **Q: Does Hermes Agent work with clip.qa?** A: Hermes Agent documents remote HTTP and local stdio MCP connections, including OAuth for remote servers. The clip.qa server has not been verified with Hermes: test successful retrieval of a real report using https://mcp.clip.qa/mcp or @clip-qa/mcp-server. Pasting the Markdown report works with no setup. **Q: Can Hermes Agent fix every bug from a clip.qa report?** A: No. It gets the steps, screenshots and device context it needs to attempt the fix. Complex bugs still need your judgment, and you should review every change. **Q: Is this made with Nous Research?** A: No. clip.qa is independent of Nous Research and Hermes Agent. There is no partnership; the connection relies on standard MCP. --- [Request beta access](https://clip.qa/apps) | [Back to clip.qa](https://clip.qa)