Browser Use
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
作者提供的说明(英文原文)
Multi-engine web search, fetch, browser control. 11 tools, keyless lanes.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
GROQ_API_KEYS, TAVILY_KEYS, NV_KEY, SE_KEY, S2_KEY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"websearch": {
"command": "uvx",
"args": [
"skdev-websearch-mcp"
],
"env": {
"GROQ_API_KEYS": "your-value",
"TAVILY_KEYS": "your-value",
"NV_KEY": "your-value",
"SE_KEY": "your-value",
"S2_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add websearch --env GROQ_API_KEYS=your-value --env TAVILY_KEYS=your-value --env NV_KEY=your-value --env SE_KEY=your-value --env S2_KEY=your-value -- uvx skdev-websearch-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"websearch": {
"command": "uvx",
"args": [
"skdev-websearch-mcp"
],
"env": {
"GROQ_API_KEYS": "your-value",
"TAVILY_KEYS": "your-value",
"NV_KEY": "your-value",
"SE_KEY": "your-value",
"S2_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"websearch": {
"type": "stdio",
"command": "uvx",
"args": [
"skdev-websearch-mcp"
],
"env": {
"GROQ_API_KEYS": "your-value",
"TAVILY_KEYS": "your-value",
"NV_KEY": "your-value",
"SE_KEY": "your-value",
"S2_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 SK-DEV-AI 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:GROQ_API_KEYS, TAVILY_KEYS, NV_KEY, SE_KEY, S2_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.10.0)于12天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Browser Use, Chrome DevTools MCP, MCP Server Browser
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
MCP server for Chrome DevTools
MCP server for browser use access
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
mcp-name: io.github.SK-DEV-AI/websearch
Companion agent skills: SK-DEV-AI/skills · npx skills add SK-DEV-AI/skills
Multi-engine web search + fetch MCP server. Parallel fan-out across DuckDuckGo, Bing Web/News RSS, Tavily, Wikipedia, arXiv, Google News RSS, Brave (last resort — rate-limited from some networks), Google AI Mode, and intent-gated vertical lanes (MDN, Stack Exchange, GitHub, HN, Semantic Scholar, OSV vuln, grep.app/Sourcegraph code, GDELT news) — with consensus-merge dedup, a local cross-encoder reranker, and Groq synthesis with grounding checks.
depth defaults to 3 when a model lane is configured (more independent sources; measured) and 1 otherwise. Depth also sets how many pages are fetched: max(5, depth*2), ceiling 8. synthesize returns a short, cited answer that never invents: it says which source backs each claim, surfaces disagreement instead of averaging it, and marks itself truncated when it ran out of budget.offset). Optional distill (see below). For structured JSON use extract.fetch for one.stop_reason so you know whether the site was exhausted or a cap stopped it. Use for "read this whole docs site".javascript:/mailto:, dedups. Use before crawl or to find a "next" button.tables_found so you can pick one.dest_dir and refuses path traversal. Marks truncated if the byte cap stopped the transfer.had_previous: false.fetch. Pass session_id to reuse a persistent tab.browser_action call gets a fresh tab and closes it, so logins and cookies cannot survive. See below.effect (navigated / content_changed / none) so a submit that silently did nothing is visible rather than assumed.stop_reason.papers).Every one of these exists because an agent otherwise writes a one-off script:
| The task | The tool |
|---|---|
| Fetch 20 URLs | fetch_many |
| Read a whole docs site | crawl |
| Get every link on a page | extract_links |
| Pull a pricing table into CSV | extract_table |
| Save a PDF and get its path | download |
| "Did this page change?" | diff_page |
| Log in, then act across several calls | browser_session + browser_action(session_id=...) |
| Fill and submit a form | form_fill_submit |
| Walk "next" through pages | paginate |
browser_action opens one fresh tab per call and closes it afterwards. That is right for a single read, but it makes any interactive workflow impossible: no login, no cookies, no scroll position, no multi-step flow across calls.
A session is a named, long-lived tab:
browser_session(action="create", label="login", url="https://site.example/login")
browser_action(action="type", selector="#email", text="me@example.com", session_id="login-1a2b3c4d") browser_action(action="click", selector="#submit", session_id="login-1a2b3c4d") browser_action(action="text", session_id="login-1a2b3c4d") # same tab, still logged in browser_session(action="close", session_id="login-1a2b3c4d")
Sessions are opt-in: without session_id, behaviour is exactly as before. They are capped at 8 with least-recently-used eviction, tabs are always closed (including on eviction), and metadata is mirrored to ~/.cache/websearch/sessions.json so list can explain what survived a restart. Sessions need a browser, so they are local-only.
A fetched page can be 50k characters. The calling model pays for all of it even when it needed one fact. fetch(distill=true) runs a small model inside the tool first and returns a compressed result:
fetch(url="https://example.com/long-report", distill=True,
distill_question="What are the pricing tiers?")
The result never pretends to be the page:
| Field | Meaning |
|---|---|
distill.distilled | whether a summary was produced |
distill.raw_chars | size of the original text |
distill.grounded | whether every number and quoted span was found in the source |
distill.grounding.numbers_unverified | figures in the summary that do not appear in the source |
distill.grounding.quotes_unverified | quoted spans that are not verbatim |
distill.how_to_get_raw | how to get the untouched text: distill=false |
Below the size threshold (default 4000 chars) distillation is skipped and the raw text is returned, because a summary would cost more than it saves. On any failure the raw text is returned with distill_skipped explaining why - a broken summary is never returned in place of the page.
| Variable | Default | Meaning |
|---|---|---|
DISTILL_BASE_URL | http://127.0.0.1:11435/v1 | any OpenAI-compatible endpoint |
DISTILL_MODEL | reflection/beam:free | model id |
DISTILL_API_KEY | none | bearer token; without it the lane stays off |
DISTILL_RETRIES | 3 | attempts per call (1-10) |
DISTILL_MAX_TOKENS | 3000 | initial completion budget |
DISTILL_MAX_TOKENS_CEILING | 12000 | ceiling when escalating after empty content |
DISTILL_TIMEOUT | 90 | seconds per request |
DISTILL_THRESHOLD_CHARS | 4000 | below this, skip distillation |
search does not just rank results; it writes the answer. That answer is generated from the retrieved text alone, under rules that exist to stop the three failure modes of a search summary:
| Failure | What the prompt does |
|---|---|
| Invention | Nothing from the model's own knowledge. A claim with no citable source is deleted, not softened. If the results do not answer the question, saying so is the correct answer. |
| Bias | Rank is not evidence. The prompt says so explicitly, caps how many sources can come from one domain, requires disagreement between sources to be reported rather than averaged into a number that appears in no source, corrects false premises in the question, and labels vendor claims as vendor claims. |
| Injection | Results are wrapped in and declared untrusted data. A page that says "ignore previous instructions" is data, not instruction; the model must exclude it and say it did. |
Concision is structural, not a wish: a sentence ceiling, an answer-first rule, and a named ban on filler phrasing ("it is important to note", "overall", ...).
Everything is verifiable rather than claimed:
prompt_version, so a quality change can be tied to a revision instead of guessed attemperature is 0, so the same sources give the same textfinish_reason and truncated are returned; a half sentence is labelled instead of looking like a complete thoughtdiversity reports the source mix and whether the per-domain cap had to relaxas_of reports the newest publication date among the sources, and undated sources are labelled "Published: not stated", so freshness is never impliedduplicates_removed counts syndicated copies collapsed before synthesis, and figures_unverified lists numbers the answer contains that appear in no cited source (deterministic, no model call)unusable_sources names the results that could not become evidence - a 404, an error page, or a page with under 400 chars of text - with the reason, and unreadable_sources counts the ones with no text at allfollow_ups and marks synthesis.round = 2. Bounded: once per call, only under a 75s budget, and follow_up=false disables itgrounded) re-reads the answer against the exact text the first pass saw and flags sentences no cited source supports. It is marked advisory because it is another model's opinion, not a proofAll 20 tools carry MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) so a client can tell a read from an action: search and fetch are read-only, download writes a local file without being destructive, browser_session changes local browser state only, and browser_action / form_fill_submit are marked destructive because a click or a form submit can have an effect that cannot be undone from here.
MCP clients cut a tool call at their own timeout (jcode: 300 s) and report a bare Request timeout after 300s with no payload. Measured over one day on a single busy server: 314 calls, median 2.7 s, p90 123 s, max 225 s, and 33 hard client timeouts — the tail is the problem, not the median. So the server bounds its own work instead of hoping the client waits:
| Env | Default | Meaning |
|---|---|---|
WEBSEARCH_TOOL_DEADLINE | 240 | Seconds one tool call may run. Keep it under the client timeout. 0 disables the bound |
WEBSEARCH_MAX_CONCURRENT | 8 | Simultaneous tool calls. Extra callers wait, then get busy. 0 = unlimited |
| WEBSEARCH_QUEUE_WAIT | 20 | Seconds a call may wait for a free slot before being answere
只显示了开头部分;其余内容请在仓库中阅读