Echo

Echo is a desktop browser that runs on your computer. It exposes an MCP server so Cursor, Claude Desktop, ChatGPT/Codex, Continue, Cline, Windsurf, VS Code, and other MCP clients can drive it with your existing subscription.

There is no model API and no cloud Chromium. The browser window you see is the one the assistant controls.

Quick start (for your friend)

1. Install Echo on your computer (Windows, Mac, or Linux — see below).

2. Leave Echo running. Closing the window hides it; it keeps running in the tray (Windows/Linux) or menu bar (Mac).

3. Open Settings (⋮ menu, top right) → Connections.

4. Click Connect for Cursor, Claude, or ChatGPT/Codex.

5. Fully quit and reopen that AI app so it picks up Echo.

6. Ask the assistant to search the web or open a page — it should use Echo’s tools (navigate, snapshot, search_web, etc.).

MCP URL on the same computer: http://127.0.0.1:18931/mcp
Server name: echo
A bearer token is shown in Settings → Connections (Echo creates it on first launch).

Related MCP server: agentify-desktop

Download

Installers: GitHub Releases

Pick the file for your OS:

If the Releases page is empty, the maintainer needs to publish a version tag (for example v1.0.0) so GitHub Actions builds the installers. Until then, use Run from source below.

Repo: https://github.com/krishngohel/local-browser

Install — Windows

1. Download the installer for your CPU from Releases:

   • Most PCs: Echo-Setup-*-x64.exe

   • ARM laptops (Surface Pro X, Snapdragon, Copilot+ PC): Echo-Setup-*-arm64.exe — do not use the x64 build on ARM.

2. Run the installer. Windows SmartScreen may warn because the build is unsigned:

   • Click More info → Run anyway.

3. Finish the wizard. Echo installs to %LOCALAPPDATA%\Programs\Echo\ and adds Desktop + Start Menu shortcuts.

4. Echo opens when setup finishes. Leave it running.

5. Closing the window does not quit Echo — it hides to the system tray (by the clock). Right-click the Echo icon there to Show or Quit.

Open Settings: click the ⋮ menu (top right) → Connections.

Uninstall: Windows Settings → Apps → Echo. Your browsing profile stays in %APPDATA%\Echo unless you delete that folder manually.

Install — Mac

1. Download Echo-1.0.0-mac-universal.dmg from Releases.

2. Open the .dmg. Drag Echo to Applications.

3. Eject the disk image. Do not keep using Echo from the mounted .dmg — it will stop working after eject. Echo warns you if you launch from the disk image.

4. Open Echo from Applications.

5. First launch — Gatekeeper: the app is unsigned (no Apple Developer ID yet). macOS blocks a normal double-click:

   • Right-click Echo → Open → Open.

   • On macOS Sequoia or later, if needed: System Settings → Privacy & Security → Open Anyway.

6. Leave Echo running. The red close button hides the window; Echo stays in the Dock and menu bar (top right).

   • Show again: click the Dock icon, menu-bar icon, or Echo → Show Echo.

   • Quit: Echo → Quit Echo, Cmd+Q, or menu-bar icon → Quit.

Open Settings: ⋮ menu → Connections.

If you use Claude Desktop: install Node.js (LTS) from nodejs.org. Claude launched from the Dock cannot see Homebrew’s PATH; Echo writes Node’s full path when you click Connect.

Profile folder: ~/Library/Application Support/Echo

Firewall (optional): if another device on your Wi-Fi cannot connect, allow Echo in System Settings → Network → Firewall.

Install — Linux

1. Download Echo-1.0.0-linux-x64.AppImage from Releases.

2. Make it executable and run it:

chmod +x Echo-1.0.0-linux-x64.AppImage
./Echo-1.0.0-linux-x64.AppImage

3. Leave Echo running (system tray). Open Settings → Connections from the ⋮ menu.

Profile folder: ~/.config/Echo (or the Electron userData path for the packaged app).

