OmniBrowse

OmniBrowse is a Model Context Protocol (MCP) server providing a private-mode text-based headless browser for AI agents. No Selenium, Playwright, or Chromium — just Node.js with Chrome TLS impersonation (curl-impersonate), jsdom JavaScript execution, full DOM/input handling, and 31 tools designed for AI browsing workflows.

Pages are parsed into an accessibility-style text snapshot with interactive element refs (`r1`, `r2`, …). The model clicks, types, scrolls, and runs JavaScript — each action triggers the real protocol (HTTP/curl-impersonate with true Chrome JA3, or local schemes like data:/file:/ftp:/ipfs:).

Install

Add to your MCP client config (Claude Desktop, Kilo, Cursor, etc.):

{
  "mcpServers": {
    "web-browser": {
      "command": "npx",
      "args": ["-y", "omnibrowse"]
    }
  }
}

> Until the npm package is published, run locally:

>

> ```json

> {

> "mcpServers": {

> "web-browser": {

> "command": "node",

> "args": ["/absolute/path/to/omnibrowse/dist/index.js"]

> }

> }

> }

> ```

Tools

All tools with an empty input schema use `z.object({})` for MCP SDK compatibility.

Protocols

HTTP/HTTPS goes through `curl-impersonate` with `--impersonate chrome131`, producing a true Chrome JA3 fingerprint. Local protocols are handled directly without network access:

Private browsing posture

• Cookies live only in memory for the current MCP session, scoped per hostname. Third-party cookies (cross-registrable-domain Set-Cookie) are dropped. SameSite=None without Secure is rejected.
• DNT: 1 and Sec-GPC: 1 sent on every HTTP request.
• Referer suppressed to origin for cross-origin navigations.
• No persistent cache, history, or storage written to disk between sessions.
• WebRTC (`RTCPeerConnection`) blocked entirely. getUserMedia/getDisplayMedia denied. ServiceWorker.register throws SecurityError.
• Geolocation, notifications, clipboard resolve silently without user prompts (denied/granted respectively).
• Canvas/WebGL/AudioContext return plausible null contexts with no real pixels or audio output (fingerprint-safe).
• crypto.subtle backed by Node's real WebCrypto — modern auth flows (PKCE, JWE) work.
• fetch/XHR observed and recorded for the network-log tool.

Content rendering

Non-HTML resources fetched via `fetch_resource` are handled by content-type-specific renderers:

How it works

Build from source

npm install
npm run build      # outputs dist/
node dist/index.js # run the server (reads JSON-RPC from stdin)

Test

node test/test-comprehensive.mjs  # 31 automated checks: navigation, JS, all protocols, tools, resources
node test/test-ai-browse.mjs      # Realistic 20-step AI browsing session (example.com → HN → DDG → resources → JS eval → protocols)

License

MIT