QAProvider
Real testers find your bugs ā€” your AI agent fixes them
Start new thread

QAProvider - Real testers find your bugs. Your AI agent fixes them.

byā€¢
QAProvider connects your product with real testers on real devices worldwide ā€” phones, tablets, desktops, whatever your users actually have. They find the bugs CI never catches: a layout that breaks on one screen size, a checkout that fails only on a slow network, an onboarding step nobody understands. Every report is structured, reproducible, and backed by evidence. And with our MCP server, your AI coding agent can read those reports, view attachments, and close them without leaving your IDE.

Add a comment

Replies

Best
Maker
šŸ“Œ
Hey Product Hunt šŸ‘‹ QAProvider is a crowdtesting platform. You describe what to test, and real testers around the world run through your product on their own hardware ā€” phones, tablets, desktops, whatever your users actually have. They find the bugs CI never catches: a checkout flow dead on one particular device, a form unusable on a screen size nobody on your team owns. Every report comes in structured, reproducible, and backed by evidence ā€” screenshots, steps, environment. You review them, reward the good ones, and ship with less anxiety. What's new in this launch: QAProvider now ships with an MCP server. Point your AI coding agent at it, and the agent can read incoming reports, open attachments, investigate your codebase, fix what it can, and mark the report resolved with a commit reference. Human testers find the problem; your agent closes it. Every agent action is logged separately from human ones, so you always know who did what. We started this in 2018 because shipping software you can't test on your users' actual devices is a bad way to live. The agent part is what makes the loop close fast enough to matter. Free to start ā€” bring a project, get your first reports, see if the reports are good enough to hand to an agent. Happy to answer anything: how testers are vetted, how the MCP server works, what breaks when you give an agent write access to production data. ā€” Maxim

Hello)
The headline says the AI agent 'fixes' bugs, but the description only mentions the MCP server letting it read, view attachments, and close reports ā€” does the agent actually write and commit the fix itself, or does it just mark reports resolved after a developer fixes them manually?

Maker

Ā The agent writes and commits the fix ā€” but it's your agent, in your repo.

The MCP server covers the report side: your coding agent lists reports, reads them, pulls attachments (screenshots included ā€” vision models read them directly), comments, and updates status. It then investigates and patches your codebase with its own tools, in your environment, under your review, and marks the report resolved with a commit reference.

We deliberately don't touch your code. QAProvider is the input side of that loop.

One detail: agent-resolved reports are stored separately from human-resolved ones, so you can always see which fixes came from an agent. And the tester who filed the report gets to verify or reopen it ā€” so the loop closes with a human on the other end, not with the agent marking its own homework.