F
licenseNot graded
qualityB
maintenanceEnables Claude Code and Claude Desktop to control your own Chrome browser, with Jev deciding each click, keystroke, and scroll.
2
-
cursor-jev
by Pioneer113
Related Servers
Alternatives to cursor-jev
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude Code and Claude Desktop to command the jev-ultrafast browser agent in your real Chrome, autonomously pursuing plain-language goals on a given start URL while enforcing a domain-bound safeguard.3MIT
- AlicenseAqualityCmaintenanceEnables AI agents to delegate complex web browsing goals to a real Chrome instance driven by Jev, completing tasks end-to-end in ~300ms per decision and returning only the final result.111MIT
- AlicenseNot gradedqualityBmaintenanceLets any MCP agent control your signed-in Chrome with full login state, offering normal browser tools and an optional Fast JEV mode for bounded-speed typed decisions on the same profile.MIT
- AlicenseAqualityBmaintenanceEnables agents to delegate browser exploration to Jev by providing natural-language objectives, receiving compact evidence and source context, and continuing the same live browser session through supervisor handoffs.6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to drive a live Chrome or Brave browser over stdio, with tools for navigation, clicking, typing, screenshots, and executing automation goals.3MIT
TDQS
A3.7/5.0
Scored across 5 tools
Disambiguation5/5
Each tool addresses a distinct step in the Jev browser workflow: enumerate tabs, claim a tab, run a chunk, wait for state, and inject host text. No two tools compete for the same responsibility, and the run/wait/type split is clearly delineated.
Naming Consistency3/5
All names share the jev_ prefix and snake_case, but the internal pattern is inconsistent: claim_tab is verb_noun, user_tabs is a noun phrase, browser_run reverses the order, wait is verb-only, and host_type is ambiguous. Still readable and semantically tied to the domain, so moderately coherent.
Tool Count5/5
Five tools is a focused, appropriate size for a specialized Jev browser automation server. Each tool supports a distinct part of the workflow without redundancy.
Completeness4/5
The core loop is covered: list tabs, claim one, run bounded Jev chunks, wait for accessibility text, and type host-supplied text. Minor gaps exist such as no explicit release/stop tool and the resume path after needs_verification is left to the caller, but the main operation can be completed.
Maintenance
ActivityMaintained
ResponsivenessNo issues