MCP server that generates AIQUAA BDD and Playwright artifacts with business-rule traceability.
Most browser automation work still happens through a UI a human drives. Aiquaa MCP server moves it into the conversation instead. MCP server that generates AIQUAA BDD and Playwright artifacts with business-rule traceability.
El resultado no es un test aislado. Es una cadena de evidencia:
aiquaa-playwright-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 8 tools. What each one is for:
qa_bdd — Features Gherkin desde texto o requirement_idqa_pruebas — Steps, hooks, reporter, configuración, auth y pipelinesqa_reglas — Reglas paginadas con filtrosqa_mapear — Features etiquetados con @rule:qa_cobertura — Cobertura y estado por regla/featureqa_contexto — Contexto estructural enfocado mediante CodeGraphqa_memoria — Decisiones y aprendizajes recuperados desde Engramqa_recordar — Memoria curada e idempotente por topic_keyConfiguration is passed through the environment: CODEGRAPH_BIN, CODEGRAPH_ALLOWED_ROOTS, ENGRAM_BIN, ENGRAM_PROJECT_PREFIX, AIQUAA_API_BASE_URL, AIQUAA_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Aiquaa's toolset — qa_bdd, qa_pruebas, qa_reglas and 5 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| qa_bdd | Features Gherkin desde texto o requirement_id |
| qa_pruebas | Steps, hooks, reporter, configuración, auth y pipelines |
| qa_reglas | Reglas paginadas con filtros |
| qa_mapear | Features etiquetados con @rule:<ID> |
| qa_cobertura | Cobertura y estado por regla/feature |
| qa_contexto | Contexto estructural enfocado mediante CodeGraph |
| qa_memoria | Decisiones y aprendizajes recuperados desde Engram |
| qa_recordar | Memoria curada e idempotente por topic_key |
{
"mcpServers": {
"aiquaa-playwright": {
"command": "npx",
"args": ["-y", "aiquaa-playwright-mcp-server"],
"env": {
"CODEGRAPH_BIN": "your-value",
"CODEGRAPH_ALLOWED_ROOTS": "your-value",
"ENGRAM_BIN": "your-value",
"ENGRAM_PROJECT_PREFIX": "your-value",
"AIQUAA_API_BASE_URL": "your-value",
"AIQUAA_ACCESS_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CODEGRAPH_BIN | Configuration value read at startup. | Optional |
| CODEGRAPH_ALLOWED_ROOTS | Configuration value read at startup. | Optional |
| ENGRAM_BIN | Configuration value read at startup. | Optional |
| ENGRAM_PROJECT_PREFIX | Configuration value read at startup. | Optional |
| AIQUAA_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| AIQUAA_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.