Connect any AI agent to your browser

1. What AI Bridge Gives Your Agent

AI Bridge runs a Chrome extension plus a small local server. Together they let an AI agent read a page, click and type, take screenshots, run JavaScript, and make authenticated calls to a site's own internal API using the session you're already logged into, without you copying tokens around by hand.

Everything runs on your machine. The only outbound calls are license validation and an optional Firebase token refresh. See the Privacy Policy for details.

2. Prerequisites

1. Install the AI Bridge Chrome extension and open the side panel.
2. Run the installer: download Install AI Bridge (macOS, Apple Silicon), open the DMG, and double-click Install AI Bridge. The installer is notarized by Apple, so it opens with no security warning. It copies the bridge into place and registers it. No Terminal, no config.
3. Click Start Bridge in the side panel. This launches the local server, no terminal needed after setup.
4. Activate your license key (get one at whop.com/ai-bridge), required for tab control and Deep Capture.
5. Have a tab open in Chrome for the agent to act on.

Your agent shouldn't try to perform this setup itself. Have it check GET /health first and ask you to confirm the bridge is running before it attempts anything else.

3. Connecting

Base URL: http://127.0.0.1:9124. Most routes require a shared-secret header, generated on first run and stored locally:

KEY=$(cat ~/.ai-bridge/key)
curl http://127.0.0.1:9124/health
curl -H "X-Bridge-Key: $KEY" http://127.0.0.1:9124/tokens

GET /health and GET /info need no key, so they are always safe to probe first. A 401 means the key is missing or wrong; a 502 on a tab action means the extension isn't connected (check the side panel); an error mentioning the license means the key isn't active yet.

4. Use it as an MCP server (Claude Desktop, Cursor, Cline)

Prefer native tools over raw HTTP? AI Bridge ships a small MCP server (bridge/mcp_server.py) that exposes the whole toolkit as MCP tools: open and close tabs, click, type, upload, select, hover, scroll, read, screenshot, list page elements, run JS, and call_site_api (hit a site's own API through your captured session). Your MCP client drives your real browser through them, with no glue code.

Make sure the bridge is running (Start Bridge in the side panel), then add this to your client config (for Claude Desktop, claude_desktop_config.json). With uv it installs its own dependency automatically:

{
  "mcpServers": {
    "ai-bridge": {
      "command": "uv",
      "args": ["run", "/ABSOLUTE/PATH/TO/bridge/mcp_server.py"]
    }
  }
}

No uv? Use { "command": "python3", "args": ["/ABSOLUTE/PATH/TO/bridge/mcp_server.py"] } after pip install mcp. The server reads the bridge key from ~/.ai-bridge/key automatically. Everything still runs locally and every sensitive action stays human-approved.

5. Endpoint Reference

No key required

Requires X-Bridge-Key

6. Example: Read, then Act

Don't guess selectors. Read or screenshot the page first, then act:

curl -X POST http://127.0.0.1:9124/tab/screenshot -H "X-Bridge-Key: $KEY"

curl -X POST http://127.0.0.1:9124/tab/click -H "X-Bridge-Key: $KEY" \
  -d '{"selector":"[data-testid=save]","reason":"Save the draft"}'

Prefer calling a site's own API over clicking through its UI whenever one is available. It's faster and more reliable than DOM automation:

curl -X POST http://127.0.0.1:9124/proxy -H "X-Bridge-Key: $KEY" \
  -d '{"method":"GET","url":"https://example.com/api/v2/items","use_token":true}'

7. Best Practices

• Prefer /proxy over tab automation when the target site has an observable API for the action.
• Read before you click. Selectors drift; confirm the element exists first.
• Don't hammer endpoints. A 429 means slow down, not retry immediately.
• Pass a reason on tab actions. It shows up in your confirmation prompt so you always know why the browser just moved.
• Deep Capture (raw network/WebSocket recording) is toggled from the side panel, not the API. Turn it on only when you want an agent to see full request/response bodies.

8. Bonus: GHL Automation Skill

Included with your license: a portable skill that teaches your AI agent to automate GoHighLevel through AI Bridge, in three modes:

• Socrates: read-only audit of a subaccount (workflows, funnels, pipelines, forms, calendars, contacts) into a prioritized report.
• Aristotle: build and modify workflows, sequences, and triggers via the internal builder API.
• Daedalus: read and edit the React/Vite source of a GHL Vibe (AI Studio) site directly, no clicking in the editor.

It's a single SKILL.md: drop it into ~/.claude/skills/ghl-automation/ (or any agent that reads skills) and it drives everything through your local bridge. The macOS installer can set this up for you. It offers to install both this and the AI Bridge skill during setup. You can also download it manually below.