jev-browser
Related Servers
Alternatives to jev-browser
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables any MCP-capable agent to drive a real Chrome browser through stdio or HTTP, supporting navigation, page reading, interaction, scrolling, JavaScript execution, and replaying saved step-by-step recipes.24Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to drive a Chromium browser over MCP, reading pages as a numbered list of controls and performing actions like clicking, filling forms, and asserting page state without screenshots or API keys.1091 PyPI19MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to drive a live Chrome or Brave browser over stdio, with tools for navigation, clicking, typing, screenshots, and executing automation goals.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables local opencode agents to control a live Chrome browser via MCP tools, including tab management, JavaScript execution, clicking, form filling, page reading, screenshots, and console log retrieval.MIT

orchords-web-pilotofficial
FlicenseAqualityCmaintenanceEnables coding agents to drive a real Playwright-backed browser session, navigating, observing, interacting, and capturing proof on web pages via MCP tools across stdio and Streamable HTTP transports.152-- AlicenseNot gradedqualityDmaintenanceLets coding agents control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.1,305,336 npmApache 2.0
TDQS
Scored across 5 tools
Each tool maps to a distinct phase of browser control: observe reads state, navigate opens URLs, act performs element actions, close ends the session, and config handles configuration. The only mild overlap is that act can perform many action types, but it remains clearly separated from the read-only observe.
All five tools follow an identical 'jev_' prefix plus a concise snake_case verb pattern (observe, navigate, act, close, config), making the set highly predictable and readable.
Five tools is lean but well-scoped for a browser automation agent, with each tool earning its place in the observe-navigate-act-close loop. The addition of config is justified for runtime setup.
The core browser lifecycle (navigate, observe, act, close) is covered, and act likely encompasses clicks, typing, and scrolling via element IDs. Minor gaps like explicit back/forward navigation, tab management, or scroll-only primitives exist but agents can work around them.