Skip to main content
Glama

It sees the page, and it acts.

gaze is a CLI + local stdio MCP server that drives the browser you are already signed in to — with a consent gate on every write.

License: MPL-2.0 Tests: 31 consent + launch Benchmark: 100/100 CI: green npm audit: 0 vulns

Usage · Benchmark · Security · Comparison · Research · Roadmap


Most browser automation drives a fresh, anonymous browser. gaze drives the one you are already signed in to.

It is a CLI and a local stdio MCP server. It is not an AI agent: it has no model, no planning and no autonomy. An agent you run (Claude Code, Codex, any MCP client) drives gaze; gaze decides nothing.

  • Reads never prompt. Anything that changes something asks first.

  • Page content comes back wrapped and injection-scanned, never as instruction.

  • Nothing listens on a network port, and nothing phones home.

Receipts

Proof

Result

Benchmark

100/100, grade S on a 12-level anti-scraping course — F1 1.0, perfect conduct, 17.2 s against a 180 s par

Tests

195 automated checks, green on every push/PR; every suite uses a throwaway browser and never touches a real profile

Prompt-injection defence

Scraped output is flagged, not followed (the course plants instructions aimed at the agent — see Security)

Comparison

Says plainly where larger tools beat gaze — and where they cannot act as you

Research

Every design decision traced to published work

Roadmap

Where it is going: any browser, any OS, faster, sourced

Related MCP server: Orvima

Install

git clone https://github.com/KevinTrinhDev/gaze && cd gaze && npm install
ln -s "$PWD/bin/gaze" ~/.local/bin/gaze     # Linux / macOS (Windows: WSL)

Quick start

gaze sync            # clone your logins (close that browser first)
gaze start           # open the automation browser (visible, on purpose)
gaze goto https://news.ycombinator.com
gaze map             # what is clickable, each with a reusable selector

Then read, click, fill, scrape, record, save sessions — see Usage. Anything that will not start: gaze doctor.

Drive it from an AI client

{ "mcpServers": { "gaze": {
    "command": "node", "args": ["/path/to/gaze/mcp.mjs"],
    "env": { "GAZE_APPROVAL": "fingerprint" } } } }

16 tools: read, map, click, fill, login (from a vault you unlocked), session, screenshot, challenge detection, batch. Stdio only, deliberately.

Guardrails

  • Writes ask on the terminal, or for a fingerprint touch (GAZE_APPROVAL=fingerprint). No terminal, no opt-out → refused.

  • grant approves once for a bounded window; there is no --forever.

  • CAPTCHAs are detected and handed to a human — never solved.

  • Passkeys and native sign-in stay human: gaze initiates, you complete.

  • revoke stops everything. stats shows what ran. log shows what failed.

  • It drives a browser holding your real sessions — treat it accordingly.

Browsers

Family

Browsers

Protocol

Chromium

Brave, Chrome, Chromium, Edge, Vivaldi, Opera

CDP

Firefox

Firefox, Dev Edition, BASILISK

WebDriver BiDi

Safari is unsupported (WebKit protocol, macOS only). One browser per identity: sync copies one profile. Roadmap: auto-discovery of whatever is installed — see Roadmap.

Docs

USAGE.md

every command and flag

ARCHITECTURE.md

the reviewed technical blueprint

GAUNTLET.md

the benchmark, level by level

COMPARISON.md

vs Playwright MCP, browser-use, Skyvern, Claude in Chrome and more

SECURITY.md

threat model, consent, CAPTCHA and vault rules

RESEARCH.md

the published work behind the design

ROADMAP.md

any-browser / any-OS plan, research-backed

OPERATING.md

for people changing the driver


Use it with discretion: this drives a browser holding your live sessions and can act as you on any site you are signed in to. Many sites restrict automation; being logged in does not change that. Not affiliated with any browser vendor.

MPL-2.0 · part of the BASILISK ecosystem

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely control a real, logged-in browser with per-site permissions, per-action approvals, secret redaction, and a tamper-evident audit log, all locally without a cloud relay.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP-capable AI client to drive the user's own Chrome or Edge browser through a set of browse_* tools — navigating, clicking, typing, extracting, and managing tabs with their existing logins on their own machine. Runs locally and self-hosted with a live viewport and pause/approve controls so every verified step stays under user watch.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP-capable AI agent to operate the user's own everyday Chrome browser with all existing login sessions intact, offering 22 tools for reading page/network data, filling forms, clicking, batch multi-step actions, and handing CAPTCHAs or confirmations back to the human — without API keys, debug ports, or launch flags.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and MCP clients to safely control the user's real Chrome browser, using shared tabs with per-site approvals, credential-field protection, a kill switch, and an activity log.
      Apache 2.0