Browser

Browser support connects Anyy to a managed browser MCP server and exposes Anyy-managed browser tools through the browser toolset.

This is an MCP integration path, not a built-in browser engine. The local CLI configures the MCP server block, validates discovered tools, and activates the toolset when requested.

Status

Check local config and runtime visibility:

anyy browser status
anyy browser status --json

The status output reports whether the managed browser MCP server is configured, enabled, which URL is saved, how many tools are allowed, whether the gateway is reachable, and whether browser is visible in the runtime tool catalog.

Doctor

Run doctor when status is not enough:

anyy browser doctor
anyy browser doctor --json

Doctor probes the configured MCP server, verifies required tools, rejects excluded managed tools, and checks that the runtime can discover the server.

Required discovered tools are:

Tool
browser_navigate
browser_snapshot
browser_click
browser_type
browser_wait_for
browser_take_screenshot
browser_tabs
browser_close

Connect

For a local browser MCP node, the default URL is:

http://localhost:8931/mcp

Connect and activate:

anyy browser connect

For a remote HTTPS MCP endpoint:

anyy browser enable --url https://browser-node.example.com/mcp

connect can use the local default URL. enable requires --url.

During connect, Anyy discovers tools and keeps only the managed allowlist. It then writes mcp.client.servers.browser and adds browser to the default toolset list.

Disconnect

Disable the managed browser server and remove the default toolset:

anyy browser disconnect
anyy browser disable

Both commands apply the same disable operation. If the gateway supports runtime config RPC, the change is applied through the gateway. Otherwise the CLI writes config.yaml; restart the gateway before expecting runtime visibility to change.

Configuration

The managed config shape is:

mcp:
  client:
    enabled: true
    servers:
      browser:
        enabled: true
        display_name: Browser
        transport: http
        url: http://localhost:8931/mcp
        call_timeout_ms: 180000
        tools:
          include:
            - browser_navigate
            - browser_snapshot
            - browser_click
            - browser_type
            - browser_wait_for
            - browser_take_screenshot
            - browser_tabs
            - browser_close

toolsets:
  default:
    - browser

The actual include list can contain the broader managed allowlist discovered at connect time, including navigation, click, type, form fill, selection, check, uncheck, key press, wait, screenshots, tabs, close, and dialog handling tools.

Excluded managed tools include browser code execution, file upload, network requests, console messages, route management, cookie/storage access, and PDF save. If those appear in the include list, doctor fails.

Security Boundaries

Boundary	Behavior
Transport	Plain HTTP MCP URLs must be local. Use HTTPS for remote browser nodes.
Tool filtering	Anyy validates required tools and rejects excluded browser MCP tools.
Toolset visibility	Browser tools appear only through browser when the server is enabled and the toolset is selected. Raw mcp-browser tools are for explicit MCP diagnostics.
Secrets	URLs and MCP status errors are redacted before display.
Policy	Anyy browser tools own model-visible risk, approval, timeout, and output projection. Raw MCP policy applies only when mcp-browser is explicitly selected for diagnostics.

For MCP concepts and field-level config, see MCP Integration.