Browser Use
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Beschreibung vom Entwickler (englisches Original)
Any website as MCP tools: a real Chrome signed in as you, and shortcuts the agent saves as tools.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
ANYSITE_HEADLESS, ANYSITE_CHROMEDu brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"anysite": {
"command": "npx",
"args": [
"-y",
"anysite-mcp"
],
"env": {
"ANYSITE_HEADLESS": "your-value",
"ANYSITE_CHROME": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add anysite --env ANYSITE_HEADLESS=your-value --env ANYSITE_CHROME=your-value -- npx -y anysite-mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"anysite": {
"command": "npx",
"args": [
"-y",
"anysite-mcp"
],
"env": {
"ANYSITE_HEADLESS": "your-value",
"ANYSITE_CHROME": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"anysite": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"anysite-mcp"
],
"env": {
"ANYSITE_HEADLESS": "your-value",
"ANYSITE_CHROME": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
ANYSITE_HEADLESS envANYSITE_CHROME envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 10. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto DwytMCL bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.6.0) kam heute in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Browser Use, Chrome DevTools MCP, MCP Server Browser
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
A real Chrome, signed in as you, on your own computer.
claude mcp add anysite -- npx -y anysite-mcp
No API keys. No cloud browser. No extra LLM. Your logins never leave your machine.
Quick start · Why it's different · Tools · Shortcuts · Shortcut Library · Packs · Safety · FAQ
anysite-mcp is an MCP server that drives a real Chrome on your computer. Every site gets its own browser profile that you sign in to once, by hand. The agent then works the site the way a screen reader does, by role and name, so small redesigns don't break it.
When the agent gets a job done, it can save the steps as a shortcut, and that shortcut becomes a new tool it can call in one step next time.
Your accounts, kept apart
One Chrome profile per site, signed in by hand once. Google sign-in works.
Gets faster with use
A job the agent has figured out becomes a one-call tool that's there next session. Shortcuts are tested before they're saved and fail loudly if a page stops looking right.
Repairs itself
When a site renames a button or swaps it for a link, the shortcut finds the new one and updates itself. No extra LLM needed.
Learns by watching
Run anysite-mcp record github.com my_job, do the job by hand, and it's a tool.
You set the limits
Per site: read-only, ask before sending, buying or deleting, and which domains it may open.
Light on tokens
After each action the agent sees only what changed, and points at elements by ref. web_extract turns lists and tables into JSON.
A shared, health-checked library
Community shortcuts are tested against the live sites every week, and you can search them from the terminal.
Packs for popular sites
Gemini and NotebookLM are included. A new pack is one file.
You: Ask Gemini to summarise this PDF, then add the summary as a source to my "Thesis" notebook in NotebookLM.
Claude: gemini_ask { prompt: "Summarise this PDF in 10 bullet points", files: ["~/Downloads/paper.pdf"] } → - The study compares … (Chat: https://gemini.google.com/app/…) notebooklm_add_source { notebook: "Thesis", text: "- The study compares …" } → Added pasted text.
You: Check my GitHub notifications.
Claude: web_open { site: "github.com", url: "/notifications" } → This looks like a sign-in page. Call web_login for "github.com" … web_login { site: "github.com" } "A Chrome window opened on GitHub. Sign in there, then quit that window and tell me." You: done Claude: web_open { site: "github.com", url: "/notifications" } → (accessibility tree of your inbox) web_save_shortcut { site: "github.com", name: "notifications", description: "List unread GitHub notifications", steps: [{ "action": "open", "url": "/notifications" }, { "action": "read", "role": "main" }] } → Saved github_com_notifications.
(Next week, in a new session) You: Anything new on GitHub? Claude: github_com_notifications {} → 3 unread: …
Most browser tools make the agent rediscover a site every session. anysite-mcp keeps what it learned.
| anysite-mcp | Playwright MCP | browser-use / Stagehand | |
|---|---|---|---|
| Signed in as you | Yes, a separate profile per site, signed in by hand once | One browser for everything (its extension can use your Chrome) | Usually cloud or fresh browsers |
| Google sign-in (Gemini, NotebookLM, Gmail) | Works: sign-in happens in a plain, non-automated window | Often refused as an "insecure browser" | Often refused |
| Gets faster with use | The agent saves working steps as new tools | No | Some cache actions |
| Survives redesigns | Saved steps repair themselves | No | With an LLM call |
| Learn by watching you | `record` mode | No | No |
| Per-site permissions | Read-only, confirm, allowed domains | No | No |
| Site packs and shared shortcuts | Gemini, NotebookLM, a health-checked library | No | No |
| Needs an LLM API key | No | No | Yes |
[!NOTE]
Profiles are kept apart on purpose. Copying a signed-in profile so two browsers share one session gets that
session revoked by Google (and other careful sites), which logs you out everywhere.
Requirements: Node 22+ and Chrome (or
npx playwright install chromium). Works on macOS, Windows and Linux.
1. Sign in to the sites you want, once each. A normal Chrome window opens; sign in, then quit it (Cmd+Q on a Mac, close all its windows on Windows and Linux).
npx -y anysite-mcp login gemini
npx -y anysite-mcp login notebooklm npx -y anysite-mcp login github.com
2. Add the server to your agent.
Claude Code
claude mcp add anysite -- npx -y anysite-mcp
Claude Desktop, Cursor, Windsurf and other MCP clients
Add this to claude_desktop_config.json or the client's MCP settings:
{ "mcpServers": { "anysite": { "command": "npx", "args": ["-y", "anysite-mcp"] } } }
3. Ask your agent to do something on one of those sites. That's it.
With no arguments the server offers every site you have signed in to. To pick sites, list them: npx -y anysite-mcp gemini github.com. The agent can also add a new site at any time by calling web_login.
anysite-mcp is listed in the MCP Registry as io.github.DwytMCL/anysite-mcp, so clients that browse the registry can find and install it.
Each tool takes site: a pack name like gemini, or a domain like github.com.
| Tool | What it does |
|---|---|
web_snapshot | The page's accessibility tree: roles, names, text, and a ref per element ([ref=e12]). Give ref or role/name to see only part of it, depth for an outline. |
web_open | Go to a URL (absolute or relative to the site) |
web_click, web_type, web_select, web_press | Act on an element found by ref, by role and name, or by visible text (add within: "dialog" and so on to look only inside one part of the page). Returns only what changed; show: "full" for the whole page. |
web_read | Text of the page or of one element |
web_extract | Rows as JSON, one per matching element (role: "row", "listitem", "article"…), with optional fields looked up in each |
web_wait | Wait, or wait until some text appears |
web_upload, web_download | Give files to a file picker; save a download |
web_screenshot | PNG of the page, for when the tree is not enough |
web_login | Open a plain window so you can sign in |
web_save_shortcut, web_list_shortcuts, web_delete_shortcut | Turn a working sequence into a tool named _ (tried once before it's saved) |
web_record | Watch the user do a job in the site's window and save it as a shortcut |
Every tool carries MCP annotations for clients that use them, for example to ask before a destructive tool runs. Tools that only read are marked read-only, and tools that can change something on a page (clicking, typing, choosing, pressing keys, uploading) are marked destructive. Shortcut tools are marked by what their steps do.
| Pack | Tools |
|---|---|
gemini | gemini_ask (prompt, files, model, tools such as Create image or Deep Research; returns the reply as markdown), gemini_list_chats |
notebooklm | notebooklm_ask, notebooklm_add_source (URLs, text, files), notebooklm_create_notebook, notebooklm_list_notebooks |
A shortcut is a list of steps, each one the arguments of a web_* tool plus its action. {{param}} is filled in from the tool's arguments, and the shortcut returns the text of its read steps.
expect is text that must be on the page afterwards, so a shortcut fails instead of returning the wrong thing.test_args (set verify: false for steps that must not happen twice, like sending).~/.anysite-mcp/sites/ .json, which you can edit, share or commit.{
"search": { "description": "Search Hacker News and return the results", "params": { "query": "What to search for" }, "steps": [ { "action": "open", "url": "https://hn.algolia.com/?q={{query}}" }, { "action": "wait", "seconds": 5, "until_text": "results", "expect": "{{query}}" }, { "action": "read", "role": "main" } ] } }
Params can also be { "description", "type": "number" | "boolean", "optional", "default" }.
A step whose element is gone is repaired before it fails:
Only a single clear match counts. The shortcut file is updated and the agent is told what changed. If nothing fits, the error says which step and why, and the agent can redo the job and save the shortcut again.
npx -y anysite-mcp record github.com star_repo
Chrome opens on the site; click and type as usual, then press Enter in the terminal. Each typed value becomes a parameter, with what you typed as its default. The agent can do the same with web_record.
npx -y anysite-mcp doctor
doctor follows each shortcut while its steps only open and read pages, checks that the element of the first step that would act is there, and repairs what it can. It never clicks or types.
Each parameter gets its default if it has one. Otherwise an optional parameter is left empty, so the check sees the p
Nur der Anfang wird gezeigt; den Rest findest du im Repo