20 Best Browser Automation MCP Servers, Compared (October 2026)
The short answer
Reach for Chrome DevTools MCP when you need an AI coding assistant to control and inspect a live Chrome browser. It had 52,668 GitHub stars, 2,166 stars gained per 30 days, 1,803,816 npm downloads in a typical week, 308 commits on its default branch in the last 12 weeks, and its last commit 2 days ago. If your work is exploratory browser automation where the agent should hold persistent page state through structured accessibility snapshots, Playwright MCP Server is the better fit: it exposes 25 tools with a tool description grade of B and had 7,262,675 npm downloads in a typical week, with its last commit 2 days ago. If sites block standard automation, SeleniumBase MCP is the more specific answer: it runs a persistent SeleniumBase Pure CDP Mode browser session and includes a solve_captcha tool for Turnstile and reCAPTCHA.
Whichever you choose, give it the narrowest access that still works (a read-only credential, a replica, a scratch account), and widen it only once you have watched what your agent actually asks for.
Glama operates the MCP registry these numbers are measured from, and sells MCP hosting and a gateway. No position on this page is paid for. How the registry is built.
Quick picks
- 1Chrome DevTools MCP : An AI coding assistant debugging a live Chrome browser: it automates actions, records performance traces, monitors network requests, takes screenshots, and reads console messages.
- 2Playwright MCP Server : Exploratory browser automation where an agent holds persistent page state: it exposes navigate, click, form fill, snapshot, and network inspection tools.
- 3SeleniumBase MCP : Sites that block standard automation: it runs a persistent SeleniumBase Pure CDP Mode browser session, with a solve_captcha tool for Turnstile and reCAPTCHA.
- 4Stealth Browser MCP : Automating sites behind Cloudflare or anti-bot login walls with an MCP agent: it documents navigation through real Chrome-family instances via nodriver and CDP.
- 5AIHawk : Driving anti-bot-protected pages from Claude Code, Codex, or Gemini CLI: it exposes 16 MCP browser tools with proxy routing, persistent profiles, and reproducible seeds.
Which one, for your situation
| Your situation | What to use |
|---|---|
| Debugging a live Chrome browser from an AI coding assistant | Chrome DevTools MCP automates actions, records performance traces, monitors network requests, takes screenshots, and reads console messages; it had 52,668 GitHub stars, 1,803,816 npm downloads in a typical week, and 308 commits on its default branch in the last 12 weeks. |
| Exploratory automation with persistent page state and snapshots | Playwright MCP Server exposes navigate, click, form fill, snapshot, and network inspection tools, with 25 tools measured and a tool description grade of B, plus 7,262,675 npm downloads in a typical week. |
| Sites that block standard automation and captchas | SeleniumBase MCP runs a persistent SeleniumBase Pure CDP Mode browser session with a solve_captcha tool for Turnstile and reCAPTCHA, exposes 24 tools, has a tool description grade of A, and had 336,931 PyPI downloads in a typical week. |
| Automating sites already logged into in your Chrome profile | playwriter connects to your running Chrome through an extension so existing sessions, cookies and extensions stay in place, and it had its last commit 3 days ago with 168 commits on its default branch in the last 12 weeks. |
| Testing or scraping in Firefox with DOM snapshots | firefox-devtools-mcp supports snapshot and UID-based interactions plus network monitoring, console capture, and screenshots, and it exposes 34 tools with a tool description grade of A and its last commit 5 days ago. |
| Human-in-the-loop logins on brittle sites | Auto-Browser saves named auth profiles from a live session and hands the same browser to a human via noVNC takeover, with 20 tools and a tool description grade of A, and its last commit was 2 days ago. |
Top MCP servers for Browser Automation
| Best for | Profile | ||||||
|---|---|---|---|---|---|---|---|
| 1 | An AI coding assistant debugging a live Chrome browser: it automates actions, records performance traces, monitors network requests, takes screenshots, and reads console messages. | Community favourite | 52,668 | +2,166 | 2 days ago | 92.5 | |
| 2 | Exploratory browser automation where an agent holds persistent page state: it exposes navigate, click, form fill, snapshot, and network inspection tools. | Community favourite | 37,580 | +1,080 | 2 days ago | 91.9 | |
| 3 | Sites that block standard automation: it runs a persistent SeleniumBase Pure CDP Mode browser session, with a solve_captcha tool for Turnstile and reCAPTCHA. | Community favourite | 13,035 | +75 | 2 days ago | 91.1 | |
| 4 | Automating sites behind Cloudflare or anti-bot login walls with an MCP agent: it documents navigation through real Chrome-family instances via nodriver and CDP. | Community favourite | 2,148 | +318 | 2 days ago | 88.4 | |
| 5 | Driving anti-bot-protected pages from Claude Code, Codex, or Gemini CLI: it exposes 16 MCP browser tools with proxy routing, persistent profiles, and reproducible seeds. | Community favourite | 31,665 | No snapshot history | 2 days ago | 84.1 | |
| 6 | Debugging an app in an already logged-in Chrome tab: it attaches through a DevTools extension and exposes console, network, screenshot, and Lighthouse audit tools. | Community favourite | 7,326 | +30 | 46 days ago | 83.7 | |
| 7 | Operator-assisted logins on brittle sites: it saves named auth profiles from a live session and hands the same browser to a human via noVNC takeover. | Community favourite | 793 | +16 | 2 days ago | 80.1 | |
| 8 | MCP clients that need direct Chrome DevTools Protocol control: one use_browser tool handles navigation, interaction, extraction, screenshots, and auto-captures DOM actions. | Community favourite | 355 | +13 | 2 days ago | 78.6 | |
| 9 | Browser automation across agent runtimes where a Chrome extension plus CLI is acceptable: it exposes tab, navigation, CDP, action plan and cleanup tools over MCP. | Community favourite | 311 | +73 | 19 days ago | 78.3 | |
| 10 | Testing or scraping a site in a Firefox instance you control, using UID-based DOM snapshots and clicks, plus network and console capture. | Community favourite | 431 | +64 | 5 days ago | 76.6 | |
| 11 | Browser automation against a real headless browser for goal-directed tasks: it exposes one tool, jev_navigate, which takes a task and start URL. | Community favourite | 271 | No snapshot history | today | 75.7 | |
| 12 | Driving a Chrome profile already logged in: it controls the user's own browser through a companion extension, so existing sessions work without API keys. | Emerging | 231 | +231 | yesterday | 74.6 | |
| 13 | Playwright automation under CloakBrowser's Chromium: a drop-in upstream Playwright tool surface plus humanized input, Docker, and Streamable HTTP. | Community favourite | 65 | +13 | today | 74.1 | |
| 14 | Anyone who needs LinkedIn data through their own logged-in session: it exposes 17 tools for profiles, companies, jobs, messaging and connection requests. | Community favourite | 3,629 | +396 | today | 73.5 | |
| 15 | Automating tasks in an already-configured Chrome profile: it runs as a Chrome extension and reuses existing login states instead of launching a separate browser. | Abandoned but popular | 12,441 | +111 | 264 days ago | 73.2 | |
| 16 | Authenticated browser work needing parallel lanes: it controls real Chrome via CDP and exposes worker, tab, cookie, storage, and form tools. | Community favourite | 237 | +1 | 4 days ago | 71.7 | |
| 17 | Developers recording browser interactions and generating Playwright test files: it provides start/end codegen session tools alongside 32 browser automation tools. | Abandoned but popular | 5,658 | +19 | 289 days ago | 70.1 | |
| 18 | When testing web or mobile apps on BrowserStack: it exposes tools for live sessions, test runs, last-failure debugging, and accessibility scans. | Community favourite | 152 | +2 | 2 days ago | 69.8 | |
| 19 | People who want professional task templates inside an assistant they already use: it installs markdown SKILL.md files via npx or the Claude plugin directory. | Community favourite | 1,407 | +96 | 5 days ago | 69.1 | |
| 20 | Automating sites you are already logged into: it connects to your running Chrome through an extension, so existing sessions, cookies and extensions stay in place. | Community favourite | 3,922 | +91 | 3 days ago | 68.1 |
The ranking, with the evidence
Each position is a weighted mean of adoption (40%), maintenance (24%), momentum (14%), tool description quality (13%) and trust (9%), multiplied by three attenuators: how directly the server is about Browser Automation (named for it, declaring it, tagged with it, or merely mentioning it), whether its repository is still moving, and how much independent evidence of adoption it has. Open the score on any entry to see every number, including the ones marked ≈, which were imputed from the median of the other candidates rather than measured. The maintenance grade on each entry is mostly issue responsiveness, release recency and open security alerts rather than commits, so a recent commit beside a low grade is two different measurements rather than a contradiction.
- Abandoned but popular: People use it, but its default branch has stopped moving. Fine to keep running, risky to adopt.
- Community favourite: Widely adopted and still actively maintained.
- Dormant: Neither changing nor widely adopted. Here because it still matches the search.
- Emerging: Small audience, growing quickly, maintained. The bet with the most upside.
- Steady: Maintained, modest audience, no surprises in either direction.
Best for: An AI coding assistant debugging a live Chrome browser: it automates actions, records performance traces, monitors network requests, takes screenshots, and reads console messages.
Chrome DevTools MCP acts as an MCP server and CLI that let coding agents control and inspect a live Chrome browser, documenting browser automation through Puppeteer, performance traces, network request analysis, screenshots, and console messages. Before choosing it, note that it requires Node.js LTS, npm, and current stable Google Chrome or newer, and officially supports only Google Chrome and Chrome for Testing.
GitHub stars52,668Stars / 30 days+2,166npm / typical week1.8MPyPI / typical weekno attributed packageTools exposednever inspectedLast commit2 days agoCommits / 12 weeks308Maintenance gradeATool descriptionsNot gradedScore 92.5: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars100
- npm downloads100
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum77 / 100 · weight 14%
- Stars gained, relative to size84
- Stars gained, absolute100
- npm download trend36
- Tool quality≈68 / 100 · weight 13%
- Tool description quality≈68tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integrates100
- Weighted mean of the five
- 92.5
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 92.5
Best for: Exploratory browser automation where an agent holds persistent page state: it exposes navigate, click, form fill, snapshot, and network inspection tools.
Playwright MCP is a Model Context Protocol server that drives a browser through Playwright, exposing 25 tools for navigation, clicking, form filling, accessibility snapshots, tab and dialog handling, and console and network inspection without screenshots or vision models. Before choosing it, note that it requires Node.js 18 or newer, and its README directs coding agents toward a CLI plus skills workflow instead, since MCP loads tool schemas and accessibility trees into the model context.
GitHub stars37,580Stars / 30 days+1,080npm / typical week7.3MPyPI / typical weekno attributed packageTools exposed25Last commit2 days agoCommits / 12 weeks29Maintenance gradeATool descriptionsBScore 91.9: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars100
- npm downloads100
- Used through Glama32
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum77 / 100 · weight 14%
- Stars gained, relative to size70
- Stars gained, absolute100
- npm download trend64
- Tool quality68 / 100 · weight 13%
- Tool description quality60
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integrates100
- Weighted mean of the five
- 91.9
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 91.9
Best for: Sites that block standard automation: it runs a persistent SeleniumBase Pure CDP Mode browser session, with a solve_captcha tool for Turnstile and reCAPTCHA.
SeleniumBase MCP exposes 24 tools that drive a browser session: start_browser and close_browser for lifecycle, open_url, manage_history and manage_tabs for navigation, find_elements, get_content, get_attributes and check_if_condition for reading a page, click_element, type_text, select_option, hover_action, focus_element, scroll_page and run_javascript for interaction, alongside manage_cookies, manage_storage, manage_window, wait_for_condition, assert_condition, save_page and solve_captcha. Choosing it means adopting SeleniumBase's Pure CDP Mode, since the session has to be launched with start_browser before the interaction tools are usable, and no npm package is published, so the install comes through the seleniumbase package on PyPI.
GitHub stars13,035Stars / 30 days+75npm / typical weekShips no npm packagePyPI / typical week336.9KseleniumbaseTools exposed24Last commit2 days agoCommits / 12 weeks253Maintenance gradeATool descriptionsAScore 91.1: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars100
- PyPI downloads50PyPI downloads show no weekday rhythm; halved
- Used through Glama86
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum37 / 100 · weight 14%
- Stars gained, relative to size31
- Stars gained, absolute76
- PyPI download trend0
- Tool quality100 / 100 · weight 13%
- Tool description quality93
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integrates100
- Weighted mean of the five
- 91.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 91.1
Best for: Automating sites behind Cloudflare or anti-bot login walls with an MCP agent: it documents navigation through real Chrome-family instances via nodriver and CDP.
Stealth Browser MCP is an MCP-compatible browser automation server that documents stdio setup for MCP clients and uses nodriver, Chrome DevTools Protocol, and FastMCP to drive Chrome, Chromium, or Edge. Before choosing it, note that it requires Python 3.10+ and a locally installed Chrome, Chromium, or Microsoft Edge browser, and measurements list no published npm package and no attributed PyPI package.
GitHub stars2,148Stars / 30 days+318npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit2 days agoCommits / 12 weeks20Maintenance gradeATool descriptionsNot gradedScore 88.4: show every number behind it
- Adoption83 / 100 · weight 40%
- GitHub stars83
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum100 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute100
- npm download trendnot measuredno download history for the selected registry
- Tool quality≈68 / 100 · weight 13%
- Tool description quality≈68tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 88.4
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 88.4
Best for: Driving anti-bot-protected pages from Claude Code, Codex, or Gemini CLI: it exposes 16 MCP browser tools with proxy routing, persistent profiles, and reproducible seeds.
The server exposes 16 browser-automation tools over MCP for navigating, clicking, typing, reading text, HTML, snapshots, screenshots, watching, and evaluating JavaScript, and its README also documents a standalone web UI with chat beside a live browser. The standalone web UI requires an OpenRouter API key supplied with --openrouter-key or OPENROUTER_API_KEY, while the MCP installation uses plugin or extension commands for Claude Code, Codex, or Gemini CLI.
GitHub stars31,665Stars / 30 daysno snapshot historynpm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed16Last commit2 days agoCommits / 12 weeks288Maintenance gradeATool descriptionsAScore 84.1: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars100
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum≈0 / 100 · weight 14%
- Stars gained, relative to sizenot measuredno snapshot history yet
- Stars gained, absolutenot measuredno snapshot history yet
- npm download trendnot measuredno download history for the selected registry
- Tool quality85 / 100 · weight 13%
- Tool description quality77
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integrates100
- Weighted mean of the five
- 84.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 84.1
Best for: Debugging an app in an already logged-in Chrome tab: it attaches through a DevTools extension and exposes console, network, screenshot, and Lighthouse audit tools.
It provides an MCP server plus a Chrome extension that capture console output, network activity, screenshots, storage, and Lighthouse accessibility, performance, SEO, and best-practices audits from Chrome tabs with DevTools open. The main constraint is that it requires Node 22.19 or newer and a manually loaded Chrome extension, with capture active only while Chrome DevTools is open.
GitHub stars7,326Stars / 30 days+30npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit46 days agoCommits / 12 weeks23Maintenance gradeATool descriptionsNot gradedScore 83.7: show every number behind it
- Adoption97 / 100 · weight 40%
- GitHub stars97
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance90 / 100 · weight 24%
- Last commit touching this server88
- Repository maintenance grade100
- Commit cadence85
- Momentum40 / 100 · weight 14%
- Stars gained, relative to size26
- Stars gained, absolute60
- npm download trendnot measuredno download history for the selected registry
- Tool quality≈68 / 100 · weight 13%
- Tool description quality≈68tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 83.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 83.7
Best for: Operator-assisted logins on brittle sites: it saves named auth profiles from a live session and hands the same browser to a human via noVNC takeover.
Auto-Browser runs a Playwright browser as an MCP server over HTTP or through a bundled stdio bridge, exposing 20 tools for sessions, tabs, observations, screenshots, downloads, actions, auth profiles, and JavaScript evaluation, alongside a REST API and Docker Compose deployment. Choosing it means running Docker locally, accepting that CAPTCHA solving and unauthorized scraping are out of scope, and expecting operator approval for actions such as browser.eval_js.
GitHub stars793Stars / 30 days+16npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed20Last commit2 days agoCommits / 12 weeks88Maintenance gradeATool descriptionsAScore 80.1: show every number behind it
- Adoption72 / 100 · weight 40%
- GitHub stars72
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum52 / 100 · weight 14%
- Stars gained, relative to size54
- Stars gained, absolute50
- npm download trendnot measuredno download history for the selected registry
- Tool quality83 / 100 · weight 13%
- Tool description quality75
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 80.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 80.1
Best for: MCP clients that need direct Chrome DevTools Protocol control: one use_browser tool handles navigation, interaction, extraction, screenshots, and auto-captures DOM actions.
superpowers-chrome exposes a single MCP tool, use_browser, which controls a persistent Chrome browser via Chrome DevTools Protocol and automatically captures DOM actions to a session directory. A constraint worth knowing is that it is distributed through the Claude Code plugin marketplace rather than an npm package, and headed Linux/WSL2 use requires the DISPLAY environment variable.
GitHub stars355Stars / 30 days+13npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed1Last commit2 days agoCommits / 12 weeks24Maintenance gradeATool descriptionsAScore 78.6: show every number behind it
- Adoption64 / 100 · weight 40%
- GitHub stars64
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100dated from the last commit on the default branch, re-read from GitHub at publication; the stored date would have published 51 days ago
- Repository maintenance grade100
- Commit cadence85
- Momentum58 / 100 · weight 14%
- Stars gained, relative to size66
- Stars gained, absolute46
- npm download trendnot measuredno download history for the selected registry
- Tool quality98 / 100 · weight 13%
- Tool description quality90
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 78.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 78.6
Best for: Browser automation across agent runtimes where a Chrome extension plus CLI is acceptable: it exposes tab, navigation, CDP, action plan and cleanup tools over MCP.
open_browser_use is an MCP server, launched as
obu mcp, that exposes browser tools for tab listing, opening, claiming, navigation, CDP, action plans, and cleanup, and it also ships JavaScript, Python, and Go SDKs plus a CLI. Before choosing it, note the dependency it assumes: setup registers a native messaging host and a matching Chrome extension from the Chrome Web Store, so a Chrome browser and the open-browser-use CLI are required.GitHub stars311Stars / 30 days+73npm / typical week196PyPI / typical weekno attributed packageTools exposednever inspectedLast commit19 days agoCommits / 12 weeks7Maintenance gradeBTool descriptionsNot gradedScore 78.3: show every number behind it
- Adoption66 / 100 · weight 40%
- GitHub stars62
- npm downloads24downloads show none of the weekday rhythm human traffic has; halved
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance88 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence65
- Momentum93 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute75
- npm download trend100
- Tool quality≈68 / 100 · weight 13%
- Tool description quality≈68tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 78.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 78.3
Best for: Testing or scraping a site in a Firefox instance you control, using UID-based DOM snapshots and clicks, plus network and console capture.
firefox-devtools-mcp exposes 34 tools that drive Firefox over WebDriver BiDi via Selenium WebDriver, covering page and tab control, UID-based snapshot interactions, form filling, screenshots, downloads, extensions, screencasts, and script evaluation. It requires a local Firefox installation (it cannot run on cloud hosting) and recommends a dedicated Firefox profile rather than a personal one.
GitHub stars431Stars / 30 days+64npm / typical week1.1KPyPI / typical weekno attributed packageTools exposed34Last commit5 days agoCommits / 12 weeks130Maintenance gradeATool descriptionsAScore 76.6: show every number behind it
- Adoption76 / 100 · weight 40%
- GitHub stars66
- npm downloads65
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum92 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute73
- npm download trend100
- Tool quality73 / 100 · weight 13%
- Tool description quality65
- Built and inspected by Glama100
- Trust0 / 100 · weight 9%
- License0
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 76.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 76.6
Best for: Browser automation against a real headless browser for goal-directed tasks: it exposes one tool, jev_navigate, which takes a task and start URL.
Jev Browser exposes a single jev_navigate tool that drives a real headless browser from a task and start URL, and its README also documents CLI and library interfaces plus MCP client install commands. Before choosing it, note that it requires Node.js 22 or newer and an API key for a Jev transport, and Playwright's Chromium downloads automatically on install unless opted out.
GitHub stars271Stars / 30 daysno snapshot historynpm / typical week0PyPI / typical weekno attributed packageTools exposed1Last committodayCommits / 12 weeks57Maintenance gradeATool descriptionsAScore 75.7: show every number behind it
- Adoption61 / 100 · weight 40%
- GitHub stars61
- npm downloads0downloads show none of the weekday rhythm human traffic has; halved
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum44 / 100 · weight 14%
- Stars gained, relative to sizenot measuredno snapshot history yet
- Stars gained, absolutenot measuredno snapshot history yet
- npm download trend44
- Tool quality93 / 100 · weight 13%
- Tool description quality85
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 75.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 75.7
Best for: Driving a Chrome profile already logged in: it controls the user's own browser through a companion extension, so existing sessions work without API keys.
huashu-chrome is an npm package whose CLI writes MCP configuration for a documented list of agents (Claude Code, Codex CLI, Cursor, Gemini CLI, Cline, Windsurf and others), and whose MCP server talks over a local bridge on 127.0.0.1 to a companion Chrome extension that performs the clicking and filling. Before choosing it, note that the extension must be loaded by hand through chrome://extensions because browsers do not let a script install it, and that browser-protected pages such as the Chrome Web Store cannot be driven by any extension.
GitHub stars231Stars / 30 days+231npm / typical week0PyPI / typical weekno attributed packageTools exposednever inspectedLast commityesterdayCommits / 12 weeks46Maintenance gradeCTool descriptionsNot gradedScore 74.6: show every number behind it
- Adoption59 / 100 · weight 40%
- GitHub stars59
- npm downloads0downloads show none of the weekday rhythm human traffic has; halved
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance89 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade55
- Commit cadence100
- Momentum85 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute95
- npm download trend44
- Tool quality≈68 / 100 · weight 13%
- Tool description quality≈68tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 74.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 74.6
Best for: Playwright automation under CloakBrowser's Chromium: a drop-in upstream Playwright tool surface plus humanized input, Docker, and Streamable HTTP.
It runs upstream @playwright/mcp as its tool surface pointed at CloakBrowser Chromium, exposing 25 tools for navigation, clicking, form filling, snapshots and screenshots, network request inspection, tab handling, and two local introspection tools reporting package and bridge metadata. Before choosing it, note that it requires Node.js 22.13 or 24 and above, and that browser_run_code_unsafe executes arbitrary JavaScript in the Playwright server process, which the README calls RCE-equivalent.
GitHub stars65Stars / 30 days+13npm / typical week406PyPI / typical weekno attributed packageTools exposed25Last committodayCommits / 12 weeks115Maintenance gradeATool descriptionsBScore 74.1: show every number behind it
- Adoption62 / 100 · weight 40%
- GitHub stars45
- npm downloads56
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum62 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute46
- npm download trend11
- Tool quality58 / 100 · weight 13%
- Tool description quality50
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 74.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 74.1
Best for: Anyone who needs LinkedIn data through their own logged-in session: it exposes 17 tools for profiles, companies, jobs, messaging and connection requests.
The server drives a locally running browser session logged into LinkedIn to expose 17 tools covering person and company profiles, job search and details, feed and inbox reading, messaging, and connection requests. Choosing it assumes the user can authenticate with their own LinkedIn account in that browser session, since every lookup and write action runs against that live session rather than a separate API.
GitHub stars3,629Stars / 30 days+396npm / typical weekShips no npm packagePyPI / typical week9.6Kmcp-server-linkedinTools exposed17Last committodayCommits / 12 weeks249Maintenance gradeATool descriptionsAScore 73.5: show every number behind it
- Adoption95 / 100 · weight 40%
- GitHub stars89
- PyPI downloads42PyPI downloads show no weekday rhythm; halved
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum97 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute100
- PyPI download trend89
- Tool quality73 / 100 · weight 13%
- Tool description quality65
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 94.2
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 73.5
Best for: Automating tasks in an already-configured Chrome profile: it runs as a Chrome extension and reuses existing login states instead of launching a separate browser.
Chrome MCP Server is a Chrome extension-based MCP server that connects an AI assistant to the user's existing Chrome browser, with README documentation covering a global mcp-chrome-bridge install, a manually loaded unpacked extension, and streamable HTTP. Choosing it requires Node.js 20 or higher and a global mcp-chrome-bridge installation before loading the extension, and the README states the project is in early development.
GitHub stars12,441Stars / 30 days+111npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit264 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 73.2: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars100
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance32 / 100 · weight 24%
- Last commit touching this server42
- Repository maintenance grade30
- Commit cadence5
- Momentum56 / 100 · weight 14%
- Stars gained, relative to size39
- Stars gained, absolute83
- npm download trendnot measuredno download history for the selected registry
- Tool quality≈68 / 100 · weight 13%
- Tool description quality≈68tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 73.2
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 73.2
Best for: Authenticated browser work needing parallel lanes: it controls real Chrome via CDP and exposes worker, tab, cookie, storage, and form tools.
OpenChrome is a browser automation MCP server and Node CLI that controls a real Chrome browser via CDP, with 122 exposed tools for navigation, computer actions, page reads, forms, JavaScript, network capture, cookies, storage, screenshots, PDFs, tabs, workers, and workflows. Before choosing it, note that it requires Node.js 20 or newer, and setup writes client configuration that requires restarting the MCP host.
GitHub stars237Stars / 30 days+1npm / typical week973PyPI / typical weekno attributed packageTools exposed122Last commit4 days agoCommits / 12 weeks173Maintenance gradeATool descriptionsBScore 71.7: show every number behind it
- Adoption73 / 100 · weight 40%
- GitHub stars59
- npm downloads64
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum15 / 100 · weight 14%
- Stars gained, relative to size24
- Stars gained, absolute15
- npm download trend0
- Tool quality58 / 100 · weight 13%
- Tool description quality50
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 71.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 71.7
Best for: Developers recording browser interactions and generating Playwright test files: it provides start/end codegen session tools alongside 32 browser automation tools.
mcp-playwright exposes 32 tools that drive Playwright to navigate pages, click, fill and select elements, handle iframes, take screenshots, run JavaScript, inspect console logs, send HTTP requests, save PDFs, and record codegen sessions. Before choosing it, note that installation is via the npm package @executeautomation/playwright-mcp-server, and it assumes Playwright browser binaries, which it can download automatically on first use or can be installed manually with npx playwright install.
GitHub stars5,658Stars / 30 days+19npm / typical week18.3KPyPI / typical weekno attributed packageTools exposed32Last commit289 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsBScore 70.1: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars94
- npm downloads91
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance32 / 100 · weight 24%
- Last commit touching this server42
- Repository maintenance grade30
- Commit cadence5
- Momentum36 / 100 · weight 14%
- Stars gained, relative to size23
- Stars gained, absolute52
- npm download trend39
- Tool quality66 / 100 · weight 13%
- Tool description quality57
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 70.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 70.1
Best for: When testing web or mobile apps on BrowserStack: it exposes tools for live sessions, test runs, last-failure debugging, and accessibility scans.
The BrowserStack MCP server exposes five tools: runTestsOnBrowserStack, runAppLiveSession, runBrowserLiveSession, getFailuresInLastRun, and startAccessibilityScan, and its README documents one-click setup for VS Code and Cursor plus a hosted Streamable HTTP endpoint. Before choosing it, note that getFailuresInLastRun applies only when a browserstack.yml file is present in the project root.
GitHub stars152Stars / 30 days+2npm / typical week9.8KPyPI / typical weekno attributed packageTools exposed5Last commit2 days agoCommits / 12 weeks228Maintenance gradeBTool descriptionsBScore 69.8: show every number behind it
- Adoption88 / 100 · weight 40%
- GitHub stars55
- npm downloads80downloads capped: not corroborated by repository audience
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance95 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence100
- Momentum48 / 100 · weight 14%
- Stars gained, relative to size37
- Stars gained, absolute21
- npm download trend100
- Tool quality66 / 100 · weight 13%
- Tool description quality57
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integrates100
- Weighted mean of the five
- 82.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 69.8
Best for: People who want professional task templates inside an assistant they already use: it installs markdown SKILL.md files via npx or the Claude plugin directory.
The README documents a library of plain-markdown SKILL.md files that an assistant reads to handle professional tasks, installed through the Claude plugin directory,
npx pm-claude-skills add, or run free in a browser playground. No tool list has been measured for this server and the README documents no browser automation interface, so it is not a pick for driving pages or a headless browser.GitHub stars1,407Stars / 30 days+96npm / typical week2.3KPyPI / typical weekno attributed packageTools exposednever inspectedLast commit5 days agoCommits / 12 weeks395Maintenance gradeATool descriptionsNot gradedScore 69.1: show every number behind it
- Adoption84 / 100 · weight 40%
- GitHub stars79
- npm downloads36downloads show none of the weekday rhythm human traffic has; halved
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum94 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute80
- npm download trend100
- Tool quality≈68 / 100 · weight 13%
- Tool description quality≈68tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 88.6
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 69.1
Best for: Automating sites you are already logged into: it connects to your running Chrome through an extension, so existing sessions, cookies and extensions stay in place.
Playwriter documents a Chrome extension plus a CLI with commands to start a browser, create isolated sessions, execute Playwright JavaScript snippets against them, and manage tab groups, alongside a connectViaExtension() Node API. Before it works the extension must be installed and connected to a running browser, and there is no default page, so each script must create a tab or locate an existing one by URL.
GitHub stars3,922Stars / 30 days+91npm / typical weekdownloads not countedPyPI / typical weekno attributed packageTools exposednever inspectedLast commit3 days agoCommits / 12 weeks168Maintenance gradeATool descriptionsNot gradedScore 68.1: show every number behind it
- Adoption90 / 100 · weight 40%
- GitHub stars90
- npm downloadsnot measurednpm publishes root from mafintosh/root
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum69 / 100 · weight 14%
- Stars gained, relative to size62
- Stars gained, absolute79
- npm download trendnot measuredno download history for the selected registry
- Tool quality≈68 / 100 · weight 13%
- Tool description quality≈68tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 87.3
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 68.1
Questions people ask
How do I choose between Chrome DevTools MCP and Playwright MCP Server?
Choose Chrome DevTools MCP if an AI coding assistant needs to control and inspect a live Chrome browser, including performance analysis, debugging, network request monitoring, screenshots and console messages. It had 52,668 GitHub stars, 1,803,816 npm downloads in a typical week, and 308 commits on its default branch in the last 12 weeks. Choose Playwright MCP Server for exploratory browser automation where an agent holds persistent page state through structured accessibility snapshots without requiring vision models or screenshots. It exposes 25 tools with a tool description grade of B, had 7,262,675 npm downloads in a typical week, and its last commit was 2 days ago.
What does SeleniumBase MCP require before it will run?
You install it from the PyPI package seleniumbase, which had 336,931 downloads in a typical week. The server is built around a persistent SeleniumBase Pure CDP Mode browser session for sites that block standard automation. It exposes 24 tools with a tool description grade of A, and its last commit was 2 days ago.
What should I be careful about with Chrome MCP Server?
Chrome MCP Server is labelled Abandoned but popular, with its last commit 264 days ago and 0 commits on its default branch in the last 12 weeks. It still had 12,441 GitHub stars and 111 stars gained per 30 days, and it runs as a Chrome extension that reuses existing login states. If you need recent activity, consider playwriter, which had its last commit 3 days ago and 168 commits on its default branch in the last 12 weeks.
Which server should I use for Cloudflare or anti-bot login walls?
Stealth Browser MCP is for undetectable browser automation that bypasses Cloudflare, antibots, and social media blocks, using real Chrome-family instances via nodriver and CDP. It had 2,148 GitHub stars, 318 stars gained per 30 days, and 20 commits on its default branch in the last 12 weeks, with its last commit 2 days ago. SeleniumBase MCP is another option for sites that block standard automation, with a persistent SeleniumBase Pure CDP Mode browser session and a solve_captcha tool for Turnstile and reCAPTCHA. AIHawk targets anti-bot-protected pages from Claude Code, Codex, or Gemini CLI and exposes 16 MCP browser tools with a tool description grade of A.
How do I automate a browser profile that is already logged in?
playwriter connects to your running Chrome browser through an extension, so existing sessions, cookies and extensions stay in place. It had 3,922 GitHub stars, 91 stars gained per 30 days, 168 commits on its default branch in the last 12 weeks, and its last commit was 3 days ago. Chrome MCP Server also runs as a Chrome extension and reuses existing login states, but it is labelled Abandoned but popular with its last commit 264 days ago and 0 commits in the last 12 weeks. huashu-chrome controls the user's own browser through a companion extension, with existing sessions working without API keys or re-authentication.