MCP Servers / productivity / qa-use

qa-use

JSON →
stdionone22productivity

Provides comprehensive browser automation for QA testing capabilities.

Install
How to run this server
[ { "cmd": "npx\nnpx", "imports": [] } ]
server path: qa-use
Tools
What this server exposes
qa-use test init
Initialize test directory with example
qa-use test run <name>
Run a test by name
qa-use test run --all
Run all tests in qa-tests/
qa-use test list
List local tests
qa-use test list --cloud
List cloud tests
qa-use test validate <name>
Validate test syntax
qa-use test sync --push
Push local tests to cloud
qa-use test sync --pull
Pull cloud tests to local
qa-use test export <id>
Export cloud test to local file
qa-use browser create
Start browser session
qa-use browser goto <url>
Navigate to URL
qa-use browser snapshot
Get page element refs
qa-use browser click <ref>
Click element by ref
qa-use browser fill <ref> <value>
Fill input field
qa-use browser screenshot <path>
Save screenshot
qa-use browser run
Interactive REPL mode
qa-use browser close
Close browser session
qa-use browser status --list
List active sessions across processes
qa-use tunnel start http://localhost:3000 --hold
Hold a public tunnel
qa-use tunnel ls
List active tunnels
qa-use tunnel status <target|hash>
Detail for one entry
qa-use tunnel close <target|hash>
Force-release a tunnel
qa-use doctor
Reap stale sessions/tunnels
qa-use doctor --dry-run
Preview what would be reaped
qa-use api ls
List endpoints from live/cached OpenAPI
qa-use api <path>
Send API request to endpoint
qa-use api ... --refresh
Force OpenAPI spec refresh
qa-use api ... --offline
Use cached spec without network
qa-use check list --app-config <app-config-id> --q login
List checks with optional query filter
qa-use check info <check-id>
Get check details
qa-use check create
Create a new check
Configuration
Environment & auth
authnone
envQA_USE_API_KEY
envQA_USE_API_URL
envQA_USE_APP_URL
envQA_USE_DEFAULT_APP_CONFIG_ID
Resources
qa-use — MCP Server · libregistry