chrome-agent-bridge
Related Servers
Alternatives to chrome-agent-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible agents and HTTP clients to discover, claim, and control Chrome tabs through an authenticated local bridge, including snapshots, actions, approvals, task ownership, screenshots, frames, diagnostics, and cleanup.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents to securely control the user's already authenticated Chrome browser via explicit tab authorization and DOM-based actions.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLocal MCP server for persistent Chrome automation with multi-profile support, enabling tab management, page inspection, element interaction, JavaScript evaluation, and screenshots while preserving login sessions across restarts.117 npm3MIT
- AlicenseAqualityAmaintenanceMCP server that drives your real Chrome/Edge/Opera browser through a Chrome extension and DevTools Protocol, preserving logins and session state, and can also perform OS-level mouse and keyboard input behind approval.5129 PyPI2MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for browser automation, exposing tools for tab management, navigation, CDP, action plans, and cleanup.302 npm361MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for local browser control via Chrome/Edge extension, enabling agents to open isolated tabs, observe pages, take screenshots, and interact with accessible controls using an existing browser profile. It is agent-agnostic, local-only, and supports safe session scoping with origin grants and sensitive-data blocking.MIT
TDQS
Scored across 100 tools
Many tools overlap: browser_act vs browser_click/fill, browser_snapshot vs browser_screenshot, browser_cdp_send/events vs browser_network_poll, and multiple debugger/network session attachment tools. Descriptions help but boundaries remain blurry, risking misselection.
Dominant prefix_noun_action pattern (browser_, debugger_, sourcemap_) is readable, but bare verbs (watch, breakpoint, understand_code, collect_code) and mixed verb/noun order break consistency.
100 tools far exceed a well-scoped surface; the server spans browser automation, CDP, debugger, network, sourcemaps, binary/proto analysis, WASM, JS deobfuscation, and crypto. This is an extreme mismatch for a single MCP server.
Surface is extremely comprehensive, covering browser control, CDP raw access, debugger lifecycle, network capture, sourcemap analysis, binary/proto/WASM inspection, and JS static analysis. No obvious dead ends for the broad reverse-engineering/browser-bridge purpose.