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)
Browser DevTools for agents in your signed-in Chrome: cross-tab watching, route sweeps, bug reports.
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": {
"fileforge": {
"command": "npx",
"args": [
"-y",
"fileforge-mcp-server"
]
}
}
}Run this in your terminal
claude mcp add fileforge -- npx -y fileforge-mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"fileforge": {
"command": "npx",
"args": [
"-y",
"fileforge-mcp-server"
]
}
}
}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": {
"fileforge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"fileforge-mcp-server"
]
}
}
}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 6, 2026
The registry name was verified with the GitHub account mayank1307, 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.2.2) reached the registry yesterday.
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.
The MCP server for FileForge. Your agent watches your signed-in Chrome across tabs, sweeps your routes, and hands you the bug report. This package also contains the FileForge Chrome extension, which you load unpacked from the package folder.
You need Node.js 20 or newer and Google Chrome.
npm install -g fileforge-mcp-server
Install it globally, not with npx: Chrome loads the extension from the package folder, so the folder must stay put.
fileforge-setup
This prints the extension folder and the exact command or config for each MCP client, using your real paths. It changes nothing unless you pass --write.
Open chrome://extensions, turn on Developer mode, click Load unpacked and pick the folder it printed. The card should show ID nlcebipkdgecilmgfpobamljieanadpn.
Then connect your client. For Claude Code or Codex, run the command it printed. For Cursor or Claude Desktop, let it edit the config file; it keeps your other servers and saves the old file as .bak:
fileforge-setup --client cursor --write
Every client is covered in the setup guide.
With your MCP client open and Chrome running:
fileforge-verify
Then ask your agent to call fileforge_runtime_action with action: "status".
Optional: with FILEFORGE_REQUIRE_PAIRING=1 in the server's environment, the extension must present the bridge token. fileforge-pair prints it, and you paste it into the side panel's Settings tab. See the setup guide.
npm install -g fileforge-mcp-server@latest
Then click the reload icon on the FileForge card at chrome://extensions and restart your MCP client. fileforge-verify warns when Chrome is still running the old extension code.
MIT license.