kogiQA MCP Server
The kogiQA MCP Server harnesses the full power of kogiQA's browser automation and delivers it directly to your AI coding agents via the Model Context Protocol (MCP). You can control browsers, inspect network traffic, debug issues and generate tests, all through natural language prompts.
Getting Started
Prerequisites
Install kogiQA Desktop to run the local MCP server:
- Download kogiQA Desktop
- Start the application (the MCP server will be available automatically)
MCP Server URL
Once kogiQA Desktop is running, the MCP server is available at:
http://localhost:4239/mcp
Claude Code Integration
Option 1: Using the Claude Code CLI
If you are using Claude Code, add the kogiQA MCP server with:
claude mcp add --transport http kogiqa-browser http://localhost:4239/mcp
Option 2: Direct Coding Agent
If you are using a direct coding agent or another MCP-compatible client, simply point it to:
http://localhost:4239/mcp
Example Prompts
Here are some powerful ways to use the kogiQA MCP server. Each prompt is prefixed with use kogiQA Browser: so the agent knows to invoke the browser automation tools.
$ Use the KogiQA browser. Please take a look at my website, kogiqa.com, and check the logs and network requests. Then, give me a list of all the bugs you found.
The MCP server accesses browser console logs, network history, and page state to help diagnose issues.
$ Use kogiQA Browser: Go to example.org and look at all pages and find any misspellings.
Let the agent crawl your site and report spelling errors automatically.
$ Use kogiQA Browser: Go to example.org and give me a summary of all features of the page.
Get a comprehensive overview of a website's functionality and UI elements.
$ Use the KogiQA browser. Go to example.org and create a Cypress test to check that the page is working correctly.
Generate end-to-end Cypress tests based on real user interactions captured by the browser.
$ Use kogiQA Browser: Go to kogiqa.com and write a Playwright test to check if I use the search for click action I get to the demo code for that action.
The agent navigates, interacts, and writes robust Playwright tests. See the generated example below.
$ Use kogiQA Browser: Look at my test code in this folder the login tests fail. Please debug it and fix it.
The agent reads local test files, runs them via kogiQA, analyzes failures, and suggests or applies fixes.
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:
The kogiQA MCP Server supports all standard browser actions including navigate, click, type, scroll, screenshot, network inspection, accessibility checks, email testing, and more.