A
licenseNot graded
qualityC
maintenanceEnables Claude to autonomously drive Firefox by combining Claude's planning with Jev's fast element selection for clicks, navigation, and form actions, reducing latency and token usage.
1
MIT
jev-reflex
by MSalvalaggio
Related Servers
Alternatives to jev-reflex
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.1120 npm5MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude Code and Claude Desktop to control your own Chrome browser, with Jev deciding each click, keystroke, and scroll.5-
- 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
- AlicenseBqualityDmaintenanceA browser automation agent that enables Claude to interact with web browsers through the Model Context Protocol, allowing for actions like navigating websites, manipulating elements, and managing browser state.29MIT
- FlicenseNot gradedqualityCmaintenanceEnables Claude to directly control a persistent, real logged-in Chrome browser via 17 browser tools and 9 trading tools, with natural-language selectors, self-healing element resolution, and risk-limited trading operations.-
TDQS
B3.3/5.0
Scored across 23 tools
Disambiguation4/5
Most tools map cleanly to distinct browser actions, but browser_current_tab and browser_page_info overlap on basic tab metadata, and browser_type vs browser_fill both handle text input. The descriptions help disambiguate, but an agent could plausibly misselect between these pairs.
Naming Consistency4/5
All tools share the browser_ prefix and snake_case style, and the majority follow a clear verb_noun pattern (goto, click, close_tab, new_tab). However, a few names deviate with noun phrases or added prepositions like current_tab, page_info, ensure_real_tab, and wait_for_load, making the pattern mostly but not fully consistent.
Tool Count4/5
At 23 tools, this is on the heavier side, but each tool serves a distinct browser automation capability—navigation, tabs, wait conditions, input, JS/CDP, upload, and recording. The count is justified for a browser control surface, though it slightly exceeds the typical well-scoped range.
Completeness4/5
The tool set covers most standard browser automation needs: navigation, tab management, interaction, waiting, screenshots, JS evaluation, raw CDP, file upload, and session recording. Minor gaps like explicit back/forward/reload, hover, or direct text extraction exist, but these are workable via browser_js or browser_cdp.
Maintenance
ActivityMaintained
ResponsivenessNo issues