Delta Browser
The browser your AI agent actually needs
62 MCP tools · real Chrome, Edge or Chromium · kernel-enforced sandbox · one-command install
Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
62 MCP tools · real Chrome, Edge or Chromium · kernel-enforced sandbox · one-command install
Delta Browser - a Model Context Protocol (MCP) server that gives AI agents a real browser. 62 tools, batched calls, delta snapshots, persistent sessions, and a kernel-enforced sandbox. One-command install.
Delta Browser is a Model Context Protocol (MCP) server that gives an AI agent a real web browser to drive — Chrome, Edge, Chromium, or a managed sandboxed engine — with 62 tools for navigating, clicking, typing, extracting text, capturing screenshots, and asserting on results.
It is a browser for agents, not a browser with an agent bolted on. There is no API key, no hosted service, and no per-run billing. The binary sits between your agent and a browser you already have, over the Chrome DevTools Protocol, so it inherits that browser's profiles and login state.
# Linux, macOS, WSL
curl -fsSL https://raw.githubusercontent.com/DevAnimecx/deltabrowser/main/scripts/install.sh | sh
# Windows PowerShell (5.1 or 7)
irm https://raw.githubusercontent.com/DevAnimecx/deltabrowser/main/scripts/install.ps1 | iex; Install-DeltaBrowser
# Windows CMD
powershell -ExecutionPolicy Bypass -Command "irm https://raw.githubusercontent.com/DevAnimecx/deltabrowser/main/scripts/install.ps1 | iex; Install-DeltaBrowser"
Then prove it works:
delta doctor
Works on Linux, macOS, Windows, and WSL. No admin rights required — everything installs to your user directory, and the installer verifies the download's SHA-256 before it reaches your PATH.
What is an MCP browser? An MCP server that exposes browser control as tools an AI agent can call over the Model Context Protocol, so the agent can navigate, click, type and read pages on its own instead of asking a human to do it.
Do I need Playwright, Puppeteer, Selenium, or Node.js? No. Delta Browser is a single Rust binary. The alternatives are libraries your code drives call-by-call; Delta Browser is a server the agent talks to.
Is it safe to let an agent browse untrusted pages?
On Linux x86_64, yes, within a boundary: each session runs in its own worker process with a Landlock filesystem policy and a seccomp syscall filter applied before the browser starts. On Windows and macOS there is no kernel isolation, and server_status says so rather than implying protection that is not there.
Does it cost anything per run? No. No API keys, no hosted service, no per-run billing. You run it against a browser on your own machine.
Is it open source? It is source-available under the Business Source License 1.1, and converts to Apache-2.0 on 2030-01-01. Free for personal, research, educational and internal business use below USD 10M annual revenue. Full answer.
How do I get from AeroBrowser to Delta Browser? Every renamed name is listed, and there are four steps: migration guide.
An agent that cannot open a page cannot verify a claim, fill a form, or read a rendered result. Most "agent browser" tooling is either a heavyweight automation library the agent must be taught to drive step by step, or a hosted service that charges per run and holds your credentials.
Delta Browser is a single binary that sits between those two:
server_status rather than implying protection it does not provide.batch runs several tools in one MCP message, and snapshot { delta: true } returns only what changed since the last snapshot instead of the whole accessibility tree.Tool counts for the competitors are approximate and change with their upstream releases. Delta Browser's count is exact and asserted in its own test suite.
New to Delta Browser, or coming from AeroBrowser? Start with the FAQ, the agent guide, or the migration table.
curl -fsSL https://raw.githubusercontent.com/DevAnimecx/deltabrowser/main/scripts/install.sh | sh
Install to a specific directory, pin a version, or configure an agent in the same step:
curl -fsSL https://raw.githubusercontent.com/DevAnimecx/deltabrowser/main/scripts/install.sh \
| sh -s -- --dir "$HOME/.local/bin" --agent opencode --install-engine
--versionSHA256SUMSdelta --version and removes the binary if it failsPowerShell 5.1 or PowerShell 7:
irm https://raw.githubusercontent.com/DevAnimecx/deltabrowser/main/scripts/install.ps1 | iex; Install-DeltaBrowser
From a local file, with options:
.\scripts\install.ps1 -InstallDir "$env:USERPROFILE\.local\bin" -Agent opencode
Windows blocks downloaded scripts by default in some configurations. Run the same install with an explicit bypass:
powershell -ExecutionPolicy Bypass -Command "irm https://raw.githubusercontent.com/DevAnimecx/deltabrowser/main/scripts/install.ps1 | iex; Install-DeltaBrowser"
If your environment forbids that, download the binary directly from
Releases, verify it against
SHA256SUMS, and put delta.exe on your PATH.
The installer adds %USERPROFILE%\.local\bin to your user PATH. It takes
effect in new terminals only. To apply it to the current session:
$env:PATH = "$env:USERPROFILE\.local\bin;$env:PATH"
Use the Linux installer inside WSL. Delta Browser and the browser engine both run inside the distribution, so the sandbox features are available:
curl -fsSL https://raw.githubusercontent.com/DevAnimecx/deltabrowser/main/scripts/install.sh | sh
To drive a browser running on the Windows host from inside WSL, start Chrome on
Windows with --remote-debugging-port=9222 bound to all interfaces, then point
Delta Browser at it:
delta connect opencode --cdp http://host.docker.internal:9222
Without WSL, install the Windows build. Both talk to the same MCP interface.
The binary has no runtime dependencies beyond glibc, so it drops into any image:
FROM rust:1-slim AS build
WORKDIR /src
COPY . .
RUN cargo build --release --locked
FROM debian:stable-slim
COPY --from=build /src/target/release/delta /usr/local/bin/delta
# Delta Browser needs a browser; point it at one or use the managed engine.
ENTRYPOINT ["delta"]
CMD ["mcp", "--transport", "stdio"]
docker run --rm -v "$HOME/.delta:/home/delta/.delta" ghcr.io/devanimecx/deltabrowser:latest doctor
In a container, sandboxing is usually provided by the container runtime rather
than by Delta Browser. Set DELTA_PROFILE=scrape and rely on the container's own
isolation.
git clone https://github.com/DevAnimecx/deltabrowser.git
cd deltabrowser
cargo build --release --locked
./target/release/delta --version
To bundle the managed engine into the binary (requires the engine archive from the release pipeline):
cargo build --release --locked --features bundled-moli
Not published to Homebrew, apt, rpm, or crates.io yet. Until they are, use the installer or the release binaries. See docs/ROADMAP.md.
delta doctor
delta doctor checks the engine, sandbox support, browser and daemon ports, the
auth token, and the config path for every known agent. Each failing check prints
the specific fix.
Delta Browser 0.0.1 — environment report: issues
[ok ] build delta 0.0.1 on linux
[ok ] home_directory /home/you
[ok ] engine_detected moli via managed
[ok ] sandbox Landlock ruleset applied
[FAIL] cdp_port nothing listening on 127.0.0.1:9222
-> Launch your browser with --remote-debugging-port=9222, or use a managed engine
[ok ] daemon_port listening on 127.0.0.1:8931
[ok ] auth_token stored token at /home/you/.delta/token.json (44 chars)
Agent configs found: opencode, claude-code
Tools available: 62
Add --json for machine-readable output. Include it in any bug report — it
usually identifies the problem on its own.
Quick sanity check without a browser:
delta tools | python -c "import json,sys; print(len(json.load(sys.stdin)['tools']), 'tools')"
# 62 tools
delta connect opencode # OpenCode
delta connect claude-code # Claude Code
delta connect cursor # Cursor
delta connect codex # Codex
delta connect claude-desktop # Claude Desktop
Then restart your agent so it reloads its MCP configuration.
delta profile list prints the live list. Run delta doctor to see which config
files already exist.
Config generation is implemented and tested for all of these. No client has been run against a live server in this project's validation environment. "It wrote a config file" and "it has been verified end to end" are different claims.
Any client that can spawn a process and speak stdio works, even without a dedicated adapter. Add this server definition:
{
"mcpServers": {
"delta": {
"command": "delta",
"args": ["mcp"],
"env": { "DELTA_CDP": "http://127.0.0.1:9222" }
}
}
}
Transports available: stdio, streamable HTTP, and legacy SSE.
Four actions in one MCP message instead of four round-trips:
{"name": "batch", "arguments": {"calls": [
{"name": "navigate", "arguments": {"url": "https://example.com/login"}},
{"name": "snapshot", "arguments": {"interactive_only": true}},
{"name": "fill", "arguments": {"ref": "@e1_4", "value": "[email protected]"}},
{"name": "click", "arguments": {"ref": "@e1_5"}}
]}}
The response reports requested, executed, failed, stopped_early, and a
results array where each entry has ok plus either result or error and a
duration_ms. Every call is schema-validated before it reaches the browser, so a
typo fails immediately rather than half-completing a sequence.
Set "stop_on_error": false to attempt every call regardless of failures. Maximum
50 calls per batch.
{"name": "snapshot", "arguments": {"delta": true}}
Returns only what changed:
+ button Sign in [ref=e4_2]
~ changed textbox Email [ref=e1_4]
- removed [ref=e2_7]
Elements are fingerprinted on role, accessible name, depth, and disabled state, so a re-render that changes nothing meaningful produces no output.
When
delta.baselineisfalseand areasonis present, the response is a full snapshot — there was no previous baseline, or the document or URL changed. Treat it as a normal snapshot. Never assume a delta response is complete.
navigate to open a URLsnapshot with interactive_only: true to get refsref (@e1_3) or a CSS selectorwait_for before touching anything that loads asynchronouslyevaluate runs arbitrary JavaScript and is for trusted clients only.Full guidance: docs/AGENT-SKILL.md, which is installed alongside your agent's config automatically.
All 62, grouped. delta tools prints the machine-readable inventory;
docs/tools.json is generated from the same source as the server
schema, so the two cannot drift.
# Managed: downloads the engine, applies the sandbox, launches on first use
delta connect opencode --install
# External: use the browser already on your machine
google-chrome --remote-debugging-port=9222 &
delta --engine external --cdp http://127.0.0.1:9222 mcp
On Windows and macOS, delta connect --install finds a locally installed browser
and configures the external engine automatically, because managed engine downloads
are Linux x86_64 only. The result explains the choice in platform_note.
delta sandbox probe # what does this kernel support?
delta profile list # which profiles exist and which are implemented?
On Linux, hard ceilings:
delta --memory-limit-mb 512 --pids-limit 256 mcp
Stated plainly, because "sandboxed" invites assumptions the implementation does not support:
offline is all-or-nothing via seccomp.
There is no allowlist and no connection-time mediation.save_state output yourself.evaluate is not privilege-gated, despite its schema saying otherwise.Full trust model: SECURITY.md.
A small DSL for browser tests that run against a real engine.
open https://example.com/login
wait_for #email
fill #email "[email protected]"
fill #password "hunter2"
click button
assert_text #result "Welcome, [email protected]"
assert_url contains "#dashboard"
python3 -m http.server 4173 --bind 127.0.0.1 --directory examples &
delta test examples/login.delta --report results.html
results.html is a self-contained report with light and dark themes, per-step
durations relative to the slowest step, expandable error detail, and no logged
arguments — safe to attach to a review.
delta validate <file> parses a recipe without touching a browser.
Shorthand verbs: get text, get url, back, forward, reload, tabs,
new-tab, press, wait, scroll, cookies, cdp, save-state, logs,
status.
DELTA_ENGINE defaults to moli in builds with the bundled-moli feature;
published binaries default to external.
delta doctor shows engine_detected failing
On Linux x86_64, run delta engine install moli. Elsewhere, start a browser with
--remote-debugging-port=9222 and run delta connect <agent> --install.
My agent does not list the tools
Restart the agent after delta connect. Confirm it is reading the config file
delta connect wrote — delta doctor lists the paths it checks.
DELTA_TOKEN must contain at least 24 characters
A token was set by hand and is too short. Use 24 or more characters, or delete the
token file to have one generated.
Sandbox errors on Linux
Landlock needs kernel 5.13 or newer. delta sandbox probe reports what your kernel
supports.
sandbox: {"supported": false}
Expected on Windows, unvalidated on macOS. Use an external browser.
The daemon returns 503
The session actor stopped. Run delta start.
A ref is rejected as stale
Refs do not survive navigation or tab switches. Take a fresh snapshot.
Delta always returns a full snapshot
delta.baseline is false with a reason, meaning there was no baseline or the
document or URL changed. Take a second snapshot { delta: true }.
Machine-readable summaries for answer engines and tooling live in
llms.txt, the CycloneDX SBOM in
docs/SBOM.cdx.json, and the tool manifest in
docs/tools.json.
Do I need a Chrome extension or a paid API key? No. Delta Browser talks to Chrome, Edge, or Chromium over the DevTools Protocol, or runs its own managed engine. There is no hosted service and no key.
Can I use my existing browser profile and logins?
Yes, when you run an external engine. Delta Browser creates an isolated context
inside that browser rather than driving your default profile directly, so your
tabs are not disturbed. Logins do not carry over automatically — use
save_state and restore_state to persist cookies and storage.
Does it work on Windows?
Yes. Install with the PowerShell script, then delta connect <agent> --install,
which finds your installed Chrome or Edge. Note that Windows has no kernel-level
isolation; use a container if you need it.
Does it work in Docker? Yes. It is a static-ish binary with no runtime dependencies, and the container runtime provides the isolation.
Is it free for commercial use? Free for personal, research, educational, and internal business use below USD 10M annual revenue. Above that, or if you offer browser automation as a service, a commercial license is required. See LICENSE.
How does it compare to Playwright MCP? Playwright MCP exposes roughly 30 tools and drives the Playwright library. Delta Browser exposes 62, can batch calls, supports delta snapshots, offers a sandboxed managed engine, and has no npm dependency. If you already have Playwright working and do not need batching or sandboxing, either is reasonable.
Why does server_status say sandbox: external browser responsibility?
Because you asked for an external engine. Delta Browser applies no kernel policy to
a browser it did not launch. Switch to a managed engine on Linux to get one.
Are the reported numbers verified? The tool count is asserted in the test suite. Performance and token-efficiency figures are not published, because no reproducible benchmark has been run. When one exists it will ship as a script in this repository.
How do I report a vulnerability? See SECURITY.md. Please do not open a public issue.
Is Delta Browser open source? It is source-available under the Business Source License 1.1, not OSI open source. You get the complete source, and you may use, modify and redistribute it freely for non-production and internal work. It converts to Apache-2.0 on 2030-01-01. Production use above USD 10M annual revenue, or offering browser automation as a service, requires a commercial licence. This is stated plainly so nobody discovers it after building on top of it.
Can I use Delta Browser with LangChain, CrewAI, AutoGen, or any other agent framework?
Yes. Delta Browser speaks the standard Model Context Protocol, so any MCP-capable
client works — not just the ones with a built-in adapter. Run delta agents --config to print a ready-to-paste server block for a client Delta Browser does
not recognise.
How is Delta Browser different from Selenium, Puppeteer, or Playwright? Those are browser-automation libraries: your code drives them imperatively, one call at a time. Delta Browser is an MCP server: the agent chooses tools from a schema and the tool layer decides the sequence. It also adds batching, delta snapshots, and a kernel-enforced sandbox, which are agent-shaped problems that a raw library does not try to solve.
Does Delta Browser replace Playwright MCP? Not universally. If you already have Playwright working and do not need batching, delta snapshots, or sandboxing, either is a reasonable choice. Delta Browser is for the case where the agent is the caller and you want fewer round-trips and a containment boundary.
cargo fmt --check
cargo clippy --locked --all-targets -- -D warnings
cargo test --locked --all-targets
python3 scripts/check-encoding.py # reject mojibake
python3 scripts/check-docs.py # verify links resolve
python3 scripts/check-metadata.py # version and license agreement
See CONTRIBUTING.md for the integration-suite setup and the checklist for adding a tool.
Business Source License 1.1 with an Additional Use Grant.
Free for personal, research, educational, and internal business use by organizations with under USD 10M annual revenue. Production use above that threshold, and offering browser automation as a service, require a commercial license.
Copyright (c) 2026 Blackvault Technology, Inc. and Delta Browser contributors. Change date 2030-01-01, after which the project reverts to Apache-2.0.
Full terms: LICENSE.
Delta Browser - a Model Context Protocol (MCP) server that gives AI agents a real browser. 62 tools, batched calls, delta snapshots, persistent sessions, and a kernel-enforced sandbox. One-command ins
ภาพรวม
Delta Browser - a Model Context Protocol (MCP) server that gives AI agents a real browser. 62 tools, batched calls, delta snapshots, persistent sessions, and a kernel-enforced sandbox. One-command install.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Deltabrowser ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Delta Browser - a Model Context Protocol (MCP) server that gives AI agents a real browser. 62 tools, batched calls, delta snapshots, persistent sessions, and a kernel-enforced sandbox. One-command install.