Skip to main content
Use your coding agent to prepare a Mo brief, start and follow a session, and review its findings. For fixes, have the agent update the app and ask Mo to recheck the original reproduction. Prefer the hosted Momentic MCP via qa mcp for deployed apps and PRs. Run npx -y qa login before adding npx -y qa mcp as the momentic-hosted stdio server. Claude.ai/ChatGPT connectors use https://mcp.momentic.ai with OAuth. Use mo-qa as the coding-agent skill for both hosted sessions and CLI sessions. Follow the skill’s routing. For a requested hosted session, use an existing Connector for local or private web targets, or create a named tunnel with the qa CLI and pass the discovered Connector name as access; report authentication failures without switching to the CLI.

Run and recheck

Ask your agent to use the hosted MCP tools with your brief. momentic_mo_start_session starts the session, momentic_mo_get_session returns progress, pending questions, a bounded report summary, and a webUrl for the full report. Open that URL to review or share findings. Hosted tools do not export a report directory. momentic_mo_message_session answers Mo. After deploying a fix, use momentic_mo_retest_finding to recheck the original finding. After confirming testing is complete, read the finished report, then call momentic_mo_stop_session even if report retrieval fails, unless you want more testing. Report the stop tool’s actual result; an idle session may have nothing to stop. Then summarize findings and uncovered requirements.

Install the Mo skill

Install the skill without a global CLI install. Replace codex with your agent’s target:
If you use the CLI, run qa skills in your repository to install mo-qa for Claude Code, Cursor, Codex, Devin, Copilot, or OpenCode. It adds a pointer block to each selected agent’s instructions file. Use --target to select agents without a prompt:
Use qa skills --yes to install for detected agents. Devin skills go in .devin/skills. See coding agent skills for all installation directories. For localhost or private targets, follow the tunneling guide and keep the requested interface. Hosted sessions use Connector names; CLI sessions use --tunnel. Use qa report to export the idle report to a local directory. See Mo integrations for other connections.