Booli MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add booli-mcp -- npx -y @chrischall/booli-mcp

{
  "mcpServers": {
    "booli-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/booli-mcp"
      ]
    }
  }
}

[mcp_servers.booli-mcp]
command = "npx"
args = ["-y", "@chrischall/booli-mcp"]

{
  "mcpServers": {
    "booli-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/booli-mcp"
      ]
    }
  }
}

{
  "servers": {
    "booli-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/booli-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: BOOLI_TRANSPORT (Selects the path: auto (default — direct fetch first, browser-bridge fallback when walled), fetchproxy (always the bridge), or direct), BOOLI_WS_PORT (Override the fetchproxy WebSocket port (the fleet shares 37149)), FETCHPROXY_WS_HOST (Bridge bind interface, a literal IP only (default 127.0.0.1). Keep on loopback; exists for a hosted child in its own network namespace), FETCHPROXY_IDENTITY_DIR (Absolute path for the long-term bridge identity keypair (default ~/.fetchproxy/identity/). Exists for a host that runs a separate child per caller).