Walzone Browser Tool

Enhance Your Browsing with Walzone Browser Tool

Launch Walzone Browser Tool

Control a different (even remote) Chrome browser that has the Walzone extension installed. This page is the controller; actions run in the target browser.

Heads up: Install the extension on the target browser, open its popup to copy the browser token, then paste that token when launching the assistant here.

On this site

Use this page as a controller. It sends commands to a separate/remote Chrome where the extension runs. Paste the token from that target browser’s extension popup, then ask for tasks (e.g., “Go to example.com and summarize the headline”).

Open assistant

New: MCP Server

Prefer Model Context Protocol? Connect to our MCP server at https://mcp.walzone.com/mcp (2025-06-18 JSON-RPC/HTTP). It exposes the Walzone browser assistant as a tool, plus a ready-made handshake payload.

See MCP details

Install the Walzone Browser Tool Extension

Install the Walzone Browser Tool extension, then copy the browser token from its popup. This token lets the assistant control your browser securely.

  1. Download the extension by clicking the button below.
  2. Extract the downloaded file to a folder on your computer.
  3. Open Chrome and navigate to chrome://extensions/.
  4. Enable the Developer Mode toggle in the top-right corner of the page.
  5. Click on the Load unpacked button and select the folder where you extracted the extension files.
  6. Once loaded, the Walzone Browser Tool will appear in your list of extensions and in the Chrome toolbar.
Download Walzone Browser Tool – Chrome Extension

Once you have installed the extension, open the popup and copy the browser token:

If you have any issues or questions, feel free to contact our support team. Happy browsing with Walzone Browser Tool!

Need a faster, custom solution?

If the Walzone Browser Tool feels too slow or doesn't cover your specific workflow, we can build a customized automation script tailored to your task.

Contact: admin@walzone.com — we’ll reply within 24 hours.

Request a custom script

Model Context Protocol Server (New)

Endpoint: https://mcp.walzone.com/mcp (single MCP endpoint, 2025-06-18 JSON-RPC/HTTP) with built-in handshake payload. No extra deps; run the server with python3 mcp_server.py --config config.json.

Auth options

Static API keys or full OAuth 2.0 (authorization code + client credentials, discovery docs, dynamic client registration, JWKS placeholder). Tokens are short-lived bearer tokens; optional on-disk store and per-client tool allowlists. Can also run “open” with no auth.

Tools & resources

Drop models under models/ to expose tools automatically, including the Walzone browser assistant (scripted tasks or single actions; token-per-call). Tool metadata ships with schemas, examples, and usage text. Resource routes (resources/list, resources/get) are scaffolded for your own data.

HTTP surface

Health check, MCP transport, OAuth discovery/authorize/token/register/keys, and resource discovery. Path/base-prefix friendly for reverse proxies (Apache/NGINX) with HTTPS termination; logs to stdout.

Config-driven

config.json controls API keys, OAuth clients, tool rules, token TTL/store path, base path, and browser assistant settings. Pure Python 3.10+; no external dependencies.

Quick start (clients)

  • Bearer token: <your-bearer-token>
  • OAuth client: id <your-client-id> (auth code + client credentials flows). Discovery endpoints live under the same base path.
  • See HOWTO/CLIENT_ACCESS for sample curl flows.