Skip to content

aside-jev

Browser extension and MCP server where Aside observes the page and Jev picks the next action from defined candidates.

MCP serverbetaMIT

Overview

Aside Jev connects the Aside browser REPL with TypeSafe Jev. Aside observes the page and executes; Jev picks the next browser action from candidates you define. A toolbar toggle, a persistent REPL session and bounded action selection work together, and the jev_browser_run tool delegates action selection to Jev. It does not intercept all built-in Aside tools, only new task instructions and the extension's MCP.

Version 0.2.0 verifies the local MCP launcher, live Jev authentication and the Aside connection before enabling execution, with verification expiring after an hour. Execution is bounded with fresh observations, completion and risk assessment, confidence checks and stop-on-error. Only valid candidates observed on the current page and selected by Jev are executed. The README is careful to say its speed comparison is a localhost transport benchmark, not a measured end-to-end task comparison. Docs are in English and Korean.

What the decision model decides

TypeQuestionAnswers
ChoiceWhich candidate action should the browser take next?—
Yes / noIs the task complete / is this step risky?(inferred)yes · no

How it works

  1. Aside observes the page and builds allowed candidates
  2. Compact observation and candidates are sent to Jev
  3. Jev chooses a candidate ID
  4. Aside re-checks and executes only that valid target
  5. Stop on error, low confidence or completion

Strengths

  • Only observed, allowed targets are executed
  • Keys stored in macOS Keychain
  • Explicit ON verification with expiry

Caveats

  • End-to-end speed versus Aside's default model not measured
  • Depends on the Aside browser

Getting started

Download the 0.2.0 release installers and follow the guided Windows or macOS installation.

At a glance

Type
MCP server
Status
beta
Language
TypeScript
Runtime
browser extension + MCP server
Has code
yes
License
MIT

Use cases and integrations

How curated lists describe it

Frequently asked questions

Is this a Cua binding?

No, Jev is the decision model and Aside is the browser runtime.

What does Jev choose?

The next action from candidate targets observed on the page.

Has it been shown faster than Aside's default model?

Not end to end; the README's comparison is a localhost transport benchmark.

Related projects

  • MCP server and libraries that drive Chrome over CDP and hand a decision model like Jev a bounded menu of page actions.

    ProjectproductionTypeScript
  • Headless browser automation via MCP server, CLI or library: Jev picks one action per step and scores goal-met and stuck probabilities.

    MCP serverbetaTypeScript
  • Claude Desktop MCP extension that drives Brave or Chrome with Jev choosing on-page actions and a guard freezing irreversible clicks.

    MCP serverbetaTypeScript
  • Chrome MCP server with 50 tools that drives your everyday browser without losing logins, where Jev or a local decider picks each step.

    MCP serverbeta
  • Stealth browser agent where Jev decides each step in about 0.3 s and CloakBrowser carries it out; MCP server, CLI and Python API.

    MCP serverbetaPython
  • CodexQA browser skill that indexes in-page controls and has Jev pick the operation and target each step, with no screenshots needed.

    Agent skillbeta