nexus-browser
Related Servers
Alternatives to nexus-browser
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to drive the user's already-running Google Chrome through a WebSocket bridge, listing and switching tabs, navigating, clicking, typing, scrolling, extracting DOM, taking screenshots, and evaluating JavaScript. It works without restarting Chrome and preserves all existing logins, cookies, and 2FA sessions.253 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control a user's existing Chrome browser with preserved logins, performing tab management, element interaction, script execution, and screenshots, all locally via a Chrome extension and Python bridge.2MIT
- AlicenseNot gradedqualityAmaintenanceLets AI agents control the real, already-logged-in Chrome browser: reading pages, clicking, typing, navigating tabs, taking screenshots, and inspecting cookies, network traffic, console output, and storage. It connects as a local extension over Native Messaging, so no remote-debugging port or headless profile is needed.1 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control Chrome, Edge, Brave and other Chromium browsers through an extension and native messaging host, exposing a Claude-in-Chrome-compatible tool set for real clicks, typing, screenshots, accessibility-tree reading, page text, form filling, JavaScript execution, console and network inspection, file uploads and GIF recording. Agent sessions run in isolated tab groups with per-site permission prompts, activity logging and a global stop control.Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to create, read, and operate granted background tabs in Chrome via a local stdio MCP server, preserving the human's front tab. Supports tab groups, navigation, clicking/typing, screenshots, and human-priority permissions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally drive the user's own logged-in Chrome browser, including clicking, typing, reading pages, taking screenshots, running JavaScript, recording GIFs, and coordinating parallel agents across Chrome profiles and tab groups.MIT
TDQS
Scored across 49 tools
Most tools target distinct actions, but several overlap in reading/inspecting the page: browser_content, browser_export, browser_axtree, browser_interactive_map, browser_find, browser_vision_inspect and browser_screenshot all serve discovery/extraction, and browser_eval vs browser_cdp_send(Runtime.evaluate) both run code. Descriptions are rich enough to guide selection, but an agent can easily pick the wrong extraction or inspection tool.
All names share the browser_ prefix and snake_case, forming a predictable family. Minor deviations exist: some names are verbs (browser_click, browser_navigate) while others are nouns (browser_content, browser_axtree, browser_logs, browser_pdf), which is readable but not perfectly uniform.
49 tools is far above the typical 3-15 well-scoped range and makes the surface heavy. While browser automation is broad, several tools (cdp_send, eval, webmcp, gsuite export) feel like specialized add-ons rather than core workflow tools.
Coverage is extensive: navigation, tabs, interaction, waits, network, downloads, exports, screenshots, and handoff/2FA checks are all present. Minor gaps exist around direct cookie/storage mutation and browser-level (non-tab) control, but agents can work around them.