Web Browser (kogiQA)

com.atagonPublished by atagon.comv1.3.103Updated Oct 24, 2026

This web browser has been designed to help your agent debug and develop complex web applications.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives an assistant a selector-free browser for debugging, documenting and testing web applications through natural language.

What you can do
  • Drive a browser on web pages by describing tasks in natural language, without writing selectors.
  • Inspect pages to debug style and layout issues and to collect and fix console errors.
  • Explore a site's internal links and produce documentation of each page and its features.
  • Walk through user flows to smoke-test them, write end-to-end tests, and run exploratory testing.
When to use it
Useful when an agent needs to work inside a running web app: reproducing layout bugs, cleaning up console errors, mapping an app's pages, or generating and validating end-to-end tests against local or staging URLs.
Requirements
Runs locally over stdio via npx (package kogiqa-mcp); Node.js 20 or newer and an MCP client such as VS Code, Cursor, Windsurf, Claude Desktop, Goose or Junie. Desktop only; no authentication or environment variables declared.
Before you install
The browser acts on live pages, so prompts that log in, submit forms or click through flows can change data on the target site; point it at local or staging environments and use demo credentials. It can also edit source code when asked to fix errors.

Installation

In SourceWeft

  1. Open Web Browser (kogiQA) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

kogiQA MCP Web Browser

[npm version] [Total Downloads] [License]

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
  • Automatically write end-to-end tests
  • Automate exploratory testing of your application

See example prompts Usage Examples

kogiQA MCP vs Playwright MCP

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:

[Install in VS Code] [Install in VS Code Insiders]

Alternatively, install via the VS Code CLI:

bash
code --add-mcp '{"name":"kogiqa-browser","command":"npx","args":["kogiqa-mcp@latest"]}'
Cursor

[Install in Cursor]

Alternatively, go to Cursor Settings → MCP → Add new MCP Server and enter the command npx kogiqa-mcp@latest.

Standard configuration

For any other MCP client, add the following to your MCP configuration:

json
{  "mcpServers": {    "kogiqa-browser": {      "command": "npx",      "args": [        "kogiqa-mcp@latest"      ]    }  }}

Usage Examples

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

Source: readme.md at commit 8fc690a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.3.103LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts