Unbrowse浏览器MCP工具

Dependency walk for multi-step UIs

Treat each successful browser submit as a dependency boundary.

• Do not jump straight to guessed downstream URLs like /date-selection.html or /payment.html unless the current session already reached them through the real page flow.
• Use unbrowse_submit for the actual transition, then trust the returned url, session_id, and any next-step hints over your own assumptions.
• unbrowse_sync after a good transition so the route graph records which request chain unlocked the next page.
• If a page later returns abandonedCart, session_expired, or a wrong audience/product variant, restart from the last known good upstream step and walk forward again.

The dependency graph is not just API-to-API. On JS-heavy checkout flows it also captures browser-state prerequisites: selected product, resident/non-resident audience, date, slot, auth, and cart state. Future agents should reason from those prerequisites before calling deeper steps.

One-line install from the latest GitHub release

curl -fsSL https://unbrowse.ai/install.sh | sh

That installer now follows the Kuri pattern: detect platform, download the matching release tarball, install `unbrowse` into `~/.local/bin`, then run `unbrowse setup`.

Deterministic setup from a repo clone

git clone --single-branch --depth 1 https://github.com/unbrowse-ai/unbrowse.git ~/unbrowse cd ~/unbrowse && ./setup --host off

`./setup` installs repo dependencies, prebuilds the packaged CLI runtime, installs a stable `unbrowse` shim, and then runs the real first-time bootstrap: ToS acceptance, agent registration + API-key caching, and wallet detection when present.

If a wallet is configured, that wallet address becomes the contributor/payment truth: it is synced onto your agent profile, used as the destination for contributor payouts when your routes earn, and used as the spending wallet for paid marketplace routes.

Recommended for new installs: set up Crossmint `lobster.cash` during bootstrap. `unbrowse setup` now encourages it, and when the tooling is already present it will try `npx @crossmint/lobster-cli setup` automatically. That wallet becomes the payout destination for contributed routes and the spending wallet for paid marketplace routes.

Unbrowse supports wallet providers such as Crossmint `lobster.cash` for x402-gated routes. If you use `lobster.cash`, set `LOBSTER_WALLET_ADDRESS`. Other providers can use `AGENT_WALLET_ADDRESS` and optional `AGENT_WALLET_PROVIDER`.

For repeat npm use after a healthy publish:

The npm package is binary-first: install downloads the prebuilt Bun-compiled CLI for your platform. It does not ship the TypeScript runtime or JS fallback launcher.
On supported platforms, install now fails fast if the matching GitHub release asset is missing or unreachable.

For generic MCP hosts:

That writes a ready-to-import MCP config to `~/.config/unbrowse/mcp/unbrowse.json`. A generic template is also published at [`/mcp.json`](https://www.unbrowse.ai/mcp.json).

If your agent host uses skills:

What setup does

• Checks the local runtime/package-manager environment for the repo bootstrap or packaged CLI path.
• Prebuilds the packaged CLI runtime and installs the stable unbrowse shim for the repo bootstrap path.
• Verifies the bundled Kuri binary, or builds it from the vendored Kuri source when working from repo source with Zig installed.
• Registers the Open Code /unbrowse command when Open Code is present.
• Runs the first-use flow: ToS, agent registration/API-key caching, wallet detection, and Crossmint lobster.cash encouragement.
• Starts the local Unbrowse server unless --no-start is passed.

Quick start

```bash

Demo notes

• First-time capture/indexing on a site can take 20-80 seconds. That is the slow path; repeats should be much faster.
• For website tasks, keep the agent on Unbrowse instead of letting it drift into generic web search or ad hoc curl.
• Reddit is still a harder target than most sites because of anti-bot protections. Prefer canonical .json routes when available.

Configuration

Environment variables

API reference

See SKILL.md for the full API reference including all endpoints, search, feedback, auth, and issue reporting.

Intent resolution pipeline

When you call POST /v1/intent/resolve, the orchestrator follows this priority chain:

1. Route cache (5-min TTL) — instant hit if the same intent was recently resolved
2. Marketplace search — semantic vector search ranked by composite score: 40% embedding similarity + 30% reliability + 15% freshness + 15% verification status
3. Live capture — headless browser records network traffic, reverse-engineers API endpoints, publishes a new skill
4. DOM fallback — if no API endpoints are found (static/SSR sites), structured data is extracted from rendered HTML

Skills published by live capture become available to all agents on the network.