Skip to content

Add jshookmcp to Agentic Browser Automation (real-Chrome CDP hooks) - #200

Open
vmoranv wants to merge 1 commit into
ChromeDevTools:masterfrom
vmoranv:add-jshookmcp-chromedevtools
Open

vmoranv wants to merge 1 commit into
ChromeDevTools:masterfrom
vmoranv:add-jshookmcp-chromedevtools

Conversation

@vmoranv

@vmoranv vmoranv commented Oct 11, 2026

Copy link
Copy Markdown

Adds jshookmcp to Agentic Browser Automation.

Disclosure: I maintain it. Your section note says you are picky with MCP servers that just
wrap a browser — this one does something novel under the CDP hood: it drives your actual
signed-in Chrome (cookies, sessions, login walls stay real) and exposes the live DOM / network
/ CDP layer, TLS keylog, and script injection as agent-callable tools. The point is the agent
verifies end-state against real network responses + DOM mutations, not a UI "success" banner.

  • 735 tools across 36 domains in one stdio server

  • Search-first: ~3K tokens of tool surface instead of ~40K, domains activate on demand

  • Traction: listed in Glama / LobeHub / mcp.so / the MCP Registry; 2.26M-view REA post

  • Install: npx -y @jshookmcp/jshook

  • Licence: AGPL-3.0-only

@google-cla

google-cla Bot commented Oct 11, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant