Skip to content

llms-install.md

Latest commit

 

History

History
80 lines (57 loc) · 3.17 KB

llms-install.md

File metadata and controls

80 lines (57 loc) · 3.17 KB
Raw

Browser MCP — AI-assisted install guide

This file is written for an AI assistant (e.g. Cline) setting up Browser MCP by Agent360. Follow it top to bottom. There is one step only a human can do — loading the Chrome extension — and it is called out clearly. Do not claim the setup is finished until that step is confirmed.

What this server needs to work

Browser MCP has two parts that must both be present:

  1. The MCP server (@agent360/browser-mcp, npm, stdio) — you can configure this.
  2. A Chrome extension — this is what actually drives the user's real, logged-in Chrome. Chrome does not allow an extension to install itself from npm, so a human loads it once.

The server will start and list its 40 tools without the extension, but the tools only do anything once the extension is loaded and Chrome is running. Tell the user this plainly.

Step 1 — register the MCP server with the client

Use the client's own MCP-registration command. Do not use npx @agent360/browser-mcp install for this — that command copies extension files and writes ~/.claude/mcp.json, which Claude Code does not read. Registering must go through the client.

Claude Code:

claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest

OpenAI Codex:

codex mcp add browser-mcp -- npx @agent360/browser-mcp@latest

Any other client (Cursor, VS Code, Windsurf, Cline…) — write this into that client's MCP config:

{
  "mcpServers": {
    "browser-mcp": { "command": "npx", "args": ["@agent360/browser-mcp@latest"] }
  }
}

Keep the @latest: it is what makes the server self-update on each run.

Step 2 — the Chrome extension (HUMAN action required)

Present both options to the user and let them choose. Option A is the easy, auto-updating path; recommend it.

Option A — Chrome Web Store (recommended, closest to one-click):

  1. Install from the Chrome Web Store: https://chromewebstore.google.com/detail/agent360-browser-mcp/jdehgalffmffhfhmmhaokfbfnafnmgcl
  2. That's it — the extension auto-updates and needs no Developer mode.

Option B — load unpacked (no Chrome Web Store):

  1. Run npx @agent360/browser-mcp install to copy the extension files to ~/.browser-mcp/extension/. (Ignore its "Claude Code configured" line — Step 1 already handled registration, correctly.)
  2. Open chrome://extensions, toggle Developer mode ON (top right).
  3. Click Load unpacked and select ~/.browser-mcp/extension/.

You (the AI) cannot perform Step 2 — it requires the user to act in their browser. Ask the user to confirm they have completed it before proceeding.

Step 3 — verify

Ask the user to make sure Chrome is open, then call browser_list_tabs. A successful response (even with an empty tab list) means the server and extension are connected. If it errors with "extension not connected", the extension is not loaded or Chrome is not running — return to Step 2.

Notes