1. Conduid
  2. Blockchain
  3. LvcidPsyche/auto-browser
MCP server · Blockchain

LvcidPsyche/auto-browser

based isolated sessions, stdio bridge for Claude Desktop and Cursor.

34Low

Scored 6 months ago · breakdown

About LvcidPsyche/auto-browser

LvcidPsyche/auto-browser is an MCP server in the Blockchain category: based isolated sessions, stdio bridge for Claude Desktop and Cursor.

Install

From source
git clone https://github.com/LvcidPsyche/auto-browser

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about LvcidPsyche/auto-browser

Powered by Claude · Grounded in docs

I know everything about LvcidPsyche/auto-browser. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

Auto Browser

CI MCP Server Local First Glama Open in GitHub Codespaces

Auto Browser demo

Give your AI agent a real browser, with a human in the loop.

Auto Browser is an MCP-native browser control plane for authorized workflows. It gives MCP clients, LLM agents, and operators a shared Playwright browser with human takeover, reusable auth profiles, approvals, audit trails, and local-first deployment.

Works with:

  • Claude Desktop
  • Cursor
  • any MCP client that can talk HTTP or stdio
  • direct REST callers when you want curl-first control

Why Auto Browser

  • MCP-native from day one. The browser surface is already packaged as an MCP server instead of bolted on after the fact.
  • Human takeover when the web gets brittle. noVNC keeps the same live session available when a person needs to step in.
  • Login once, reuse later. Save named auth profiles and reopen fresh sessions that are already signed in.
  • Local-first by default. Run the full stack on your own box with Docker Compose, or use Codespaces for a quick hosted demo.
  • Safety rails built in. Approvals, operator identity, PII scrubbing, Witness receipts, and compliance templates are all part of the product surface.

Release Highlights (v1.0.5)

  • Governed workflow enforcement now blocks write-sensitive agent actions until an approval token is supplied.
  • Social/Veo3 code is no longer shipped in the controller wheel and no HTTP or MCP social routes are registered.
  • Stealth defaults off with STEALTH_ENABLED=false, matching the authorized-workflow product stance.
  • Expanded evals cover auth reuse, popup/download recovery, upload approval, resume recovery, multi-tab recovery, local fixtures, and fast versus governed divergence.
  • Release audit hardening adds fixture validation, dependency audits, wheel inspection, npm audit, and an 80% controller coverage gate.

See CHANGELOG.md for the full release history.

Good Fits

  • internal dashboards and admin tools
  • operator-assisted QA and browser debugging
  • login-once, reuse-later account workflows
  • brittle sites where a human may need to recover the flow
  • MCP-powered agent workflows that need a real browser, not just HTML fetches

Not the Goal

  • stealth or anti-bot work
  • CAPTCHA solving
  • unauthorized scraping or account automation
  • deceptive identity shaping or bypass tooling

What You Get

Browser Control Operator Safety Deployment and Integration
Playwright-backed sessions with screenshots, DOM summaries, OCR excerpts, tab controls, downloads, and network inspection approval gates, operator identity headers, audit events, PII scrubbing, Witness receipts, and protection profiles MCP over HTTP, bundled stdio bridge, REST API, Docker Compose, Codespaces, auth profiles, and optional per-session isolation

Quickstart

git clone https://github.com/LvcidPsyche/auto-browser.git
cd auto-browser
docker compose up --build

That is enough for local development with the default settings.

Optional:

cp .env.example .env
make doctor

Run make doctor from a normal terminal with local Docker access and permission to open localhost sockets.

Open:

  • API docs: http://127.0.0.1:8000/docs
  • Operator dashboard: http://127.0.0.1:8000/dashboard
  • Visual takeover: http://127.0.0.1:6080/vnc.html?autoconnect=true&resize=scale

All published ports bind to 127.0.0.1 by default.

Try It in Codespaces

Open in GitHub Codespaces

Codespaces provisions the stack automatically. The dashboard and noVNC tabs are usually ready in about 90 seconds.

First Useful Demo

The highest-signal flow in this repo is:

  1. create a session
  2. log in manually if the site needs a human
  3. save the session as a named auth profile
  4. open a new session from that auth profile
  5. continue work without reauthing

Start here:

Minimal session creation:

curl -s http://127.0.0.1:8000/sessions \
  -X POST \
  -H 'content-type: application/json' \
  -d '{"name":"demo","start_url":"https://example.com"}' | jq

