π On the
mainbranch? You're viewing the bleeding-edge dev docs! For other versions, check out therelease/*branches.
An MCP Server that enables AI assistants to interact with your local browsers.
2025-04-04.20-53-26.mp4
-
Add MCP Browser Kit to your MCP Client:
{ "mcpServers": { "browser-kit": { "command": "npx", "args": ["@mcp-browser-kit/server@latest"] } } } -
Choose the right extension build for your browser:
- Check the Compatibility table below to see which build (M2 or M3) is compatible with your browser
- Note that M2 builds offer more functionality than M3 builds, so prefer M2 if your browser supports both
-
Download and unzip the latest compatible build from The Latest Release.
-
Load the extension into a compatible browser and enable it.
-
Refresh open tabs to ensure extension scripts are loaded.
-
Start messaging on your MCP Client:
Use browser-kit, star the last open GitHub repo on my browser -
Optional, check User Notes for more information.
The M2 build supports more functionalities than the M3 build.
Extension file name patterns:
- M2 build:
mcp_browser_kit_m2-[version].zip(e.g.,mcp_browser_kit_m2-5.0.0.zip)- M3 build:
mcp_browser_kit_m3-[version].zip(e.g.,mcp_browser_kit_m3-5.0.0.zip)
| Browser | M2 build | M3 build |
|---|---|---|
| Chrome | β | β |
| Brave | β | β |
| Edge | β | β |
| Firefox | β | β |
| Safari | β | β |
- Chromium-based browsers (Chrome, Brave, Edge)
- Open chrome://extensions/
- Enable
Developer mode - Click
Load unpacked - Select the unpacked extension folder
- Firefox
- Open about:debugging#/runtime/this-firefox
- Click
Load Temporary Add-on - Select the
manifest.jsonfile in the unpacked extension folder
- Safari
- Open
Develop > Show Extension Builder - Click
+and selectAdd Extension - Select the unpacked extension folder
- Click
Installto install the extension
- Open
Note for Alpha stage: Consider using a separate browser profile or dedicated browser instance with this MCP to prevent sensitive data from being unintentionally exposed to AI model providers.
Security: BrowserKit currently lacks authentication for incoming requests. Keep ports 59089 and 2769-2799 on your device network only.