M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
K

kogiQA MCP

Community
Selector-free browser automation MCP server for AI agents, focused on debugging and testing.
How to install ↓ Compare GitHub source repository ↗
Category
Browser #29 of 32
Stars
★ 95 Popular
Transport
stdio (local process)
Runtime
Node.js 20+
Credentials
No credential needed
License
MIT
Last commit
Tools
6
38FMRS · D

The kogiQA MCP Web Browser is a practical browser automation server that enables AI agents to interact with web pages efficiently through natural language and without needing selectors. It is particularly suited for development and testing scenarios, but requires attention to runtime environment and security risks.

Strongest · Setup experience 12/20 Weakest · Reliability 5/20

Reliability
5/20
Security and permissions
5/20
Maintenance
8/20
Documentation
8/20
Setup experience
12/20
Why each score
Reliability 5/20
README and manifest describe a stdio npm server, so the happy path is plausible. No source files, tool list, tests, or CI workflow were supplied; the actual handshake, declared tools, and error behavior cannot be verified. Deducted for lack of any execution evidence. Score 5.
Security and permissions 5/20
No credentials, environment variables, or data-flow documentation are present in the supplied material. The server automates a browser and may open arbitrary URLs and trigger page actions, so side effects and network boundaries are unclear. No malware or red-line indicators were found, but missing disclosure and permission/confirmation evidence lowers the score.
Maintenance 8/20
MIT license is declared, repository is not archived and has zero open issues, and a 1.3.40 npm release exists. However no commit frequency, dependency-update history, or issue-response records were provided; stars are only discovery signals. Deducted for lack of sustained-governance evidence.
Documentation 8/20
README covers installation via npx, client-specific setup for Claude Code/VS Code/Cursor, standard JSON config, requirements, and several usage examples. It lacks a tool-reference list, parameter docs, troubleshooting, limitations, and auth/data disclosure. Deducted for those gaps.
Setup experience 12/20
Setup is a single npx command plus copy-paste client configs; Node.js 20 requirement is explicit and several mainstream clients are covered. No execution evidence (CI or committed tests) was supplied, and browser runtime dependencies/platform caveats are not documented, so score is capped conservatively below the 15 static limit.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkControls a browser

Best for

  • Web developers debugging and testing complex web applications
  • QA engineers automating end-to-end testing
  • AI agents needing selector-free browser interaction

Not for

  • Tasks requiring high-precision visual verification (e.g., image recognition)
  • Bypassing browser security restrictions
  • Deployment in environments without Node.js 20+

Required permissions

  • Requires Node.js runtime
  • Requires network access to navigate web pages
  • May require access to local development servers
  • Requires ability to execute JavaScript code

Risks and side effects

  • May execute unverified navigation or actions, leading to unexpected behavior
  • May expose sensitive information (e.g., console logs)
  • Depends on a third-party service (kogiQA)
  • Potential security risks if browser automation is misused

Setup

Before you start

Runtime：Node.js 20+

  1. Ensure Node.js 20 or later is installed.
  2. In an MCP-capable client (such as Claude Desktop, VS Code, Cursor), add the server using npx: npx kogiqa-mcp@latest.
  3. For VS Code, use the provided buttons or CLI command; for Cursor, add the MCP server in settings with the above command.
  4. For other clients, add the provided JSON configuration to your MCP settings.
claude_desktop_config.json 
{
  "mcpServers": {
    "kogiqa-browser": {
      "command": "npx",
      "args": [
        "kogiqa-mcp@latest"
      ]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "kogiqa-browser": {
      "command": "npx",
      "args": [
        "kogiqa-mcp@latest"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add kogiqa-browser -- npx kogiqa-mcp@latest

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After configuring the client with npx kogiqa-mcp@latest, check that browser_navigate, browser_act, browser_extract, browser_evaluate, browser_console, and browser_screenshot appear in the client's tool list, or ask the agent to navigate to a page and take a screenshot to prove the connection.

Troubleshooting

  1. Check that Node.js version is 20 or higher
  2. Verify MCP client configuration with command 'npx kogiqa-mcp@latest'
  3. Check network connectivity to reach target web pages
  4. Inspect client logs for error messages
  5. Ensure target application is running at an accessible address

Things to try

Once connected, you can ask your AI assistant things like:

  • Open http://localhost:3000, log in with the demo credentials, add the first product to the cart, and verify the cart badge shows "1".
  • Go to https://myapp.example.com/pricing and check why the "Pro" plan card overflows its container at a 1280px-wide viewport, then suggest a CSS fix.
  • Navigate to http://localhost:5173, open every page linked from the main menu, collect all console errors, and fix them in the source code.
  • 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.

Tools 6

browser_navigate writes
Navigate to a specified URL.
browser_act writes
Perform actions on the page (e.g., click, type, hover).
browser_extract read-only
Extract structured data or text from the page.
browser_evaluate writes
Execute JavaScript code in the page context.
browser_console read-only
Retrieve or clear browser console logs.
browser_screenshot read-only
Take a screenshot of the current page (for visual debugging).

Use cases

Smoke-test a user flow: open a local app, log in, add a product, and verify cart badge.
Debug a style issue: check element overflow on a specific viewport and suggest CSS fixes.
Fix console errors: navigate through all pages, collect console errors, and fix them in source.
Map and document your app: explore internal links and produce a Markdown document describing each page.
Generate end-to-end tests: write Cypress tests for sign-up flow covering happy path and validation errors.
Exploratory testing: perform 10 minutes of exploratory testing, trying edge-case inputs and reporting issues.

Supported clients

Claude Desktop
VS Code
Cursor

Listed from the project's documentation, not tested by this site.

Overview

The kogiQA MCP Web Browser is a Model Context Protocol (MCP) server that provides browser automation capabilities using the kogiQA browser control algorithm. It allows LLMs to interact with web pages through natural language, bypassing the need for screenshots or visually-tuned models, and without requiring selectors, saving time and tokens. It is designed for debugging style issues, automatically fixing console errors, mapping and documenting web app functionality, automatically writing end-to-end tests, and automating exploratory testing.

Similar servers

Compare with other MCP servers

Source revision 28326fa00edb Data synced 2026-10-12 Read the FMRS scoring method