Minimal observation:

curl -s http://127.0.0.1:8000/sessions/<session-id>/observe | jq

MCP Clients

Auto Browser exposes:

  • an HTTP MCP endpoint at http://127.0.0.1:8000/mcp
  • convenience endpoints at http://127.0.0.1:8000/mcp/tools and http://127.0.0.1:8000/mcp/tools/call
  • a bundled stdio bridge at scripts/mcp_stdio_bridge.py

The default MCP tool profile is curated, which keeps the browser surface compact for better tool selection. If you want the full internal tool surface, set:

MCP_TOOL_PROFILE=full

Raw tool-call example:

curl -s http://127.0.0.1:8000/mcp/tools/call \
  -X POST \
  -H 'content-type: application/json' \
  -d '{
    "name":"browser.create_session",
    "arguments":{
      "name":"demo",
      "start_url":"https://example.com"
    }
  }' | jq

Client setup guides:

Security and Compliance

For a real private deployment, set at least:

APP_ENV=production
API_BEARER_TOKEN=<strong-random-secret>
REQUIRE_OPERATOR_ID=true
AUTH_STATE_ENCRYPTION_KEY=<44-char-fernet-key>
REQUIRE_AUTH_STATE_ENCRYPTION=true
REQUEST_RATE_LIMIT_ENABLED=true
METRICS_ENABLED=true
STEALTH_ENABLED=false

COMPLIANCE_TEMPLATE can apply a preconfigured posture at startup:

Template Auth Encryption Operator ID PII Scrub Isolation Max Session Age
HIPAA required required all layers docker_ephemeral 4h
PCI-DSS required required all layers docker_ephemeral 1h
SOC2 - required network + text shared 24h
GDPR - - all layers shared 24h

All templates require upload approvals. HIPAA, SOC2, and PCI-DSS also enable Witness receipts. Startup writes the applied policy to /data/compliance-manifest.json.

Example:

COMPLIANCE_TEMPLATE=HIPAA docker compose up

For deployment details, hosted Witness notes, CLI auth modes, and reverse-SSH guidance, see:

Architecture at a Glance

flowchart LR
    User[Human operator] -->|watch / takeover| noVNC[noVNC]
    LLM[OpenAI / Claude / Gemini] -->|shared tools| Controller[Controller API]
    Controller -->|Playwright protocol| Browser[Browser node]
    noVNC --> Browser
    Browser --> Artifacts[(screenshots / traces / auth state)]
    Controller --> Artifacts
    Controller --> Policy[Allowlist + approval gates]

Core components:

  • browser-node/ runs Chromium, Xvfb, x11vnc, and noVNC
  • controller/ exposes the FastAPI controller, MCP transport, policy rails, and orchestration endpoints
  • data/ holds runtime artifacts, auth state, approvals, audit logs, and optional CLI caches
  • scripts/ contains local helpers for doctor, smoke tests, bridges, and release checks

Repo Guide

Path What It Contains
controller/ controller API, MCP transport, tests, and packaging
browser-node/ browser runtime and Playwright connection layer
examples/ copy-paste flows and MCP client setup
integrations/langchain/ LangChain, LangGraph, and CrewAI adapters
docs/ architecture, deployment, hardening, and launch docs
scripts/ doctor, smoke harnesses, stdio bridge, and auth helpers
ops/ supporting service templates and operational assets

Common Commands

Command Purpose
make help list available repo commands
make lint run Ruff checks on app, tests, and helper scripts
make test run controller tests in Docker
make test-local run controller tests on host Python 3.10+
make eval run deterministic provider/profile eval scoring
make doctor run the local readiness smoke
make release-audit run the fuller release-validation pass
make smoke-isolation verify per-session Docker isolation
make smoke-reverse-ssh verify reverse-SSH remote access

Documentation Map

If You Want To... Start Here
understand the system shape docs/architecture.md
connect Claude Desktop or Cursor docs/mcp-clients.md
run the curl-first examples examples/README.md
deploy on a trusted host docs/deployment.md
review production constraints docs/production-hardening.md
inspect release history CHANGELOG.md
see where the project is headed ROADMAP.md

Contributing

If you want to help, start with:

Tips moved to TIPS.md.

If Auto Browser is useful, a star helps other people find it.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About LvcidPsyche/auto-browser

How do I install LvcidPsyche/auto-browser?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is LvcidPsyche/auto-browser safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is LvcidPsyche/auto-browser still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.