Chrome Control MCPBrowser companion
Companion 0.1.9 for Apple Silicon 0.1.8 for manual and other previews

Your browser.
Your AI.
Working together.

Give your MCP client a direct connection to Chrome. Read pages, interact with tabs, and inspect what’s happening, through a companion running on your computer.

Get the companion Read the setup guide

Companion 0.1.8 is separate from the extension. Extension 0.1.8 Store approval and availability are not yet verified. Protocol 1 is unchanged.

Page & tab access Browser interaction Screenshots Network & console Local stdio MCP

The companion

Choose your way in.

Mac users can choose the signed, notarized self-contained installer. The manual ZIP remains available for an existing Node.js setup.

New in 0.1.8: optional remembered-browser pairing and a public companion build that requires no private update account. Public companion upgrades are manual for the 0.1.8 downloads; the 0.1.9 Apple Silicon public-managed installer updates automatically from the signed public feed. Chrome Web Store extension updates are separate and depend on Store approval and Chrome delivery. Protocol 1 is unchanged.

Release status

Mac revision 9 is Developer ID signed and Apple-notarized. Apple Silicon installation is verified; native Intel and Windows testing remains in progress. These downloads use manual upgrades. Apple Silicon Macs can instead choose the 0.1.9 public-managed installer: signed, notarized, installed manually once and then updated automatically from the signed public feed. View release details.

Manual companion ZIP EXPERIMENTAL · MANUAL SETUP

Companion 0.1.8 · 382,165 bytes · Node.js required · locked dependencies included

Use the manual ZIP instructions
Download manual ZIP
Mac installers and Windows preview

The Mac packages are signed and notarized. Use an existing runtime or the self-contained package: the full missing-runtime download has not passed end-to-end testing.

Native setup

Companion 0.1.9 Apple Silicon · 0.1.8 manual and other previews

Windows x64 · Windows 10 / Server 2016+

Self-contained

PREVIEW

The companion and its runtime in one download. No separate Node.js installation.

  • Includes private Node.js 24.21.0
  • No setup-time runtime download
Unavailable on this Site
Windows x64 · EXE22.64 MiB

Full installers are temporarily unavailable while download hosting is verified. The manual companion download is available.

Windows native8 installer, payload hashes and MCP runtime smoke passed on a native x64 machine. Real Chrome pairing and a signed Windows build remain open.

SHA-256 & exact file details

chrome-control-mcp-companion-0.1.8-native.8-windows-x64-full.exe

23,742,144 bytes

21c9ccf58a6b7502825a9a8b98805b28c2401e47896794c901eadc53e80312a9

Lightweight

PREVIEW

A smaller setup that uses your supported Node.js runtime, or asks before downloading one.

  • Reuses matching Node 22/24 LTS
  • Separate consent for missing runtime download
Download Windows .exe
Windows x64 · EXE0.22 MiB

Windows native8 installer, payload hashes and MCP runtime smoke passed on a native x64 machine. Real Chrome pairing and a signed Windows build remain open.

SHA-256 & exact file details

chrome-control-mcp-companion-0.1.8-native.8-windows-x64-light.exe

235,802 bytes

afbc27ddb55f36f4d28324ee4f0d27343fa0c749ea2b9d61d49c564234815f23
Mac: Apple Silicon Macs (macOS 13.5 or later) can use the signed, notarized 0.1.9 public-managed installer: the first install is manual, and it then updates automatically from the signed public feed; its isolated prepared-layout acceptance (staged health check, live update transition, MCP smoke, freshness and offline rollback) has passed, while a full Installer-based installation of this package has not been exercised. The 0.1.8 native.9 PKGs and lightweight setup apps remain signed and notarized with manual upgrades, and Apple Silicon per-user installation, installed MCP initialization and the downloaded setup app’s Gatekeeper launch have passed for that revision. Still being tested: native Intel execution, older macOS versions and the complete missing-runtime download flow. Windows native8 installer, payload hashes and MCP runtime smoke passed on a native x64 machine; real Chrome pairing and a signed Windows build remain open, and Windows full downloads remain unavailable. Read release notes.
Verify the manual ZIP · SHA-256d9cc9cf88fcd3f9f5db4a24c34a55742788cd2f9d4f385129326c306ad89387f
Checksums for available program downloads
All native downloads

Apple Silicon 0.1.9 public-managed: signed and notarized, updates automatically from the signed public feed; SHA256SUMS-native.12. 0.1.8 Mac revision 9: signed and notarized, manual upgrades. Windows revision 8: unsigned preview.

Native setup

From download
to connection.

Choose the matching platform and architecture, then review the release details.

Prefer manual setup? →

Check your download

Choose Windows x64, macOS Apple Silicon, or macOS Intel. Compare the file’s SHA-256 with the checksum shown above. The 0.1.9 Apple Silicon public-managed PKG and the 0.1.8 revision 9 Mac packages are Developer ID signed and notarized. Windows preview packages remain unsigned.

Do not disable operating-system security to run a blocked download.

