Bruster
Native-webview browser automation: navigate, fill forms, inspect pages, and capture screenshots.
التثبيت
أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: .cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).
https://github.com/aliilyas/bruster/releases/download/v0.3.2/bruster-0.3.2.mcpbالتوثيق
مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.
bruster
Native webview browser driven by an agent over JSON lines on stdio.
WKWebView · WebKitGTK · WebView2. A small Rust executable using native browser runtimes. No Node required.
Install · Quickstart · MCP · Protocol · API · Performance
bruster uses native browser engines, installed separately where required.
Its Rust controller reads and writes JSON lines on stdin and stdout; rendering
also uses browser helper processes. This design is good for agents, scripts, and test harnesses. The
--mcp option exposes every method as a tool.
Why bruster?
- No Chromium. bruster uses WKWebView on macOS, WebKitGTK on Linux, and WebView2 on Windows. It uses wry to control them.
- Small controller. One small release executable, with a separately installed native browser runtime. The complete runtime footprint includes its libraries and helper processes.
- Agent support. MCP support with
--mcp. Screenshots return as image content, and page events return as notifications. - Cross-platform. Prebuilt for macOS (arm64, x86_64), Linux (x86_64, arm64), and Windows (x86_64).
- Practical API. Navigate, snapshot, click, fill forms, drag, upload, take screenshots, inspect the network and console, manage tabs, and keep a session with
--profile. - Deterministic and safe. Each call is one line-based JSON request and response.
beforeunloadis disarmed, and dialogs never block. - Fast. A persistent HTTP cache and profiles make repeat visits faster. The first tab loads
about:blankwhile the agent starts.
[!TIP] Live benchmarks compare Bruster with the latest stable Playwright, Puppeteer, and agent-browser after every merge to
main: startup, navigation, extraction, screenshots, total process memory, and installed runtime files. See benchmark setup and methodology.
Install
One-liner (recommended)
curl -fsSL https://raw.githubusercontent.com/aliilyas/bruster/main/install.sh | sh
The script installs the correct build for your OS and CPU into ~/.local/bin.
Prebuilt releases
Download archives for all platforms from the Releases page.
From source
cargo build --release
[!NOTE] Linux requirements. WebKitGTK 4.1 is necessary at run time. Install it with one of these commands:
apt install libwebkit2gtk-4.1-0,apk add webkit2gtk-4.1, ordnf install webkit2gtk4.1. If the system has no desktop session, bruster starts again underxvfb-run -awhenDISPLAYis not set.
Quickstart
Run bruster in its native protocol mode:
bruster
Then send JSON objects, one per line:
{"id":1,"method":"navigate","params":{"url":"https://example.com"}}
{"id":2,"method":"snapshot"}
{"id":3,"method":"click","params":{"ref":"e2"}}
{"id":4,"method":"close"}
You receive the results and events on stdout:
{"event":"load","tab":1,"url":"https://example.com/"}
{"id":1,"result":{"url":"https://example.com/"}}
{"id":2,"result":{"url":"https://example.com/","title":"Example Domain","elements":[...]}}
{"id":3,"result":null}
MCP
With --mcp, bruster uses the Model Context Protocol on stdio. Every native
method becomes a tool. Screenshots return as image content, and page events
return as notifications.
Common MCP client configs
// opencode (opencode.json), Claude Desktop (claude_desktop_config.json),
// Cursor (.cursor/mcp.json), Windsurf, Zed
{ "mcpServers": { "bruster": { "command": "bruster", "args": ["--mcp", "--quiet"] } } }
claude mcp add bruster -- bruster --mcp --quiet # Claude Code
codex mcp add bruster -- bruster --mcp --quiet # Codex CLI
// VS Code (.vscode/mcp.json)
{ "servers": { "bruster": { "type": "stdio", "command": "bruster", "args": ["--mcp", "--quiet"] } } }
--mcp keeps the windows off-screen. Add --visible to see the browser.
--hidden is not true headless mode: on Linux, WebKitGTK still requires an
X11/Wayland display or Xvfb. When no display is set, Bruster automatically tries
xvfb-run; install Xvfb if it is unavailable.
On Linux, hidden/MCP mode skips the desktop session bus to avoid waiting for
unavailable desktop portals. Set BRUSTER_USE_SESSION_BUS=1 if you need desktop
session integration in hidden mode. --visible uses the normal session bus.
Run
bruster [--mcp] [--hidden|--visible] [--quiet] [options]
| flag | effect |
|---|---|
--mcp | use the Model Context Protocol on stdio instead of the native protocol. This option also sets --hidden |
--hidden / --visible | move the windows off-screen / show the windows |
--quiet | send stderr to /dev/null. This mutes GL, ALSA, and GTK noise |
--viewport WxH | initial window size, default 1280x800 |
--user-agent UA | replace the user agent |
--profile DIR | keep cookies and storage between runs |
--proxy URL | http://host:port or socks5://host:port |
--init-script FILE | JavaScript that runs in every page before its own scripts |
--dark | persist dark color-scheme for this profile (or the default state); use light to reset |
--insecure | ignore TLS errors (Linux only) |
--no-images | do not load images. Pages load about 30% faster (Linux only) |
Window and color controls
Native commands and MCP tools minimize and maximize target the specified tab
(or the current tab), return "minimized" or "maximized", and persist the requested
window mode. Each mode replaces the previous one. minimize hides the native
window (rather than iconifying it); maximize restores visibility and maximizes.
In hidden/MCP mode both commands are accepted and saved, but windows stay
off-screen for rendering.
dark and light persist a color preference independently of window mode and
apply it to all existing tabs, new tabs, and subsequent navigations. The portable
page-level fallback sets the root CSS color-scheme (including native controls
and default page colors); it does not emulate prefers-color-scheme media queries
or recolor a site's explicit colors. Custom --init-script scripts still run.
Preferences are stored outside WebView data. With --profile PATH, metadata is
a sibling of the canonical profile directory, named PATH.bruster-window.json.
Without a profile, the file is:
- Linux:
$XDG_STATE_HOME/bruster/window.json, falling back to$HOME/.local/state/bruster/window.json. - macOS:
$HOME/Library/Application Support/bruster/window.json. - Windows:
%LOCALAPPDATA%/bruster/window.json.
Settings are profile-wide; the last successful command wins. Missing or malformed
metadata uses defaults, and legacy window-only state files are still accepted.
Persistence failures return protocol errors. OS window-manager changes are not
saved. close shuts down the server and all tabs; close_tab or closing a window
through the OS closes only that tab. Closing stdin also shuts down the server.
Linux uses software rendering. Hidden views skip off-screen GTK painting while
remaining mapped for layout, animation, and native screenshots. Set
BRUSTER_PAINT_HIDDEN=1 to enable those window paints. Hidden mode also defaults
WEBKIT_DISABLE_DMABUF_RENDERER=1 to avoid an unnecessary graphics transport
probe; an explicitly supplied value (including 0) takes precedence.
Automatic Xvfb launches disable GLX. BRUSTER_XVFB_ARGS overrides the server
arguments (default: -screen 0 1280x1024x24 -nolisten tcp -extension GLX). Set
BRUSTER_NO_XVFB=1 to prevent automatic Xvfb startup.
Tests
tests/run_all.sh [--rounds N] [--no-e2e] runs the full suite. The suite does a build, unit tests, smoke tests, edge tests, a leftover-process check, an MCP launch check, and end-to-end tests. On Linux, run the script under xvfb-run -a. CI builds and tests every platform. CI also publishes release archives on v* tags.
The Linux desktop-portal startup regression requires D-Bus, python3-dbus, and
python3-gi:
cargo build --release --locked
xvfb-run -a /usr/bin/python3 tests/startup_portal.py target/release/bruster
Protocol
One JSON object per line, in both directions. Elements are addressed by {"selector": "css"} or by {"ref": "eN"} from the last snapshot/find. With format: "text", a snapshot returns one line per element:
https://example.com/
Example Domain
e1 heading "Example Domain"
e2 text "This domain is for use in..."
e3 link "Learn more" href=https://iana.org/help/example-domains
e4 checkbox "Remember me" checked=false
[!NOTE] Same-origin hrefs lose the origin in the text format. Alert and prompt dialogs never block. bruster answers them as the current
dialogsetting specifies, and reports them asdialogevents.beforeunloadhandlers are disarmed.
Calls routed through the page runtime (eval, url, title, snapshot, interactions and other DOM tools) have an outer request_timeout in milliseconds, defaulting to at least 30000 ms (or the requested timeout/time plus 5000 ms, whichever is longer). This deadline includes time spent waiting for navigation. Set it explicitly for unusually long operations. A timeout stops waiting for the reply; it does not interrupt JavaScript already running in the page. In particular, an infinite loop can make a web process unresponsive and may require restarting bruster. Late replies are discarded. Navigation uses its own timeout; native operations such as screenshots do not use request_timeout. MCP represents null results as the text null.
API
| method | params | result | |
|---|---|---|---|
navigate | url, until? (load default, dom, idle), timeout? ms (default 30000) | {tab, url} on load/DOM/idle, or a failure on timeout, DNS/error, or download (Linux) | |
reload back forward | none | {url}, or null if there is nowhere to go | |
url title | none | string | |
eval | expression | JSON value. Promises are awaited. Compiled as a script | |
snapshot | selector?, max? (1000), boxes?, format? (native default json, MCP default text) | {url,title,elements[],truncated?} or text lines | |
find | text? or regex? + snapshot params | filtered snapshot | |
screenshot | path?, full?, clip? {x,y,width,height} | {path,bytes} or {png_base64}. Full pages are capped at 16000 px | |
rect | target | {x,y,width,height} viewport-relative | |
click | target or x,y; force?, timeout? | null | |
hover | target | null | |
fill | target, value | null | |
fill_form | `fields: [{selector\ | ref, value}]` | null (checkboxes bool, selects string/array) |
type | target, text, delay?, submit? | null | |
press | target?, key (Enter, Control+a) | null | |
select | target, value | selected values | |
check | target, checked? | bool | |
drag | from target, to target | null | |
upload | target, paths[] | file names set on the input | |
scroll | target or x,y deltas | {x,y} current position | |
resize | width, height (1 to 16000) | {width,height} | |
text html | target | string | |
attr | target, name | string or null | |
count | selector | number | |
wait_for | selector/ref + state? (visible, attached, hidden), text, textGone, url, idle, time ms; timeout? ms | null | |
network | clear? | fetch/XHR entries with index, method and status where available, plus resource timing entries | |
network_request | index | one entry with req_headers, res_headers, and body (first 16 KB) | |
console | clear? | [{level,text,ms}] console output and uncaught errors | |
dialog | accept?, text?, clear? | dialogs seen. Sets the answer for the next dialogs | |
cookies | none | list | |
set_cookie | name, value, domain?, path? (/) | null | |
new_tab | url?, timeout? ms (default 30000) | {tab}, or {tab,url} after load; does not switch the current tab | |
tabs | none | [{tab,url,current}] | |
switch_tab | tab | null | |
close_tab | (uses tab) | null; closing the last tab is rejected (use close) | |
close | none | exits |
Events
ready, navigating, load, tab_opened, tab_closed, dialog (type, message, accept), tls_error (Linux), load_failed, and download (Linux).
Limits
- Input uses synthetic DOM events (
isTrustedis false). You do not get:hoverstyles, native<select>popups, or OS-level shortcuts. - Network and console logs are patched in the page and reset on navigation. Network entries for fetch/XHR include status and an index; other resources use performance timings and may lack status or method. The document request is not included. Logs contain no request bodies. Use
--proxyfor real interception. - Cross-origin iframes are out of reach. Same-origin iframes and open shadow roots work.
- Use HTTP(S) URLs for navigation.
data:andfile:URLs are unsupported; serve local pages over localhost instead. - bruster does not intercept native file choosers. Use
uploadinstead of a click on a file input. - Without
--profile, cookies and storage last for one session. - Full-page screenshots are capped at 16000 px. On macOS, very tall pages can be cut when they are higher than the screen.
- WebKitGTK screenshots capture page content without non-overlay scrollbars, so their width can be narrower than the window viewport.
- On Windows (WebView2),
screenshothas noclip.--quietdoes nothing. The Linux-only flags have no effect. - With
--hidden, WebKit timer throttling can makesetTimeout-driven pages slow.
Development
bin/brusterruns the development build from this checkout.tests/run_all.shruns the build, unit tests, smoke tests, edge tests, the MCP launch check, and end-to-end tests.- CI (
.github/workflows/ci.yml) builds all platforms, runs the tests, and publishes release archives onv*tags. - Benchmarks:
scripts/bench_compare.pycompares five configurations;scripts/bench_footprint.pyinventories runtime files andscripts/bench_report.pyvalidates and publishes results. See setup and methodology.
License
الأسئلة الشائعة
ما هو Bruster؟
Native-webview browser automation: navigate, fill forms, inspect pages, and capture screenshots.
كيف أثبّت Bruster؟
اتبع خطوات التثبيت في توثيقه المعروض في هذه الصفحة وفي مستودعه.
هل يحتاج Bruster إلى مفتاح API؟
لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.
هل Bruster مفتوح المصدر؟
نعم. شيفرته متاحة على GitHub بترخيص MIT.
من يصون Bruster؟
ينشره aliilyas. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.
من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.