AGENTS DOCUMENTATION

Let local agents use search within clear boundaries

This guide covers Agent Bridge prerequisites, two integration paths, callable actions, and recovery. Agents receive bounded capabilities and structured results—not keys stored by the extension.

Install the extension

Confirm the runtime environment

Install and enable Juso in the browser that will run calls: Chrome, Edge, Chromium, Firefox, or another supported browser. The Agent Skill requires Python 3.11+. engine-search needs no AI service key; search needs the target provider configured first.

Enable two layers of consent

Open extension Options → General → Agent Bridge and enable the master switch. Enable the separate engine-search sub-switch as well when agents should search conventional engines through a real browser. Both are off by default.

Agent BridgeEvery Agent call uses a fresh loopback port, token, and request identity, then expires on completion, failure, or timeout.

Path A: the extension-delivered Agent Skill

In the same settings area, click “Download companion Agent Skill.” The extension stamps the Bridge address for the current browser into the package; after unzipping, keep scripts and reference intact and place the entire directory in your Agent skills folder.

Agent Skill

python scripts/juso_search.py list-providers
python scripts/juso_search.py list-engines
python scripts/juso_search.py search "latest AI research" --provider tavily

Path B: Server for MCP-native clients

Install the MCP Server with pip install juso-search (Python 3.10+). It uses stdio; set JUSO_BROWSER_PATH and, for Chrome, JUSO_EXTENSION_ID explicitly in the client's MCP configuration, then add profile and timeout only if needed.

MCP configuration

{
  "mcpServers": {
    "juso": {
      "command": "juso-search",
      "env": {
        "JUSO_EXTENSION_ID": "…",
        "JUSO_BROWSER_PATH": "…"
      }
    }
  }
}

FirefoxFor Firefox, set JUSO_BRIDGE_URL instead—the full moz-extension://…/bridge.html address. Firefox generates this Bridge address per installation; downloading the companion Agent Skill stamps the correct value automatically.

Read MCP Server configuration

Discover first, then call explicitly

Use list-providers and list-engines to discover the live capabilities first. search requires an explicit provider. For instances, call list-instances and then target an instance with search-instance. engine-search returns ordinary result metadata only, not AI summaries or knowledge panels.

Check boundaries before trying to bypass themFor extension_did_not_claim, confirm that Juso is installed and enabled, the Agent Bridge master switch is on, and the launched browser uses the intended profile. If engine-search returns extract-failed, check its separate sub-switch first; consent pages, challenge pages, and unsupported result layouts also return structured failures rather than empty success.

Done reading? Install and try it

Install the extension, enable Agent Bridge, and download the companion skill to make your agent's first call.

Install the extension View on GitHub