pickfit

BrowseMCP servers

kogiQA MCP Web Browser

MCP server giving LLMs selector-free browser automation to debug and develop web apps.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js 20 or newer
  1. install kogiqa-mcp globally via npm

    npm install -g kogiqa-mcp@latest

Add it to your agent

claude mcp add kogiqa-mcp -- kogiqa-mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "kogiqa-mcp": {
      "command": "kogiqa-mcp",
      "args": []
    }
  }
}

Add kogiqa-mcp as an MCP server in your MCP client, then ask the assistant to open a web page with the browser tools.

What it does

  • Control web pages with plain language
    Not tested
  • Debug style issues on web pages
    Not tested
  • Fix console errors automatically
    Not tested
  • Write end-to-end tests automatically
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Works offline

Good for

  • 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

An alternative to Playwright MCP.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client connects and lists its tools

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 1.0.0

An MCP client handshake over stdio listed 47 tools.

Differences the test machine hit

  • README: npx kogiqa-mcp@latest
    In the test: npm install -g kogiqa-mcp@latest so `kogiqa-mcp` is on PATH for offline replay; npx would fetch on every launch
  • README: --help exits with usage
    In the test: `kogiqa-mcp --help` prints setup help then starts the MCP proxy on stdio and never exits (had to be killed); use the MCP probe handshake instead

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.