Firewall (optional): allow TCP port 18931 (or the port shown in Settings) if another device on your LAN needs to connect.

Connect your AI

Echo must be running before you connect. Open Settings (⋮) → Connections.

The green dot next to MCP server means Echo is listening. Copy the This computer URL if you need it manually: http://127.0.0.1:18931/mcp.

Cursor

1. In Echo: click Connect under Cursor.

2. Echo writes ~/.cursor/mcp.json (backs up any existing file to mcp.json.bak).

3. In Cursor: Settings → MCP — enable echo if it shows as disabled.

4. Start a new chat. The assistant should see Echo tools (navigate, snapshot, search_web, …).

Claude Desktop

Connect does not hot-plug. Echo writes a config file; Claude only reads it on startup.

1. In Echo: click Connect under Claude Desktop (Echo must be running).

2. Echo writes Claude’s config:

   • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

   • Windows: %APPDATA%\Claude\claude_desktop_config.json

   • Linux: ~/.config/Claude/claude_desktop_config.json

3. Fully quit Claude Desktop — this is the step most people miss:

   • Mac: Cmd+Q (closing the red button is not enough)

   • Windows: right-click Claude in the system tray → Exit

4. Keep Echo running (tray / menu bar).

5. Open Claude again.

6. In Claude: Settings → Developer → Local MCP servers — confirm echo is listed. A hammer icon in chat means MCP tools are active.

Packaged Echo (v1.0.1+) uses Echo itself as the bridge — Node.js is not required.

Do not use Claude’s “Add custom connector” — that is for public HTTPS servers only.

If it still fails, see Claude will not connect below.

ChatGPT / Codex desktop

1. In Echo: click Connect under ChatGPT / Codex.

2. Echo writes ~/.codex/config.toml (backs up to config.toml.bak).

3. Fully quit and reopen ChatGPT desktop or Codex.

Note: chatgpt.com in a normal browser cannot reach Echo on your computer unless you set up your own HTTPS tunnel.

Any other MCP client

On the same Settings page, copy one of:

• HTTP (this computer) — Cursor, Continue, Cline, Windsurf, VS Code, etc.

• stdio (this computer) — clients that only support command-based MCP.

• This network — if the AI client runs on another device on your Wi-Fi (uses your computer’s LAN IP; still needs the bearer token).

Paste the JSON/TOML into that client’s MCP config. Include the Authorization: Bearer … header exactly as shown.

Verify it works

1. Echo is running (tray / menu bar).

2. Settings → Connections shows MCP server as listening.

3. Your AI app was fully restarted after Connect.

4. Ask something like: “Search Google for Echo browser MCP and open the first result in Echo.”

The assistant should call tools such as search_web, navigate, and snapshot. If tools are missing, check that echo is enabled in the client’s MCP settings and reconnect.

Captcha / login / 2FA: complete it in the Echo window yourself. Tell the assistant to wait_for and then continue.

Day-to-day use

Open at login: Settings → System → Open at login (starts hidden in the background).

Downloads, screenshots, recordings: Settings → System → Open folder.

Token usage: Settings → Transfers — turn off page photos, watch frames, or the skill tree on connect if you want fewer tokens. Reconnect the AI client after changing tool groups.

Run from source (developers)

Requires Node.js 20+.

git clone https://github.com/krishngohel/local-browser.git
cd local-browser
npm install
npm run dev

This compiles the app and opens the Electron window. Playwright connects to the same Chromium over CDP (port 9333). You do not need a separate browser install.

Build an installer on your machine:

npm run dist

You cannot build a Mac .dmg from Windows — that requires a Mac or GitHub Actions on macos-latest.

On Windows, after npm run dist, npm run start-menu adds Echo to the Start Menu without rerunning the installer wizard.

Troubleshooting

“Echo is already running”

Only one Echo instance should run (MCP port conflict). Find Echo in the tray (Windows/Linux) or menu bar (Mac). Quit from there, then open Echo once.

Claude will not connect

