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)
Give any AI agent your real Chrome: text perception, visible cursor, ~4x fewer tokens.
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": {
"agentic-browser": {
"command": "npx",
"args": [
"-y",
"agentic-browser-mcp"
]
}
}
}Run this in your terminal
claude mcp add agentic-browser -- npx -y agentic-browser-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agentic-browser": {
"command": "npx",
"args": [
"-y",
"agentic-browser-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": {
"agentic-browser": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentic-browser-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 davarion-tech, 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 (1.4.0) reached the registry 10 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.
Give any AI agent a real browser and watch everything it does.
Built and maintained by [Davarion](https://www.davarion.com).
No API key. No extra bill. agentic-browser is a tool, not a model: it runs on your computer and uses whatever brain your agent already has. That can be your Claude Pro/Max plan in Claude Code, your ChatGPT plan in Codex, Cursor, or a local model. Nothing to sign up for and no per-token charges from us.
Humans browse the web with browsers. Agents usually need APIs. agentic-browser lets any agent use your installed Google Chrome the way a person does. It perceives pages as compact text with pixel coordinates instead of screenshots, and a visible cursor shows every move and click.
Español · Use cases · Chat watcher · Architecture · Security · Disclaimer
▶ Watch the 15-second demo · ▶ Watch the full video (1 min)
Real runs recorded by the agent itself: compare prices · research the web · fill a form and stop before submitting.
| Problem with today's browser agents | agentic-browser |
|---|---|
| Screenshots cost ~1,000–1,500 tokens per look | Text snapshot: ~15 tokens per element. diff: true returns only what changed |
| Agents guess coordinates from images | Every element comes with its exact center @x,y. browser_element_at(x, y) tells what is at any pixel, with no image |
| You can't see what the agent is doing | A red cursor travels to each target, ripples on click and labels the action |
| Locked into one agent framework | MCP server and a plain HTTP/JSON API: Claude, GPT, Gemini, Hermes, OpenClaw, LangChain, n8n, curl… |
| Stripped-down Chromium builds | Your real Chrome: extensions, codecs, PDF, WebGPU, auto-updates |
| Yet another API key and bill | None. Works with the subscription your agent already uses; even the optional chat watcher can run on your Claude plan |
One line (Claude Code):
claude mcp add agentic-browser -- npx -y agentic-browser-mcp
Any other MCP client: use "command": "npx", "args": ["-y", "agentic-browser-mcp"]. Requirements: Node ≥ 18 and Chrome (or Edge).
Requirements: Node ≥ 18 and Google Chrome.
git clone https://github.com/davarion-tech/agentic-browser.git
cd agentic-browser && npm install
npm run doctor
npm test
Claude Code:
claude mcp add agentic-browser -- node /absolute/path/to/agentic-browser/src/mcp.js
Claude Desktop, Cursor, Codex, Hermes, OpenClaw or any MCP client: see examples/mcp-config.json.
Claude Code slash command (optional): copy skills/agentic-browser into ~/.claude/skills/. Then /agentic-browser always uses this browser instead of any other built-in browser tool.
Then ask your agent something like:
Use only the browser_* tools from agentic-browser. Open es.wikipedia.org, search for "Chrome DevTools Protocol", open the first result and summarize the first paragraph. Don't take screenshots.
npm run http
curl -s -X POST http://127.0.0.1:8787/tools/browser_navigate -d "{\"url\":\"example.com\",\"snapshot\":true}"
GET /tools returns the JSON Schema of every tool, ready to pass as function definitions to any LLM API. A dependency-free Python client is in examples/python_client.py.
Off by default. Installing agentic-browser only lets your agent use the browser when you ask it to. The watcher is a separate process that you turn on.
The watcher keeps the agent's own messaging tabs open (WhatsApp Web, Telegram, Messenger…). Waiting costs zero tokens; when a message arrives, it wakes Claude to read it and propose a reply. A code-enforced policy controls what happens next:
npm run setup
npm run watcher
It runs on your Claude subscription (claude setup-token) or an API key. Read docs/WATCHER.md and the Disclaimer first: many platforms forbid unofficial bots.
# Test bench
url: http://localhost:3000/ viewport 1280x800 scroll=0,0 docH=2090 [3] textbox "Search" ph="type something" @191,124 [4] button "Search" @339,124 [5] select "color" value="Red" opts=[*Red|Green|Blue] @429,124 [6] checkbox "I agree" {checked} @492,124 [10] button "Button in shadow DOM" @652,316 [f1:1] button "Button inside iframe" @214,217
file saves it as .md.images/, videos/, audio/, docs/ with a manifest.json (source URL, alt text, size, hash). Duplicates and tracking pixels are skipped.Files go to ~/.agentic-browser/exports (AGENT_EXPORTS); AGENT_MEDIA_MAX_MB (500) caps each file.
The chat watcher on a demo chat: it drafts a reply for you to send, and hands bank-detail requests and phishing links to you. Full video.
browser_cursor_style({ privacy: "whatsapp" }) or AGENT_PRIVACY=whatsapp blurs contacts, chat headers and profile photos so you can record or share the agent's screen without exposing anyone. Presets: whatsapp, telegram, gmail, or your own CSS selectors. The agent still reads everything.contacts: ["Cliente demo"] keeps every other chat out: they never wake the model, and before typing the watcher reads the open chat's title from the page, so the agent can't write anywhere else. Safe on an account that also has personal chats.record: true saves each event as its own video.browser_teach_start records a task while *you* do it in the agent's Chrome (clicks, text, selects, Enter). It is saved as a recipe of roles and names, not pixels, so it survives layout changes. browser_replay repeats it with new values ({"search": "October invoices"}) without perceiving every step. Passwords are never recorded: on replay, the person types them.AGENT_TEACH_BUTTON=0.browser_dismiss does it on demand; AGENT_AUTO_DISMISS=0 turns the automatic pass off.browser_extract turns the most relevant table or repeated list (products, search results, contacts) into JSON or CSV rows with title, link, price and image. Merged table headers are resolved. CSV output is safe to open in Excel.browser_cursor_style({ hud: true }) (or AGENT_HUD=1) shows, in the corner of the page, the tokens used against what screenshots would have cost. browser_stats returns the same numbers. Formula: tokens ≈ characters / 4; one screenshot ≈ width × height / 750 per perception call.| Tool | Purpose |
|---|---|
browser_snapshot | Main perception. Visible elements with ref, role, name, state and center @x,y. diff: true returns only changes |
browser_find | Find elements by text anywhere on the page, including off-screen |
browser_element_at | Pixel → element (role, text, clickable, DOM path), with no image |
browser_cursor | Where the agent's cursor is and what is under it |
browser_click / browser_move | Visible click or hover by ref or x,y (buttons, double click, modifiers) |
browser_type / browser_press | Real keyboard input: clear, submit, shortcuts like Control+L |
browser_scroll / browser_drag | Mouse wheel; drag and drop |
browser_select / browser_upload | options; file inputs |
browser_navigate / browser_history / browser_tabs | Navigation and tabs |
browser_read / browser_eval | Readable text (wrapped as untrusted content); arbitrary JS (only with AGENT_ALLOW_EVAL=1) |
browser_extract | Table or repeated list → JSON or CSV rows (title, url, price, image…). file saves it to disk |
browser_article | Reader mode: the page's main content as clean Markdown, to read or summarize cheaply. file saves a .md |
browser_pdf | Save the page as PDF or MHTML, with the agent's session |
browser_media | Download every image, video, audio file and document, organized in folders with a manifest.json. download:false only lists |
browser_video | Download the page's video: direct files or HLS/DASH via ffmpeg. Refuses DRM. list:true shows candidates |
browser_teach_start / browser_teach_stop | Record a task the person performs once, as a reusable recipe |
browser_recipes / browser_replay | List or show recipes; replay one with new params at almost zero tokens |
browser_stats | Tokens used this session vs. the screenshot equivalent |
browser_dismiss | Close popups covering the page (close or reject only, never accept). Runs automatically after browser_navigate |
| browser_batch | Several actions in one cal
Only the beginning is shown; read the rest in the repo