Qa Use

What is Qa Use?

Qa Use is an MCP (Model Context Protocol) server that provides browser automation and QA testing capabilities. It integrates with desplega.ai to offer automated testing, session monitoring, batch test execution, and test guidance using AAA (Arrange-Act-Assert) framework templates.

How to use Qa Use?

Run with npx @desplega.ai/qa-use-mcp for stdio transport, or add --http --port 3000 for HTTP/SSE mode. Configure the server in your MCP client settings, setting the QA_USE_API_KEY environment variable with a desplega.ai API key. First-time setup requires either running init_qa_server with interactive=true or providing the API key.

Key features of Qa Use

• Launch and control Playwright browser instances (headless/headed)
• Create public tunnels for browser WebSocket endpoints
• Create, monitor, and control multiple QA testing sessions
• Real‑time progress notifications with MCP timeout protection
• Run multiple automated tests simultaneously with dependency management
• Search and list automated tests with pagination and filtering
• View test execution history with performance metrics and flakiness scores
• Pre‑built AAA framework templates for common test scenarios

Use cases of Qa Use

• Automate browser testing for web applications
• Run batch test suites with dependency ordering
• Discover and analyze test run history and flakiness
• Use intelligent templates to structure login, form, and e‑commerce tests
• Remotely monitor and interact with live test sessions

FAQ from Qa Use

What dependencies and runtime requirements does Qa Use have?

Qa Use requires Node.js to run via npx, a desplega.ai API key (obtainable through the register_user tool or at desplega.ai), and an MCP client that supports stdio or StreamableHTTP transport.

How do I authenticate with Qa Use?

For stdio mode, set the QA_USE_API_KEY environment variable. For HTTP mode, include a Bearer token with your API key in the Authorization header on each request.

What are the session limits and timeouts?

Up to 10 concurrent browser sessions are supported. Sessions have a default 30‑minute TTL, automatically refreshed on interaction. Each MCP tool call has a 25‑second maximum timeout.

What transport modes does Qa Use support?

Qa Use supports stdio (default for local MCP clients) and HTTP/SSE (StreamableHTTP, for web apps and remote access). The HTTP mode implements the MCP Streamable HTTP specification.

Where are browser sessions and test data managed?

Browser instances and tunnels are launched locally by the server. Test sessions and run data are managed through the desplega.ai API, and sessions are automatically cleaned up after expiry.