Connect saves a file — it does not restart Claude for you.

1. Echo must be running when Claude starts (tray on Windows, menu bar on Mac).

2. Fully quit Claude, not just close the chat window:

   • Mac: Cmd+Q

   • Windows: tray icon → Exit

3. Reopen Claude. Check Settings → Developer → Local MCP servers for echo.

4. In Echo Settings → Connections, status should change from “Saved in Claude” to Connected now (green) once Claude’s bridge is live.

5. On v1.0.0, install Node.js and click Connect again. v1.0.1+ does not need Node — update from Releases.

6. Claude logs (if needed): Mac ~/Library/Logs/Claude/, Windows %APPDATA%\Claude\logs\.

Cursor / Claude does not see Echo (general)

• Echo must be running before the AI app starts (or restart the AI app after Echo is up).

• Click Connect again in Settings → Connections.

• Fully quit Cursor or Claude (not just close the chat window), then reopen.

• Cursor: Settings → MCP → enable echo.

• Claude: use Local MCP servers, not “Add custom connector”.

Claude says Node.js is missing

Install Node from https://nodejs.org, then click Connect again in Echo so it writes the correct path.

Mac: “Echo cannot be opened” / “damaged”

Right-click → Open, or System Settings → Privacy & Security → Open Anyway. This is normal for unsigned apps.

Mac: opened from the disk image

Drag Echo to Applications, eject the .dmg, open from Applications.

SmartScreen / Gatekeeper warnings

Installers are unsigned until an code-signing certificate is added. Use the steps above — the app is built from this repo’s GitHub Actions.

Google shows captcha or consent

Complete it in the Echo window. Ask the assistant to wait (wait_for) and retry.

Another device on Wi-Fi cannot connect

Use the This network URL and token from Settings. Allow Echo through the host computer’s firewall on private networks. Do not share the token publicly.

MCP port in use

Echo prefers port 18931 and tries 18931–18940. Port 8931 is avoided (Playwright MCP default). Check Settings for the actual URL.

Windows ARM laptop (Surface, Snapdragon)

Use Echo-Setup-*-arm64.exe, not the x64 installer. The x64 build may fail to install, crash, or behave oddly under emulation. Releases from v1.0.2 include a native ARM64 Windows build. Settings → System → About → System type should say ARM64-based PC.

What Echo gives an assistant

On connect, Echo sends a skill tree (how to browse, search, screenshot, record, etc.) unless you turn that off in Settings → Transfers.

Browse: tabs_list, tabs_new, tabs_close, tabs_select, navigate, back, reload, snapshot, screenshot, watch, click, type, fill, press, scroll, select, wait_for

Search / extract: search_web, extract_readable

Debug: console_errors, network_failures

Test: viewport_set, test_start, test_assert_text, test_assert_url, test_end

Record / replay: record_start, record_stop, recordings_list, recording_play, recording_delete

Always snapshot before click / type / fill. Refs look like e0, e1.

Full guide: skills/ECHO-SKILL-TREE.md

Security (read this)

• Anything you log into in Echo is visible to a connected assistant while MCP is connected.

• MCP listens on this computer and your LAN (0.0.0.0:18931, or the next free port). Same-machine clients should use 127.0.0.1.

• A bearer token protects the MCP server. Echo writes it into Cursor/Claude config when you Connect. Do not post the token online.

• Echo uses a separate profile from your daily Chrome — not your normal browser cookies.

• Downloads: app data folder → downloads/. Recordings: recordings/.

Legal

• Privacy Policy

• Terms of Service

• MIT License

Also in the app: Settings → About, Privacy, Terms.

Build / release (maintainers)

GitHub Actions (.github/workflows/release.yml) builds Windows, Mac, and Linux installers on v* tags (for example git tag v1.0.0 && git push origin v1.0.0). Manual Run workflow uploads artifacts to the Actions run but does not create a Release page.

Mac and Windows builds are unsigned unless signing secrets are configured.