DoesQA for AI agents
Point an MCP-capable agent at your account. It builds, runs, and triages real Tests as product data you review in DoesQA.
An AI coding agent can now work inside DoesQA rather than around it.
Connect once over MCP or the DoesQA CLI. The agent gets the platform: Flows and Test Steps, Elements, Runs and Results, traces, coverage, failure patterns, the in-app Assistant, and durable memory. Work arrives as product data, not as a codebase to maintain.
The agent can ask how your product works before it writes a Test. Answers come from your Flows, Runs, and coverage, and the exchange shows up as a conversation you can read. Session two starts where session one finished, because memory is stored for the account and scoped for the people and agents you choose.
Review is opening a link. You read a journey on the canvas and evidence from a real browser. Flows stay saved, Runs queue on hosted runners, and Results stay recorded after the agent session ends.
doesqa pull mirrors your Flows into .doesqa/ as readable documents: front matter, a diagram, and a step map. Generated, so you read them rather than maintain them.
Tokens are scoped so you grant only the tools you are willing to provide. Revoke in the app when you want access gone. Tokens expire. Auth is per user and per account. Every call is audited.
Same job, over 50% fewer tokens in our grading runs, and the same graded results on a smaller model. The saving is structural: the agent reads a compact Flow document instead of a payload dump.