kogiQA MCP Server
kogiQA is an MCP server that provides a browser for your coding agent. Once installed, Claude Code, Codex or any other MCP client can open pages, click on things and check their own work while coding, so you won't find out later that the 'fix' has broken the layout.
If you've ever seen an agent confidently rewrite your CSS without having any idea what the page actually looks like, you'll understand the problem this solves.
What it's useful for
CSS debugging: the agent examines the rendered page rather than guessing what the styles do.
Visual bugs: if your model accepts image input, the agent can take a screenshot and identify the problem.
Broken flows: login not working, checkout acting strangely whatever the problem, the agent can walk through the flow step by step to find where it breaks.
Testing while you develop: this is the main feature, honestly. The agent modifies some code, checks the page and immediately knows whether it has worked. You no longer have to manually verify everything.
Getting started
Install it:
npx kogiqa-mcp install
Open your coding CLI or AI tool and type something like:
Use the kogiQA mcp server to go to kogiQA.com and click the documentation button
Hit enter and you'll watch it work: open the page, find the button, click it.
No config file. No selector syntax to learn. If you can describe what you want in a sentence, that's the whole API.
Claude Code
claude mcp add kogiqa-browser npx kogiqa-mcp@latest
VS Code
Click one of the buttons below to install directly in vs code:
Or install via the VS Code CLI:
code --add-mcp '{"name":"kogiqa-browser","command":"npx","args":["kogiqa-mcp@latest"]}'
Cursor
Or go to Cursor Settings → MCP → Add new MCP Server and use command and type in npx kogiqa-mcp@latest.
Standard configuration
{
"mcpServers": {
"kogiqa-browser": {
"command": "npx",
"args": [
"kogiqa-mcp@latest"
]
}
}
}
See:
Why not just use one of the other browser MCPs?
Most of them dump the page's full HTML into the model's context. While this works, a single page load can use up a large part of your context window, and this has an impact on every step of every task.
kogiQA doesn't hand over the HTML. It comes with a set of built-in tools that return only what the model actually needs, so token usage drops significantly. The model never deals with selectors; it says 'click the login button' and the browser figures out what that means.
There is also less churn in the context window, meaning it's faster since the agent skips the whole inspect-the-DOM, pick-a-selector, hope-it-works routine and just acts.
Browser API Reference
All browser actions exposed through the MCP server are documented in the JavaScript SDK API reference. Explore the full list of available methods and their parameters.