Automate client feedback with our MCP serverLearn more!
Reads every open task, with comments, tags, files and browser details
Each task carries the page, the element and the screenshot or recording
Run it in your codebase and it fixes what the feedback describes
It comments on the task as you, so the trail stays on the board
Marks tasks done as it finishes, or reopens them if you disagree
Tag or complete up to a hundred tasks in a single pass
MCP server
Your AI assistant reads the bug report straight from QualityHive: screenshot, console log, browser and screen size. No copy-pasting into chat.
Form submits twice
TypeError: form.submit is not a function
qualityhive.get_task #248
The submit handler fires twice on Chrome. Guard added and tested. Want me to move it to Done?
Both, depending on where you run it. Connected to QualityHive alone, it reads the feedback, comments, tags, and completes or reopens tasks. Run it against your codebase as well, with Claude Code, and it can make the change the feedback describes and then close the task off itself. QualityHive gives it the context to do that: the page, the element, the screenshot and the browser the problem happened in.
It can comment, add tags, and mark a task complete or reopen it, including in batches of up to a hundred. It cannot edit the wording of an existing task, reassign it, move it between columns or delete it. That is deliberate: what your client reported stays as they wrote it, and the assistant adds to the record rather than rewriting it.
Everything it does is on the board in your team's normal view, and comments show it acted as you, so nothing happens invisibly. If it closes a task you disagree with, ask it to reopen the task, or reopen it yourself in a click. It is usually worth telling it to comment rather than close on the first run, until you are happy with how it handles your projects.
It sees exactly what you see, because it connects as you: the teams and projects your own account has access to, and nothing else. Each person uses their own token, so an assistant never gets a wider view of your data than the person using it.
Every paid plan, and your trial. MCP is the one thing the free plan does not include. Setting it up takes about two minutes: create an MCP token in QualityHive, then add it to Claude as a custom connector, or pass it as a header in Claude Code. Revoke the token any time and access stops straight away.
No, and they will not notice any difference. Your clients carry on reporting feedback from the page itself, the way they already do. What changes is your side of it: the list gets worked through and written up without someone on your team doing it by hand.