Agent-browser MCP Server

Self-hosted Chrome for AI agents, with a live noVNC view a human can take over.

Local serverstdio

What is the Agent-browser MCP Server?

Agent-browser is an MCP integration. Self-hosted Chrome for AI agents, with a live noVNC view a human can take over.

Packages and local setup

The published npm package is aether-browser, version 0.2.2. Its declared MCP transport is stdio.

The package declares AGENT_BROWSER_URL: Base URL of your Agent Browser server. Defaults to http://127.0.0.1:8092.; AGENT_BROWSER_CONTROLLER_TOKEN: Controller token, if the server runs authenticated.; AGENT_BROWSER_OBSERVER_TOKEN: Observer token for read-only health and snapshot calls..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

The published pypi package is aether-browser, version 0.2.2. Its declared MCP transport is stdio.

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 0.2.2 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.

Configuration

VariableDescriptionRequired
AGENT_BROWSER_URLBase URL of your Agent Browser server. Defaults to http://127.0.0.1:8092.Optional
AGENT_BROWSER_CONTROLLER_TOKENController token, if the server runs authenticated.Optional
AGENT_BROWSER_OBSERVER_TOKENObserver token for read-only health and snapshot calls.Optional