A
licenseA
qualityB
maintenanceEnables 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.
11
20 npm
5
MIT
jev-explorer
by lazyoft
Related Servers
Alternatives to jev-explorer
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to control a persistent Chrome browser through a local daemon, with Jev performing routine actions and the host agent handling reasoning, text, and verification.223 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude Code and Claude Desktop to control your own Chrome browser, with Jev deciding each click, keystroke, and scroll.5-
- AlicenseAqualityBmaintenanceEnables Cursor to drive Google Chrome through the jev-browser-use click loop, with Cursor supplying tasks, typing text, and verifying results while Jev chooses the next click.51MIT
- AlicenseAqualityBmaintenanceEnables MCP agents to execute whole browser and macOS goals locally, supplying goals, exact values, and completion conditions while Jev handles the observe-decide-act loop.141526MIT
- AlicenseAqualityBmaintenanceEnables coding agents to drive a real Chrome browser to complete natural-language web tasks and return evidence for verification.2MIT
TDQS
A4.4/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a clearly distinct role in the browser session lifecycle: open creates, inspect observes, explore delegates, continue extends, act manually intervenes, and close terminates. The descriptions reinforce these boundaries well, so an agent should have little trouble selecting the right tool.
Naming Consistency5/5
All tool names follow the same 'jev_' prefix plus a single lowercase verb pattern. This is fully consistent and makes the action of each tool predictable from its name.
Tool Count5/5
Six tools is well-scoped for a browser exploration server. Each tool covers a necessary part of the workflow without redundancy or bloat.
Completeness5/5
The tool set forms a complete lifecycle: open a session, inspect it, delegate exploration, continue with additional input, act manually when needed, and close the session. There are no obvious dead ends or missing operations for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues