LABSCO SUMMARY
Selector-free is a token argument as much as a robustness one.
The comparison the project draws with a Playwright-based server is that the agent never has to locate the element first — it states the action and the control algorithm resolves it, saving both the round trips and the tokens spent describing the DOM. The same property means your steps survive a redesign that would have broken a selector.
What it is
A browser automation server built on kogiQA's browser control algorithm: the agent says what to do in natural language and the browser does it, without CSS selectors and without a vision model reading screenshots.
What you get
- Pages driven by description — log in, add a product to the cart, check a badge — with no selector to write or maintain
- Console errors collected across the pages you visit, so the agent can go and fix them in the source
- Layout and style problems inspected at a viewport width you name
- A site explored and documented: follow internal links to a depth and produce a Markdown description of each page and its features
- End-to-end tests written from a walkthrough of the real flow, covering the happy path and the validation errors
- Exploratory testing — edge-case inputs into every form it finds, with a report of what looked broken
Requirements
Node.js 20 or newer and an MCP client. Auto-install with npx kogiqa-mcp@latest; Claude Code takes claude mcp add kogiqa-browser npx kogiqa-mcp@latest, and VS Code, Cursor and Windsurf all accept the same command.
Setup effort
One command — npx kogiqa-mcp@latest
USE CASES
01
Smoke-testing a flow after a deploy
Describe the path — log in, add to cart, check the badge — and it walks it on the running site.
02
Clearing console errors across a site
Open every page linked from the menu, collect the errors, and fix them in the source.
03
Chasing a layout bug at a specific width
Load the page at the viewport width where it breaks and get back what is overflowing, with a suggested fix.
04
Writing end-to-end tests from the real thing
Walk the sign-up flow once and generate the test cases from what actually happened.
BEFORE YOU INSTALL
What to know first
Requires
npx on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
npx kogiqa-mcp@latestMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add kogiqa-browser npx kogiqa-mcp@latestVS Code
VS CODE · TERMINAL
code --add-mcp '{"name":"kogiqa-browser","command":"npx","args":["kogiqa-mcp@latest"]}'Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"kogiqa-browser": {
"command": "npx",
"args": [
"kogiqa-mcp@latest"
]
}
}
}