jev-explorer
Related Servers
Alternatives to jev-explorer
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.1115 npm4MIT
- 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.37 npm3MIT
- AlicenseNot gradedqualityAmaintenanceEnables an LLM to drive a real browser by declaring one outcome at a time, while Jev chooses the element, action, and value and Playwright executes it, returning a clear status such as done, blocked, or needs confirmation. Also exposes tools to open pages, ask yes/no or multiple-choice questions about a page, read question-relevant page text, capture snapshots and screenshots, act on elements directly, and invoke a page's own WebMCP tools.889 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to automate browser tasks by describing desired outcomes and candidate values, while Jev selects elements/actions and returns statuses, with direct tools for navigation, checks, reading, acting, snapshots, screenshots, and WebMCP calls.889 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code and Claude Desktop to control your own Chrome browser, with Jev deciding each click, keystroke, and scroll.5MIT
- 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
TDQS
Scored across 6 tools
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.
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.
Six tools is well-scoped for a browser exploration server. Each tool covers a necessary part of the workflow without redundancy or bloat.
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.