ChromeWalk MCP Server

ChromeWalk is an MCP integration. Local browser automation for AI agents: real-browser fetch, capture, smoke tests, cross-engine QA.

Packages and local setup

The published mcpb package is https://github.com/gator8125/ChromeWalk-MCP/releases/download/v14.0.0/chromewalk-14.0.0-win32-x64.mcpb. Its declared MCP transport is stdio.

The package declares CHROMEWALK_LICENSE: License key (sign up at https://api.chromewalk.com/register.html or run chromewalk register ). Read once when the MCP server starts and used to activate this device if it is not already activated (the same value as the bundle's license_key setting). Alternatively run chromewalk activate . Without an activated license every licensed tool call returns a license-required error.; CHROMEWALK_DATA_DIR: Optional per-process data directory (profiles, output, logs, license state). Defaults to %LOCALAPPDATA%\ChromeWalk on Windows, ~/Library/Application Support/ChromeWalk on macOS..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 14.0.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related browser automation MCP servers for tools that cover the same kind of work.