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 automation: navigate, click, fill, screenshot and evaluate in a headless browser.
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": {
"headlessstage": {
"command": "npx",
"args": [
"-y",
"@reneturcios/headlessstage",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add headlessstage -- npx -y @reneturcios/headlessstage mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"headlessstage": {
"command": "npx",
"args": [
"-y",
"@reneturcios/headlessstage",
"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": {
"headlessstage": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/headlessstage",
"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 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, 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.1.0) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker 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.
Browser automation through a headless browser page, as a CLI and a stdio MCP server in one bin. Navigate to a URL, click, hover, fill and select form elements, take named screenshots and evaluate JavaScript in the page.
The browser itself sits behind an injectable executor interface (BrowserExecutor in src/types.ts). This package bundles no browser and downloads none: with no executor configured, browser commands fail with a clear "Browser unavailable" error. Deployments inject a Puppeteer-compatible executor to drive a real browser. Launch options that weaken browser security (--no-sandbox, --disable-web-security, --allow-insecure-localhost) are rejected unless a call explicitly passes allowDangerous: true.
npx -y @reneturcios/headlessstage mcp
headlessstage mcp # stdio MCP server
headlessstage navigate headlessstage screenshot [selector] headlessstage click headlessstage fill headlessstage evaluate headlessstage --version
Exit codes: 0 success, 1 browser error, 2 usage error.
| Tool | Purpose |
|---|---|
puppeteer_navigate | Navigate to any URL in the browser |
puppeteer_screenshot | Capture screenshots of the entire page or specific elements |
puppeteer_click | Click elements on the page |
puppeteer_hover | Hover elements on the page |
puppeteer_fill | Fill out input fields |
puppeteer_select | Select an element with a SELECT tag |
puppeteer_evaluate | Execute JavaScript in the browser console |
MCP client config:
{
"mcpServers": { "headlessstage": { "command": "npx", "args": ["-y", "@reneturcios/headlessstage", "mcp"] } } }
docker run -i ghcr.io/cloudcorprecords/headlessstage # MCP server
docker run --rm ghcr.io/cloudcorprecords/headlessstage --version
npm install
npm run build npm test
MIT license.