Agent Browser

Agent Browser runs locally from a Node.js package published to the npm registry: aether-browser version 0.2.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y aether-browser@0.2.2. It reads these environment variables: AGENT_BROWSER_URL, AGENT_BROWSER_CONTROLLER_TOKEN (secret) and AGENT_BROWSER_OBSERVER_TOKEN (secret); set them in the client's configuration for this server. Required arguments: mcp.

Agent Browser runs locally from a Python package published to PyPI: aether-browser version 0.2.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx aether-browser. It reads these environment variables: AGENT_BROWSER_URL, AGENT_BROWSER_CONTROLLER_TOKEN (secret) and AGENT_BROWSER_OBSERVER_TOKEN (secret); set them in the client's configuration for this server. Required arguments: mcp.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "agent-browser": {
      "command": "npx",
      "args": [
        "-y",
        "aether-browser@0.2.2"
      ],
      "env": {
        "AGENT_BROWSER_URL": "<value>",
        "AGENT_BROWSER_CONTROLLER_TOKEN": "<secret>",
        "AGENT_BROWSER_OBSERVER_TOKEN": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect