One AI tool gets eyes and hands on the web - on your machine. Open-source, local-first browser automation MCP server: 60 tools across 9 domains, a Sentinel safety gate, local OCR/vision, Edge TTS voice, and CDP real-profile attach. Runs at 127.0.0.1.
Why should Claude be the only one with a browser? Orvima gives any MCP-capable AI (Claude, Cursor, Copilot, your own agent) eyes and hands on your own Chrome or Edge — your logins, your machine, your watch. Self-hosted, local-first, MIT. MCP-native browse_* tools + live viewport.
Sterne
4
Tools
—
Uptime
—
Why Orvima
Live viewport - frames stream to a local dashboard (http://127.0.0.1:8301) you can watch.
list recipes, route a goal to a reviewed recipe or refuse
vision
11
OCR, region OCR, find text, image description, template match, face detection (boxes only), video frames, video OCR, scene changes, multi-pass OCR, browser-screenshot OCR
All tools are plain dict-in/dict-out. Credentials come from arguments or environment variables, never hardcoded.
Mutating tools return {"ok": true, ...} with a verified flag. Read tools return ok: true without verified. browse_eval returns mutating instead. browse_click and browse_navigate accept optional expect_url, expect_text, expect_count (+ expect_for) polled up to expect_timeout_ms; an unmet expectation is a hard error.
Architecture overview
File
Role
src/orvima/mcp_server.py
MCP stdio server binding all 60 tools
src/orvima/tools.py
browse_* tools as dict-in/dict-out functions
src/orvima/browser.py
real browser controller (persistent profile or CDP attach)
src/orvima/cdp.py
page-level CDP client attaching to a single open tab's socket
src/orvima/demo.py
offline simulator with the same tool surface
src/orvima/planner.py
adaptive step planner (LLMPlanner any OpenAI endpoint + DemoPlanner)
Everything runs on 127.0.0.1; no cloud dependency for core operation.
Safety gate (Sentinel)
Sentinel is an optional package and is not a declared dependency. When it is missing or broken the gate is fail-closed: no action can be judged, so no action is auto-approved. Modes:
How you run it
What happens
orvima run (CLI)
fully unattended; no gate constructed
orvima serve, Sentinel not installed
every action waits for a human (including reads)
orvima serve, Sentinel installed
only flagged actions are held for a human verdict
ORVIMA_SENTINEL=off
fully unattended, deliberately; reported as gate: "off"
Check state:
curl -s localhost:8301/api/gate/stats
# {"gate":"degraded","available":false,...} <- nothing is being judged
# {"gate":"on","available":true,...} <- judging is in force
# {"gate":"off",...} <- deliberately unattended
Key mechanisms:
Local, no LLM, no network on the decision path. Default classifier_mode=off decides in ~0.1 ms via pure string matching.
Fail closed, loudly. A throwing classifier, missing policy, or timeout returns allowed: false with degraded: true - a classifier bug never becomes permission.
Approval memory. After a human approves an action, its exact signature (tool + selector/ref/url/value/text) is stored and matching actions are auto-approved without re-running the classifier. Approving "place your order" does not auto-approve "delete account".
Strong-request override. An explicit user request can lift an outward-risk hold to allow, but can never override a destructive-risk denial.
Revalidation. A queued approval can expire while the page changes; the gate rechecks that the referenced element has not moved and the risk has not increased before honouring it (approval_ttl default 300 s).
Auditable. Every decision (risk, reason, classifier output) lands in the session transcript; overrides are appended to an override log.
The gate is a classifier plus a word list - it is wrong in both directions. It reduces reading load; it does not replace judgement.
Approvals
The three run modes and what they mean for approvals:
Mode
Command
Gate status
Behaviour
CLI unattended
orvima run "goal"
none (no gate constructed)
Every action runs without approval. No pauses, no gate.
API serve (Sentinel missing)
orvima serve
degraded (fail-closed)
Every action is refused until a human approves via the dashboard or /api/gate/approve.
API serve (Sentinel installed)
orvima serve
on
Only flagged actions wait for approval; reads and safe actions proceed.
Explicit off
ORVIMA_SENTINEL=off orvima serve
off
Every action runs without approval. Deliberate escape hatch.
Check the current mode at any time:
curl -s localhost:8301/api/gate/stats
# {"gate":"on","available":true,...} <- judging is in force
# {"gate":"degraded","available":false,...} <- nothing is being judged, fail-closed
# {"gate":"off",...} <- deliberately unattended
If a session appears stuck, check /api/gate/stats first. A degraded gate means Sentinel is not installed or failed to load - install it or set ORVIMA_SENTINEL=off if you intentionally want no gate.
Vision module
All vision operations are local-first: Tesseract 5.x for OCR, OpenCV for image/video processing, Pillow for image I/O. No API keys, no network calls.
OCR: grayscale, denoise, unsharp-mask, Otsu threshold, deskew, then multi-source x multi-PSM passes; best-confidence result wins. Low-confidence output is flagged.
Region OCR reads one rectangle (price badge, button label) instead of the whole page.
Text find reports whether a query appears and where.
Image describe returns dimensions, dominant colors, and edge density.
Template match locates a template image inside a page and returns center coords.
Face detection returns count + bounding boxes only. No identity, no recognition, no image data uploaded.
Video: adaptive frame sampling; OCR per sampled frame; scene changes via inter-frame pixel diff.
Multi-pass OCR tries 4 rotations x 3 modes and reports which orientation read best - use as a last resort for sideways screenshots.
Browser-screenshot OCR: screenshots the bound browser's current page and OCRs it in one call (vision_ocr_screenshot).
Dependencies: Tesseract binary is auto-detected from PATH and common install dirs. If missing, every tool returns a clear not available message rather than making the server fail to load. Install via winget install tesseract-ocr.tesseract on Windows or your package manager elsewhere.
orvima serve - local API + UI at http://127.0.0.1:8301.
orvima mcp - stdio MCP server (--mode {demo,real}).
orvima run "goal" - headless agent loop (--mode, --max-steps).
orvima bench - measure agent-loop task pass rate (no browser).
orvima doctor - health check for browser, profile, port, LLM, MCP.
Global flags work with any subcommand. --headless is CI/pod-friendly. ORVIMA_ATTACH_TAB names a single browser tab to avoid CDP handshake stalls on busy profiles.
Why should Claude be the only one with a browser? Orvima gives any MCP-capable AI (Claude, Cursor, Copilot, your own agent) eyes and hands on your own Chrome or Edge — your logins, your machine, your
Why should Claude be the only one with a browser? Orvima gives any MCP-capable AI (Claude, Cursor, Copilot, your own agent) eyes and hands on your own Chrome or Edge — your logins, your machine, your watch. Self-hosted, local-first, MIT. MCP-native browse_* tools + live viewport.
Tools
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Orvima?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Welchen Transport verwendet Orvima?
Orvima läuft lokal über stdio.
Wann wurde Orvima zuletzt geprüft?
Zuletzt geprüft: 2026-10-28. Why should Claude be the only one with a browser? Orvima gives any MCP-capable AI (Claude, Cursor, Copilot, your own agent) eyes and hands on your own Chrome or Edge — your logins, your machine, your watch. Self-hosted, local-first, MIT. MCP-native browse_* tools + live viewport.