Active

io.github.frsorrentino/chrome-bridge

Your real, logged-in Chrome as an MCP server: 63 token-efficient web-dev tools.

GitHub ↗npm ↗
58
TrustScore
✅ No clear abandonment signal detected; complete security and compatibility checks before production use

Before you connect

🔑 Needs an API key / token

Install / Connect

claude mcp add chrome-bridge-mcp -- npx -y chrome-bridge-mcp

Follow the official README; env and args vary per server.

🛠️ Maintenance weight 30% · 84 pts

📝
Last commit1 days ago
📈
Commits in 90 days100
💬
Recent issues with repliesNo response
🗃️
Repo statusNormal

📊 Adoption weight 25% · 27 pts

GitHub stars1 (90d +0%)
📦
npm weekly downloads1.4k
🚀
Releases per month1.7

✅ Usability weight 20% · 55 pts

📋
Official registryPending registry re-verification
▶️
Runnable entryResolvable (npx/remote)
🔍
AuditabilityOpen-source repo, auditable

❤️ Health & community weight 25% · 51 pts

🐛
open issues0
🔀
open PRs
⚖️
LicenseMIT
👥
Contributors / forks1 / 0

Sources: GitHub API · npm registry · updated 2026-08-02

90-day trend

⭐ stars +0%

Similar / alternative servers

How to choose among these

Browser servers differ mainly on local vs. cloud, and whether you need to handle login / dynamic pages.

  • Operate login-gated, JS-rendered sitesPick Playwright MCP — a real browser with the fullest interaction
  • Bulk-scrape static sites to Markdown / feed a knowledge basePick Firecrawl — easiest for whole-site crawl and extraction
  • Want scaled, cloud-hosted browsersPick Browserbase / Hyperbrowser — cloud sessions

One email a week, 5 minutes to see what happened in the MCP ecosystem

New servers, breakout trends, abandonment alerts — tracked automatically, curated by hand, sent to your inbox.

One email a week · unsubscribe anytime · no data selling