jev-ra
Related Servers
Alternatives to jev-ra
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables browser automation through the MCP protocol, allowing AI agents to control a real browser using accessibility snapshots and natural language commands.-
- AlicenseNot gradedqualityAmaintenanceEnables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.13Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables browser automation through the Claude Chrome Extension, allowing agents to navigate websites, fill forms, take screenshots, and debug web apps via standard MCP protocols.1MIT
- AlicenseBqualityBmaintenanceEnables AI agents to perform low-latency web automation with a persistent headed Chrome/Chromium instance, including navigation, DOM interaction, content extraction, screenshots, tab management, and batch/code execution via 18 MCP tools.20MIT
- FlicenseNot gradedqualityBmaintenanceEnables remote browser automation via MCP, allowing models to open pages, read snapshots, click, fill, and select elements using Playwright, with built-in security restrictions against sensitive actions.-
- AlicenseNot gradedqualityDmaintenanceEnables real browser automation as tools in Cursor, Claude Desktop, Windsurf, and any MCP-compatible client, allowing AI agents to interact with web pages through natural language.5 npmMIT
TDQS
Scored across 14 tools
Most tools have clear boundaries: open/search/observe/extract/click/type/select/scroll/press/wait/screenshot/close are distinct actions. The only mild overlap is between browser_observe and browser_extract, but their descriptions separate visible/control inspection from structured data extraction.
Every tool follows the same browser_<verb> pattern with lowercase snake_case throughout. The naming is predictable and makes the action type immediately clear.
14 tools is well within the ideal range for a browser automation server. Each tool covers a meaningful interaction or observation primitive without unnecessary bloat.
The set covers the full core workflow: open, search, observe, interact, extract, screenshot, and close. Minor gaps like explicit back/forward/refresh or tab management exist but are workable through the provided tools.