Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/adbarc92/mcp-browser-bridgeInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/adbarc92/mcp-browser-bridge/browser-bridge)<a href="https://agentmods.dev/mcp/adbarc92/mcp-browser-bridge/browser-bridge"><img src="https://agentmods.dev/badge/mcp/adbarc92/mcp-browser-bridge/browser-bridge/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/adbarc92/mcp-browser-bridge/browser-bridge"><img src="https://agentmods.dev/badge/mcp/adbarc92/mcp-browser-bridge/browser-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
browser-bridge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"browser-bridge": {
"command": "node",
"args": [
"./dist/index.js"
],
"env": {
"BRIDGE_WS_PORT": "7483"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 11 lines scan A 5b0824c7b2a9
browser-bridge is an MCP server published in the GitHub repository adbarc92/mcp-browser-bridge (1 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-session-bridge
Drive a browser you are already signed into, through the free T3rnel Browser extension. Runs locally from the @t3ratech/mcp-session-bridge npm package. Needs 3 environment variables to run.
eyebrowse
Eyebrowse is an utility which allows you to easily launch, and control browsers from the command line. It was built to launch different browser versions for cross-browser testing. Runs locally from the eyebrowse npm package.
browser-use
Make websites accessible for AI agents. Runs locally from the browser-use Python package.
browser-mcp
Browser MCP - the browser tool that can stop and ask you. A 2FA code, a CAPTCHA, a choice only you can make: it asks on your own screen, then carries on in the tab you were already signed into. 40 tools, any MCP client, MIT. Runs locally from the @agent360/browser-mcp npm package.
devharness
MCP server that connects AI assistants to Chrome DevTools Protocol for runtime debugging - set breakpoints, inspect variables, monitor network traffic, and automate browser interactions. Runs locally from the devharness npm package.
browser-controller
Control your browser. Runs locally from the browser-controller npm package.