Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
Agentic browser harness: your agent CLI in your real, signed-in browser, from a side panel or MCP.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"browsentic": {
"command": "npx",
"args": [
"-y",
"browsentic",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add browsentic -- npx -y browsentic mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"browsentic": {
"command": "npx",
"args": [
"-y",
"browsentic",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"browsentic": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"browsentic",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account imshaikot, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.9.0) reached the registry 19 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
MCP server for browser use access
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
This is Browsentic Bridge, the half of Browsentic that runs on your computer.
Browsentic is your browser's superpower: an agentic browser harness that runs the agent CLI you already use from a side panel in your real, logged-in browser. The side panel opens beside whatever tab you are on; the Bridge runs on loopback and starts your agent CLI when you give it work. It is free and open source, with no hosted relay, no API key, no account and no headless browser: the agent works in the tabs you are already signed in to.
One command sets everything up, the extension included:
npx browsentic@latest setup
It starts Browsentic Bridge, asks which browser you use, opens the extension's store page there and waits for the browser to connect. Press Add to Chrome (Add in Firefox; Edge first asks you to allow extensions from other stores), and the extension connects by itself; if it asks for a code, enter the one setup prints. On macOS and Windows an app does the same from a window: see browsentic.com/install.
The extension is on the Chrome Web Store for Chrome, Brave, Arc, Vivaldi and Opera, on Edge Add-ons for Edge, and Firefox gets an add-on signed by Mozilla. The side panel runs on an agent CLI you are signed in to: Claude Code, Codex, or another supported one.
Then open the side panel and type or speak an instruction.
To update later:
npx browsentic@latest update
The extension updates itself from its store, and the two do not have to be the same version.
PATH, logged in: claude, codex, agy, vibe, grok, cursor-agent, qwen, opencode or dshbrowsentic setup | start the Bridge, add the extension to a browser and pair it |
browsentic update | update the Bridge and restart it |
browsentic browsers | the browsers on this computer and where each gets the extension |
browsentic pair | issue a fresh single-use code |
browsentic status | the Bridge, each paired browser and the agent |
browsentic sessions | list paired browsers |
browsentic revoke | unpair one browser, or all of them |
browsentic agent | choose which agent runs the side panel |
browsentic logs | tail the Bridge's log |
browsentic mcp | serve MCP over stdio |
browsentic help lists the rest. A browser that cannot reach a store can load the extension from a folder this package carries: browsentic setup --unpacked.
Optional, and the side panel needs none of it. Registering Browsentic with an MCP client lets that client drive the same browser from a terminal.
npm i -g browsentic
claude mcp add browsentic -- browsentic mcp
Any MCP client works: Claude Code, Codex, Cursor, Zed, Claude Desktop. One Bridge owns the browser link, so several can share the same paired browser at once.
Prefer a global install over npx here. An npx command re-resolves on every client start and can quietly start a different Bridge than the one you set up.
Full documentation lives at [browsentic.com/docs](https://browsentic.com/docs/), including the security model, the tool reference and the architecture.
Source: github.com/imshaikot/browsentic · Apache 2.0