Open the matching setup

Windows, either package: Open the .exe, review the destination, then choose Install. It is configured for per-user setup; the native8 installer and packaged runtime smoke passed on a native x64 machine, while real Chrome pairing remains open.

Apple Silicon Mac (macOS 13.5 or later), self-contained 0.1.9: Open the 0.1.9 .pkg in Apple’s Installer. It is configured for the current user’s home folder and is signed and notarized. After this manual first install, the Apple Silicon public-managed flavor checks the signed public feed and applies reviewed updates; no account or credential is involved. Isolated prepared-layout acceptance has passed; a full Installer-based installation of this package has not been exercised.

Apple Silicon Mac, retained 0.1.8 option: The revision 9 self-contained PKG and lightweight setup remain available with manual upgrades.

Intel Mac, self-contained: The full build is a PKG with an included runtime. Native Intel execution and installation are untested. Use the matching lightweight download if the full build is unavailable here.

macOS lightweight: Extract the ZIP, then open Chrome Control MCP Setup.app. Review its native dialogs before choosing Install.

Lightweight setup checks for a matching, supported Node 22/24 LTS runtime. If missing, it asks separately before downloading a private runtime. Declining cancels. Windows runtime downloading also needs its built-in certutil.exe and tar.exe tools.

Add the client configuration

Mac, self-contained: Open Configuration.app in the installed folder to view or copy the example.

Windows and macOS lightweight: Open mcp-config.example.json in the installed folder. Merge its entry with your client’s existing configuration, following that client’s instructions. Setup does not edit your client settings.

Where are the installed files?

Apple Silicon Mac self-contained
~/Library/Application Support/Chrome Control MCP/native.12-public-managed-macos-arm64-full

Intel Mac self-contained
~/Library/Application Support/Chrome Control MCP/native.9-macos-x64-full

macOS lightweight
~/Library/Application Support/Chrome Control MCP/chrome-control-mcp-companion-0.1.8-native.9-macos-<arm64-or-x64>-light

Windows default
%LOCALAPPDATA%\Chrome Control MCP\native.8-windows-x64-<full-or-light>
Use the folder selected during setup if you changed it.

Start or restart your MCP client after saving. Installation alone does not start the broker or pair your browser.

Pair, then try a test page

Enable a compatible Chrome Control MCP extension in your chosen browser profile. Open the broker’s local session.json from .chrome-control-mcp in your home folder, then open its pairUrl in that browser profile.

Call browser_status and check that extensionConnected is true. Select a non-sensitive test tab before trying a snapshot or screenshot. See connection checks.

Keep the pairing URL and token private. Do not share them or paste them into an AI prompt. Pair again with the new URL after a broker restart.

Manual ZIP setup

Bring your own
Node runtime.

Set up the current manual companion release on Windows or macOS. Start with a fresh browser profile and a non-sensitive test page.

Need a hand?

Install the companion

Install a supported Node.js LTS release (Node 22 or 24 is used by the preview installers). Extract the ZIP to a permanent folder you control. Its locked dependencies are included, so no npm install is needed. Use the extracted bin/mcp.js path in the next step.

Keep the folder in place. No global npm install is needed.

Connect your MCP client

Add a local stdio MCP server. Use node as the command and the full path to bin/mcp.js as its argument. For clients with an mcpServers configuration, merge this entry with your existing servers.

MCP CONFIGURATION · REPLACE THE EXAMPLE PATH 
{
  "mcpServers": {
    "chrome-control": {
      "command": "node",
      "args": ["C:\\Tools\\chrome-control-mcp-companion-0.1.8\\bin\\mcp.js"]
    }
  }
}

Follow your client’s instructions for where to save its config, then restart it. If it cannot find Node.js, use the full path to the Node.js executable.

The first client starts the broker automatically. Other clients share it. Use bin/mcp.js as the entry point, rather than bin/broker.js.

Pair your Chrome extension

Use a compatible Chrome Control MCP extension in the browser profile you want to control. Open session.json inside the .chrome-control-mcp folder in your operating-system home directory.

Open its pairUrl in that same browser profile. If automatic pairing fails, enter the current port and token in the extension popup.

Keep the pairing token private. Never share the URL or session file, send it to support, or paste it into an AI prompt. Pair again with the new URL whenever the broker restarts.

Check that you’re connected

The extension icon turns red once it authenticates to the companion and returns to normal when disconnected. Open the popup to see connected MCP clients by their reported names. These names are labels, not verified identities; a red icon does not mean a tool action is running.

Call browser_status in your MCP client and check that extensionConnected is true. Then call browser_list_tabs and use browser_select_tab to select a non-sensitive test page.

Try a page snapshot and screenshot. Chrome may display a debugging indicator; visibility depends on Chrome and its configuration. Disable or remove the extension to stop its browser access. If a debugger conflict occurs, close DevTools on that tab. Some protected browser pages remain inaccessible.

Know what you’re connecting

Local connection.
Powerful access.

