kogiQA MCP
kogiQA MCP gives an agent a browser that finds page elements without selectors, for debugging web apps and writing e2e tests
- 88 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent opens pages, fills forms and signs in to accounts at the given addresses
- On first launch the server downloads and runs a browser binary
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/kogiqa-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent opens pages, fills forms and signs in to accounts at the given addresses
- On first launch the server downloads and runs a browser binary
This is third-party code. Review the repository files before installing.
What it does
kogiQA MCP launches a browser for an AI agent, and the agent works with the page in natural language, without selectors or screenshots. The developer compares the server with Playwright MCP: the kogiQA control algorithm finds the needed elements itself, so less time and fewer tokens go by. It installs with a single npx command. The repository also holds a Claude Code plugin: the same server with 47 browser_* tools, five skills (browser debugging, smoke test, exploratory testing, e2e test generation, app map) and three commands: console-errors, smoke-test and screenshot. Examples from the README: find why a pricing card overflows its container at 1280 pixels wide, visit the pages from the main menu and fix console errors in the source, walk through sign-up and write Cypress e2e tests.
Who it is for. Front-end developers and testers who hand an agent the job of running a site in a browser, finding console errors and writing e2e tests.
Good fit when
- A card on the pricing page overflows its container on a narrow screen and you need the cause with a ready CSS fix
- Errors pile up in the local app's console and the agent should walk the menu pages and fix the code
- Before a release a sign-up flow runs with a check that the cart badge shows one
- An app without tests needs its pages and features described in a Markdown document
- You want ten minutes of exploratory testing of forms with edge-case input
Not a fit when
- The tests are already written in Playwright and the team is happy with them: swapping the server adds nothing
- The page must not be opened in a browser under agent control, for example because of production accounts
- Node.js on the machine is older than version 20
Example request
Open http://localhost:5173, visit every page linked from the main menu, collect the console errors and fix them in the sourceMCP
- Transport
- stdio
- Authentication
- not required
Limitations
- Node.js 20 or newer is required; the browser binary downloads on first launch.
- The Claude Code plugin is connected by hand: claude --plugin-dir ./claude-plugin from a cloned repository. A permanent install goes through a marketplace or copying to ~/.claude/skills/kogiqa-browser.
- The advantage over Playwright MCP is claimed by the developer; the README has no independent measurements.
- The server visits any address you give it, production sites included: hand the agent logins and passwords for test environments only.
How to disable. claude mcp remove kogiqa-browser disconnects the server. The plugin is turned off on the /plugin page or by deleting its folder from ~/.claude/skills.
FAQ
How do I install kogiQA MCP in Claude Code?
Run claude mcp add kogiqa-browser npx kogiqa-mcp@latest. Node.js 20 or newer is required. The README calls npx kogiqa-mcp@latest without arguments an auto install.
How is kogiQA MCP different from Playwright MCP?
It includes its own kogiQA browser that finds elements without selectors. According to the developer this saves time and tokens. The README has no measurements.
Which clients does kogiQA MCP support?
The README names VS Code, Cursor, Windsurf, Claude Desktop, Goose, Junie and Claude Code. VS Code and Cursor have install buttons, and the others take the standard mcpServers configuration.
What is in the Claude Code plugin?
The server with 47 browser_* tools, five skills (browser-debug, smoke-test, exploratory-testing, generate-e2e-tests, map-app) and the console-errors, smoke-test and screenshot commands.
What is kogiQA MCP good for?
Debugging styles, fixing console errors, mapping a web app's features, generating e2e tests and exploratory testing. Each scenario appears in the README as a ready phrase for the agent.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server that spins up several browser agents to test a site for broken links, UI bugs and accessibility issues
A community Playwright MCP server: browser automation, screenshots, device emulation and test code generation
MCP server, agent and skills for end-to-end UI tests where the agent drives the computer through vision on cloud machines
MCP Interviewer checks an MCP server before an agent connects: provider limits, tool tests and a Markdown report.
An MCP server from Mozilla: an agent drives Firefox through WebDriver BiDi, reads the console and network, takes page snapshots and profiles loading
The official MCP server debugger: web UI, automation CLI and terminal UI in one package
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| kogiQA MCP (this card) | yes | not required | 88 | |
| Playwright MCP | yes | not required | 39,261 | drives the browser through the accessibility tree, while kogiQA finds elements with its own algorithm and ships QA skills |
| Chrome DevTools MCP | yes | not required | 54,879 | attaches to a live Chrome and reads network and traces, while kogiQA builds test flows in its own browser |
README in short
The README is short: what the server does, a comparison with Playwright MCP, installation for Claude Code, VS Code and Cursor, the standard configuration and six example requests with explanations. It ends with requirements: Node.js 20 and any MCP client. A separate README in the claude-plugin folder describes the plugin contents.