Maestro MCP integration (POC)
Use VisualQ as the quality brain and Maestro MCP for native mobile execution.
Maestro MCP + VisualQ (POC)
VisualQ covers web quality (VRT, FRT, a11y, perf, SEO, security, tracking) with rolling health and the @visualq/mcp server. Maestro covers native mobile (iOS, Android, React Native, Flutter) with deterministic YAML tests and its own MCP server.
This document describes a complementary setup — not a built-in integration yet.
Architecture
Cursor / Claude Code
├── @visualq/mcp → rolling health, VRT/FRT gates, multi-pillar audits
└── maestro mcp → mobile device execution, YAML flows, MaestroGPT| Layer | VisualQ | Maestro |
|---|---|---|
| Web E2E | FRT (Gherkin/Playwright) | Web YAML (optional) |
| Mobile native | Responsive viewports only | Real devices / simulators |
| MCP | 90+ quality tools | Device + flow tools |
| CI gate | gate_pr_quality, GitHub Action type: frt | Maestro Cloud |
When to use both
- Web PRs: VisualQ MCP —
gate_pr_quality,run_vrt,run_frtvia GitHub Action - Mobile releases: Maestro MCP — run flows on simulators, Maestro Cloud in CI
- Shared journeys: Document the same user story in VisualQ FRT (web) and Maestro YAML (mobile); link via Jira ticket id in names
Maestro MCP setup
- Install Maestro CLI
- Start MCP:
maestro mcp - Add to Cursor
mcp.json:
{
"mcpServers": {
"maestro": {
"command": "maestro",
"args": ["mcp"]
},
"visualq": {
"command": "npx",
"args": ["-y", "@visualq/mcp"],
"env": {
"VISUALQ_API_KEY": "vq_org_live_…"
}
}
}
}Agent workflow (web + mobile)
- VisualQ —
gate_pr_qualityon the web project before merge - Maestro — agent runs mobile smoke YAML after web is green
- VisualQ —
get_site_healthfor rolling quality score in release notes
Limitations (POC)
- No automatic sync between VisualQ FRT features and Maestro flows
- No unified merge gate across both servers — run two CI jobs or orchestrate in your agent
- VisualQ does not execute Appium/device farms; Maestro does not provide VRT or rolling page health
Roadmap
- Documented agent skill pairing VisualQ + Maestro prompts
- Optional webhook: Maestro Cloud run complete → VisualQ activity feed
- Shared Jira QA prompt across both MCP servers