Skip to content

Installation

  • Firefox (any recent version)
  • Node.js (v18 or later) — includes npm, which the installer requires
  • At least one MCP client: Claude Code, Hermes Agent, Pi Agent, omp, or a standard mcp client

The installers accept --target <claude|omp|hermes|pi|all>. The default target is claude.

  1. Clone the repository:

    Terminal window
    git clone https://github.com/boot-industries/claudezilla.git
    cd claudezilla
  2. Run the installer for the target harness:

    Terminal window
    ./install/install-macos.sh --target <claude|omp|hermes|pi|all>

    For Claude Code alone, ./install/install-macos.sh keeps the default claude target. The installer installs MCP dependencies and the Firefox native messaging manifest. It also configures the selected client as described below.

  3. Load the extension in Firefox:

    • Open about:debugging in Firefox
    • Click This Firefox in the sidebar
    • Click Load Temporary Add-on
    • Navigate to the extension/ directory and select manifest.json
  4. Click the Claudezilla icon in the toolbar to verify the connection.

  1. Clone the repository:

    Terminal window
    git clone https://github.com/boot-industries/claudezilla.git
    cd claudezilla
  2. Run the installer:

    Terminal window
    ./install/install-linux.sh --target <claude|omp|hermes|pi|all>

    On Linux the native manifest is placed at ~/.mozilla/native-messaging-hosts/claudezilla.json. Everything else works the same as macOS.

  3. Load the extension in Firefox using the same about:debugging steps described above.

The claude target automatically adds mcp__claudezilla__* to ~/.claude/settings.json permissions and registers the server in ~/.claude/mcp.json:

{
"mcpServers": {
"claudezilla": {
"command": "node",
"args": ["<path>/mcp/server.js"]
}
}
}

Claude Code uses lazy discovery by default. See Tool Discovery.

The omp target merges this stdio registration into ~/.omp/mcp.json:

{
"mcpServers": {
"claudezilla": {
"command": "node",
"args": ["<path>/mcp/server.js", "--all-tools"],
"timeout": 120000
}
}
}

The 120-second timeout replaces omp’s 30-second default because browser operations can be long-running.

The hermes target prints a registration for ~/.hermes/config.yaml:

mcp_servers:
claudezilla:
command: node
args:
- <path>/mcp/server.js
- --all-tools

The pi target prints a registration for ~/.pi/config.json:

{
"mcpServers": {
"claudezilla": {
"command": "node",
"args": ["<path>/mcp/server.js", "--all-tools"]
}
}
}

Register Claudezilla as a stdio MCP server with the command node and the argument <path>/mcp/server.js. Add --all-tools when the client only discovers tools once at startup. Clients that support dynamic notifications/tools/list_changed can omit it and use lazy discovery.

  1. Clone the repository:

    Terminal window
    git clone https://github.com/boot-industries/claudezilla.git
    cd claudezilla
  2. Run the PowerShell installer:

    Terminal window
    .\install\install-windows.ps1

    The Windows installer uses named pipes for IPC instead of Unix sockets, sets ACL-based security on the pipe, and registers the native manifest in the Windows Registry.

  3. Load the extension in Firefox via about:debugging as described above.

Once installed, start a new client session and run:

Use firefox_navigate to open https://example.com

If the client opens Firefox and navigates to the page, the installation is working.