This web browser has been designed to help your agent debug and develop complex web applications.
com.atagon/kogiqa-mcp (MCP) Server
The com.atagon/kogiqa-mcp Model Context Protocol server provides browser automation capabilities using kogiQA. It is intended for LLMs to interact with web pages through natural language, reducing reliance on screenshots or visually-tuned models. It focuses on debugging, error resolution, documentation, and test automation for complex web applications.
🛠️ Key Features
Browser automation via kogiQA
Natural-language interaction with web pages
Designed to avoid needing screenshots or visually-tuned models
🚀 Use Cases
Debug style issues on a web page
Automatically fix console errors
Map and document web app functionality
Automatically write end-to-end tests
Automate exploratory testing
⚡ Developer Benefits
Natural-language workflows for web page interaction
Supports debugging and automated improvement of console issues
Helps produce documentation and end-to-end tests
⚠️ Limitations
Source content does not specify constraints, supported environments, or tool coverage beyond the browser automation scope.
A Model Context Protocol (MCP) server that provides browser automation capabilities using kogiQA. This server
enables LLMs to interact with web pages through natural language, bypassing the need for screenshots
or visually-tuned models.
For what to use:
Debug style issues on your page
Automatically fix console errors.
Map and document the functionality of your web app
The kogiQA MCP Server provides a browser which incorporates the capabilities of the kogiQA browser control algorithm.
This enables agents to interact with pages without a selector, saving time and tokens.
Installation
Auto install:
bash
npx kogiqa-mcp@latest
Claude Code
bash
claude mcp add kogiqa-browser npx kogiqa-mcp@latest
VS Code
Click one of the buttons below to install directly in vs code:
Once the server is configured, simply talk to your agent in natural language. Because kogiQA is selector-free, you describe what you want done — not how to find the elements.
Smoke-test a user flow
text
Open http://localhost:3000, log in with the demo credentials, add the first product to the cart, and verify that the cart badge shows "1".
Debug a style issue
text
Go to https://myapp.example.com/pricing and check why the "Pro" plan card overflows its container on a 1280px-wide viewport. Suggest a CSS fix.
Fix console errors
text
Navigate to http://localhost:5173, open every page linked from the main menu, collect all console errors, and fix them in the source code.
Map and document your app
text
Explore https://staging.example.com, follow all internal links up to two levels deep, and produce a Markdown document describing each page and its main features.
Generate end-to-end tests
text
Walk through the sign-up flow at http://localhost:3000/signup and write Cypress end-to-end tests covering the happy path and validation errors.
Exploratory testing
text
Do 10 minutes of exploratory testing on http://localhost:8080: try edge-case inputs in every form you find and report anything that looks broken or inconsistent.
Requirements
Node.js 20 or newer
VS Code, Cursor, Windsurf, Claude Desktop, Goose, Junie or a other MCP client