Skip to main content

Browser Integration

Browser integration connects Anyy to a managed browser MCP server. Anyy exposes a stable browser toolset and keeps raw mcp-browser backend tools for explicit MCP diagnostics.

This page covers the integration wiring. For user-facing behavior, see Browser.

Connect​

For a local browser MCP endpoint, run:

anyy browser connect

The default local URL is:

http://localhost:8931/mcp

For a remote HTTPS endpoint:

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

connect can use the local default. enable requires an explicit URL.

What Gets Written​

Anyy writes a managed MCP server named browser:

mcp:
  client:
    enabled: true
    servers:
      browser:
        enabled: true
        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 be broader when the server exposes other approved browser tools, but Anyy still validates required tools and rejects excluded managed browser tools.

Doctor Checks​

Use status for a quick view:

anyy browser status

Use doctor when a browser tool does not appear or the endpoint changed:

anyy browser doctor

Doctor checks the saved URL, validates the managed include list, probes discovery when it can, and reports whether the running gateway can see browser.

Disconnect​

anyy browser disconnect

or:

anyy browser disable

Both disable the managed browser server and remove the default browser toolset. If the gateway is not reachable, the CLI writes config locally; restart the resident gateway before expecting the runtime to change.

Safety Notes​

  • Plain HTTP browser MCP URLs must be local.
  • Use HTTPS for remote browser nodes.
  • Browser tools are visible only when the server is enabled and browser is selected.
  • Raw MCP browser tools are not activated by browser setup by default.
  • The managed MCP server uses a transport call timeout ceiling above the browser phase budgets.