The companion runs on your computer, but your data’s journey may continue. Tool results can contain full cookies, authentication tokens, page content, screenshots, web storage, and network response bodies.

Your MCP or AI client may send that data to its provider. Choose a client and browser profile you trust.

Read the full privacy policy
Your Chrome profilePages, interactions, and debugging data
↓ Loopback connection · 127.0.0.1
Companion + MCP clientRunning on your computer
↓ Depending on your client’s configuration
Your AI provider or other serviceMay receive and retain tool results
All capabilities are enabled by default, with no default website restrictions. Optional origin rules check tool calls; they do not provide complete browser or network isolation. Configure only the access you need.

Good to know

A few useful details.

Answers before you connect.

How do upgrades and remembered pairing work?

Public companion builds do not check an automatic update feed. Install a newer reviewed companion manually, retain your existing configuration and pairing records, then update your MCP client entry to the new installation. Chrome Web Store updates apply only to the extension; an uploaded package is not an approved release.

Remembered pairing is optional and off by default. On supported macOS setups, enable the companion option and complete both matching-code approval screens. Never approve a request you did not initiate. Approval persists until revoked or forgotten. Windows native remembered enrollment is not supported in this release. Ordinary per-run pairing remains available.

Is this the Chrome extension?

No. This is its companion, which runs on your computer. You also need a compatible Chrome Control MCP extension in that browser profile. Extension 0.1.8 Store approval and availability are not yet verified. Updating the extension alone does not update the companion.

Which download should I choose?

The 0.1.8 manual companion ZIP includes its locked dependencies and uses a supported Node.js LTS runtime you provide. Apple Silicon Macs can use the 0.1.9 public-managed self-contained PKG with automatic feed updates, or the retained 0.1.8 revision 9 PKG and lightweight setup with manual upgrades. Windows x64 and Intel Mac options are unchanged. Mac requires macOS 13.5 or later. The primary Apple Silicon download is the 0.1.9 public-managed PKG (native.12); the retained Mac downloads are revision 9 and the Windows previews are revision 8. Both full Mac builds use a PKG. Self-contained includes its runtime. Lightweight checks your existing Node 22/24 LTS runtime and asks before downloading a private one if needed.

Mac packages are signed and notarized, with Apple Silicon per-user installation and MCP initialization verified. Intel-native execution remains unverified. Windows native8 full and light installers, payload hashes and MCP runtime smoke passed on a native x64 machine; real Chrome pairing and a signed Windows build remain open. The 0.1.9 Apple Silicon public-managed installer has passed isolated prepared-layout acceptance: staged health, a live HTTPS update transition, MCP smoke of the selected release, freshness and offline rollback. A full Installer-based install of that package and native Intel execution remain untested; Intel keeps its signed and notarized manual revision 9, and Windows keeps its unsigned preview. Only the public-managed Apple Silicon flavor updates from the signed public feed. Lightweight runtime-download acceptance and older macOS testing remain open.

Can I reinstall or remove a native preview?

Stop the companion before reinstalling or removing its files. macOS PKGs reinstall their package-managed files; macOS may retain a receipt. The macOS lightweight apps and Windows installers refuse to overwrite an existing destination.

To remove an installation, stop the companion and delete its exact installation folder. Runtime state in .chrome-control-mcp is separate; delete it only if you intend to remove that state too. See the release notes and privacy policy for details.

How do I restrict browser access?

Copy the included config/broker.config.example.json to .chrome-control-mcp/config.json in your home folder. Remove capabilities you do not need and configure origin rules before restarting and pairing the broker again. The included README explains each setting.

Origin rules do not filter the list of open tabs or fully isolate network activity. With origin rules configured, cookie read and clear requests require a permitted URL.

How do I disconnect and remove local data?

Disable or remove the extension to stop its browser access. Stopping the broker interrupts client tool traffic but does not detach an already attached debugger or erase extension buffers. Dismissing the debugger banner does not disable tools that do not use the debugger.

Stop the broker before deleting its local files. Data already passed to a client or other service follows that service’s retention and deletion practices. See the privacy policy for details.

Where can I get help?

The manual ZIP includes a README. Read the privacy policy linked on this site before connecting. You can also email [email protected]. Describe the issue without sharing pairing tokens, passwords, cookies, session files, or private browser data.

Optional support

Support development.

Voluntary support for software upkeep and future features.

Contributing does not change your access or features. Choose an option only if you’d like to support the project.

Monthly support via Stripe

A$5/ monthContinue to Stripe A$10/ monthContinue to Stripe A$20/ monthContinue to Stripe

Recurring monthly until canceled. Prices shown in Australian dollars.

One-off support

Choose your own amount.

Stripe · choose AUD amount PayPal · choose amount

Payments are handled by Stripe or PayPal. Stripe may initially show your local currency; select AUD for the Australian-dollar amount. Review the amount, currency, and any tax or fees at checkout. Links open in a new tab.

PayPal payments are received by Leo Software. The PayPal option is one-off; you choose the amount.