20 Best Browser Automation MCP Servers, Compared (October 2026)
The short answer
Most developers should install Playwright MCP Server. It exposes 25 tools for navigation, clicks, typing, forms, snapshots and tabs, its tool description grade is B, and @playwright/mcp recorded 7,371,788 npm downloads in a typical week; it had a commit 10 days ago and 33 commits on its default branch in the last 12 weeks. If the sites you automate block ordinary automation, SeleniumBase MCP is the better answer: it drives a persistent SeleniumBase CDP Mode browser and ships a solve_captcha tool for detectable CAPTCHAs, with 24 tools at grade A and 316,400 PyPI downloads for seleniumbase in a typical week.
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
- 1SeleniumBase MCP : Scraping sites that block ordinary automation: it drives a persistent SeleniumBase CDP Mode browser and ships a solve_captcha tool for detectable CAPTCHAs.
- 2Chrome DevTools MCP : Live Chrome debugging during coding-agent sessions: it exposes an MCP server and CLI for browser automation, console and network inspection, and performance traces.
- 3Playwright MCP Server : Automating web pages with an MCP client via structured accessibility snapshots: it exposes 25 tools for navigation, clicks, typing, forms, snapshots, and tabs.
- 4Stealth Browser MCP : Automating sites behind Cloudflare, anti-bot checks, or login walls: it drives a real Chrome-family browser via nodriver and CDP for navigation and element extraction.
- 5Auto-Browser : Operator-assisted workflows on brittle sites that need login reuse: it exposes session, human takeover, and saved auth profile tools.
Which one, for your situation
| Your situation | What to use |
|---|---|
| I want one server working this afternoon | Playwright MCP Server ships as @playwright/mcp with 7,371,788 npm downloads in a typical week, exposes 25 tools for navigation, clicks, typing, forms, snapshots and tabs, and had a commit 10 days ago. |
| The sites I scrape block ordinary automation | SeleniumBase MCP drives a persistent SeleniumBase CDP Mode browser and ships a solve_captcha tool for detectable CAPTCHAs, exposes 24 tools at grade A, and had a commit 1 day ago with 288 commits in the last 12 weeks. |
| I need console, network and performance debugging | Chrome DevTools MCP attaches to a live Chrome browser for console and network inspection and performance traces, with 1,674,540 npm downloads in a typical week, a commit 0 days ago and 380 commits in the last 12 weeks. |
| Automation has to reuse my existing Chrome login | huashu-chrome drives your own Chrome through MCP and an extension with your existing login state, and had a commit 6 days ago with 56 commits in the last 12 weeks. |
| My team works in Firefox, not Chrome | firefox-devtools-mcp exposes 35 tools at grade A for UID snapshots, network monitoring, console capture, screenshots and downloads, with 117 commits in the last 12 weeks and a commit 2 days ago. |
| I need to scrape LinkedIn profiles and jobs | LinkedIn MCP Server exposes 17 tools for profiles, companies, jobs, feed, inbox, messaging and connection requests, with 10,931 PyPI downloads for mcp-server-linkedin in a typical week and 451 commits in the last 12 weeks. |
Top MCP servers for Browser Automation
| Best for | Profile | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Scraping sites that block ordinary automation: it drives a persistent SeleniumBase CDP Mode browser and ships a solve_captcha tool for detectable CAPTCHAs. | Community favourite | 13,080 | +64 | yesterday | 93.2 | |
| 2 | Live Chrome debugging during coding-agent sessions: it exposes an MCP server and CLI for browser automation, console and network inspection, and performance traces. | Community favourite | 53,685 | +1,540 | today | 90.6 | |
| 3 | Automating web pages with an MCP client via structured accessibility snapshots: it exposes 25 tools for navigation, clicks, typing, forms, snapshots, and tabs. | Community favourite | 38,212 | +994 | 10 days ago | 90.2 | |
| 4 | Automating sites behind Cloudflare, anti-bot checks, or login walls: it drives a real Chrome-family browser via nodriver and CDP for navigation and element extraction. | Community favourite | 2,221 | +133 | 6 days ago | 88.3 | |
| 5 | Operator-assisted workflows on brittle sites that need login reuse: it exposes session, human takeover, and saved auth profile tools. | Community favourite | 906 | +161 | today | 86.8 | |
| 6 | Running goal-directed tasks in a real headless browser: it exposes jev_navigate, which takes a task and start URL and enforces step or time budgets. | Community favourite | 336 | +107 | 4 days ago | 82.3 | |
| 7 | Agents that need to drive a real Chrome install: it documents tab, navigation, CDP, and action-plan tools paired with a browser extension and CLI. | Community favourite | 370 | +77 | 3 days ago | 81.3 | |
| 8 | Debugging a logged-in Chrome session: it attaches via a Chrome extension and streams console, network, screenshots, and Lighthouse audits to MCP clients. | Community favourite | 7,329 | +4 | 2 days ago | 81.0 | |
| 9 | When automation must reuse a Chrome login: it drives the user's own browser via MCP and extension for form filling, clicking, data fetching, and captchas. | Community favourite | 322 | +124 | 6 days ago | 79.0 | |
| 10 | Local Chrome automation through a single MCP tool: use_browser drives a persistent browser over the DevTools Protocol and auto-captures each DOM action. | Community favourite | 361 | +7 | 8 days ago | 76.8 | |
| 11 | Running multi-session browser automation over Streamable HTTP with CloakBrowser Chromium: it forwards upstream Playwright MCP browser tools plus CloakBrowser binary and bridge info. | Emerging | 167 | +146 | today | 75.5 | |
| 12 | For agentic browsing or agent-assisted web development with local Firefox: it exposes 35 tools for UID snapshots, network monitoring, console capture, screenshots, and downloads. | Community favourite | 494 | +79 | 2 days ago | 74.1 | |
| 13 | Automating a browser from plain-English assistant instructions while keeping logins alive: AIHawk exposes 16 MCP tools for navigation, clicks, typing, reading, screenshots, and JavaScript evaluation. | Community favourite | 32,150 | +606 | 4 days ago | 73.7 | |
| 14 | LinkedIn outreach and research through an authenticated browser session: it exposes 17 tools for profiles, companies, jobs, feed, inbox, messaging, and connection requests. | Community favourite | 3,895 | +386 | 2 days ago | 72.7 | |
| 15 | Automating tasks in an already logged-in Chrome profile: it runs as a Chrome extension and reuses the browser's existing configuration and login state. | Abandoned but popular | 12,488 | +64 | 285 days ago | 71.9 | |
| 16 | Debugging BrowserStack test failures or running manual app/browser sessions from an MCP client: it exposes last-run failure, live session, test instructions, and accessibility scan tools. | Community favourite | 155 | +4 | 2 days ago | 69.8 | |
| 17 | Automating a Chrome session that already has logins and extensions: it connects to the running browser through a Chrome extension and exposes the Playwright API. | Community favourite | 4,010 | +126 | 11 days ago | 69.1 | |
| 18 | Cleaning up tabs and researching in the user's own Firefox: tab and tab-group management, history search, and consent-gated page reading through a paired extension. | Community favourite | 334 | +13 | 56 days ago | 68.1 | |
| 19 | Recording Playwright actions into generated test code: it exposes codegen session tools alongside navigation, click, fill, and screenshot actions. | Abandoned but popular | 5,668 | +14 | 310 days ago | 67.6 | |
| 20 | Sessions needing a logged-in Chrome profile: it drives a real Chrome browser over CDP and exposes worker and workflow tools for isolated parallel tabs. | Community favourite | 236 | -1 | 25 days ago | 66.9 |
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: Scraping sites that block ordinary automation: it drives a persistent SeleniumBase CDP Mode browser and ships a solve_captcha tool for detectable CAPTCHAs.
It exposes 24 tools over one persistent browser session, covering navigation and history, element finding, clicking, typing, dropdowns, cookies and web storage, tabs and windows, JavaScript evaluation, and saving a page to disk. The session model assumes start_browser runs first and close_browser runs last, and the package is distributed only as seleniumbase on PyPI, so a JavaScript-only stack has nothing here to install.
GitHub stars13,080Stars / 30 days+64npm / typical weekShips no npm packagePyPI / typical week316.4KseleniumbaseTools exposed24Last commityesterdayCommits / 12 weeks288Maintenance gradeATool descriptionsAScore 93.2: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars100
- PyPI downloads50PyPI downloads show no weekday rhythm; halved
- Used through Glama69
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum52 / 100 · weight 14%
- Stars gained, relative to size29
- Stars gained, absolute73
- PyPI download trend67
- 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
- 93.2
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 93.2
Best for: Live Chrome debugging during coding-agent sessions: it exposes an MCP server and CLI for browser automation, console and network inspection, and performance traces.
Chrome DevTools MCP is an MCP server, with a companion CLI, that lets coding agents control and inspect a live Chrome browser for automation, debugging, console and network request monitoring, and performance tracing. Before choosing it, note that it requires Node.js LTS, npm, and a current stable Chrome or newer, and officially supports only Google Chrome and Chrome for Testing.
GitHub stars53,685Stars / 30 days+1,540npm / typical week1.7MPyPI / typical weekno attributed packageTools exposednever inspectedLast committodayCommits / 12 weeks380Maintenance gradeATool descriptionsNot gradedScore 90.6: 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
- Momentum63 / 100 · weight 14%
- Stars gained, relative to size70
- Stars gained, absolute100
- npm download trend6
- 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
- 90.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 90.6
Best for: Automating web pages with an MCP client via structured accessibility snapshots: it exposes 25 tools for navigation, clicks, typing, forms, snapshots, and tabs.
Playwright MCP Server provides an MCP interface to Playwright browser automation, exposing 25 tools such as browser_navigate, browser_snapshot, browser_click, browser_type, browser_fill_form, browser_network_requests, and browser_tabs. It requires Node.js 18 or newer and an MCP client, and the standard configuration launches @playwright/mcp@latest through npx.
GitHub stars38,212Stars / 30 days+994npm / typical week7.4MPyPI / typical weekno attributed packageTools exposed25Last commit10 days agoCommits / 12 weeks33Maintenance gradeATool descriptionsBScore 90.2: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars100
- npm downloads100
- Used through Glama36
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum60 / 100 · weight 14%
- Stars gained, relative to size67
- Stars gained, absolute100
- npm download trend0
- 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
- 90.2
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 90.2
Best for: Automating sites behind Cloudflare, anti-bot checks, or login walls: it drives a real Chrome-family browser via nodriver and CDP for navigation and element extraction.
Stealth Browser MCP is an MCP stdio server that drives a real Chrome-family browser through nodriver and the Chrome DevTools Protocol, documented for navigation, element cloning, network inspection, request hooks, and CDP execution. Before choosing it, note that it is installed from a cloned repository rather than an npm or PyPI package, and it requires Python 3.10+ plus a local Chrome, Chromium, or Edge browser.
GitHub stars2,221Stars / 30 days+133npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit6 days agoCommits / 12 weeks31Maintenance gradeATool descriptionsNot gradedScore 88.3: show every number behind it
- Adoption84 / 100 · weight 40%
- GitHub stars84
- 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
- Momentum93 / 100 · weight 14%
- Stars gained, relative to size99
- Stars gained, absolute86
- 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.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 88.3
Best for: Operator-assisted workflows on brittle sites that need login reuse: it exposes session, human takeover, and saved auth profile tools.
Auto-Browser is an MCP-native browser control plane that exposes 20 tools for creating sessions, navigating, observing pages, executing actions, managing tabs and downloads, saving or loading auth profiles, and requesting human takeover, with MCP over HTTP, a bundled stdio bridge, and a REST API. Before choosing it, note that its quickstart runs the stack with Docker Compose on localhost and that it explicitly does not target CAPTCHA solving, unauthorized scraping, or account automation.
GitHub stars906Stars / 30 days+161npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed20Last committodayCommits / 12 weeks61Maintenance gradeATool descriptionsAScore 86.8: show every number behind it
- Adoption74 / 100 · weight 40%
- GitHub stars74
- 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
- Momentum96 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute89
- 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
- 86.8
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 86.8
Best for: Running goal-directed tasks in a real headless browser: it exposes jev_navigate, which takes a task and start URL and enforces step or time budgets.
Jev Browser drives a real headless browser through an MCP server, CLI, or library, and its one tool, jev_navigate, takes a task and start URL and uses TypeSafe's Jev model to pick one action per step until the goal is met, the stuck gate fires, or a budget runs out. Before choosing it, note that it requires Node.js 22 or newer, a Jev transport API key (TypeSafe direct is the default), and Playwright's Chromium, which downloads automatically unless JEV_BROWSER_SKIP_BROWSER_DOWNLOAD is set.
GitHub stars336Stars / 30 days+107npm / typical week0PyPI / typical weekno attributed packageTools exposed1Last commit4 days agoCommits / 12 weeks89Maintenance gradeATool descriptionsAScore 82.3: show every number behind it
- Adoption63 / 100 · weight 40%
- GitHub stars63
- 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
- Momentum81 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute82
- npm download trend44
- 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
- 82.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 82.3
Best for: Agents that need to drive a real Chrome install: it documents tab, navigation, CDP, and action-plan tools paired with a browser extension and CLI.
Open Browser Use ships as an MCP server invoked with
obu mcp, exposing browser tools for tab listing, opening, claiming, navigation, CDP, action plans, and cleanup, with the same layer reachable through JavaScript, Python, and Go SDKs or the CLI. Setup is not just an MCP config entry: the machine needs the globally installed CLI and the matching Chrome extension with its native host registered throughopen-browser-use setup, while an embedded Electron browser instead requires the host-authorizedobu iab mcproute.GitHub stars370Stars / 30 days+77npm / typical week249PyPI / typical weekno attributed packageTools exposednever inspectedLast commit3 days agoCommits / 12 weeks17Maintenance gradeATool descriptionsNot gradedScore 81.3: show every number behind it
- Adoption68 / 100 · weight 40%
- GitHub stars64
- npm downloads26downloads show none of the weekday rhythm human traffic has; halved
- 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
- Momentum93 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute76
- 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
- 81.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 81.3
Best for: Debugging a logged-in Chrome session: it attaches via a Chrome extension and streams console, network, screenshots, and Lighthouse audits to MCP clients.
BrowserTools MCP runs as an npx MCP server that pairs with a Chrome extension to expose tools including console logs, network logs, selected elements, page info, screenshots, storage, browser refresh, and Lighthouse accessibility, performance, SEO, and best-practices audits. The main constraint is that it requires Node 22.19 or newer, the Chrome extension loaded, and DevTools open on the target tab, because it reads from the current Chrome session rather than driving a fresh automated browser.
GitHub stars7,329Stars / 30 days+4npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit2 days agoCommits / 12 weeks23Maintenance gradeBTool descriptionsNot gradedScore 81.0: 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
- Maintenance92 / 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 67 days ago
- Repository maintenance grade80
- Commit cadence85
- Momentum18 / 100 · weight 14%
- Stars gained, relative to size10
- Stars gained, absolute29
- 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
- 81.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 81.0
Best for: When automation must reuse a Chrome login: it drives the user's own browser via MCP and extension for form filling, clicking, data fetching, and captchas.
huashu-chrome documents an MCP server plus a Chrome extension, installed through an npm package and CLI, that lets MCP-compatible agents drive the user's own Chrome to fill forms, click elements, fetch data, and handle captchas. Before choosing it, note that installation assumes Node.js and requires the user to add the Chrome extension manually, since browsers do not allow scripts to perform that step.
GitHub stars322Stars / 30 days+124npm / typical week35PyPI / typical weekno attributed packageTools exposednever inspectedLast commit6 days agoCommits / 12 weeks56Maintenance gradeATool descriptionsNot gradedScore 79.0: show every number behind it
- Adoption65 / 100 · weight 40%
- GitHub stars63
- npm downloads17downloads 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
- Momentum80 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute85
- npm download trend38
- 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
- 79.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 79.0
Best for: Local Chrome automation through a single MCP tool: use_browser drives a persistent browser over the DevTools Protocol and auto-captures each DOM action.
superpowers-chrome exposes a single MCP tool, use_browser, for controlling a persistent Chrome browser over the Chrome DevTools Protocol with automatic page capture. Before choosing it, note that headed mode on Linux or WSL2 requires the DISPLAY environment variable to be configured for the MCP server.
GitHub stars361Stars / 30 days+7npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed1Last commit8 days agoCommits / 12 weeks35Maintenance gradeATool descriptionsAScore 76.8: 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
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum44 / 100 · weight 14%
- Stars gained, relative to size49
- Stars gained, absolute37
- npm download trendnot measuredno download history for the selected registry
- 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
- 76.8
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 76.8
- 11
Best for: Running multi-session browser automation over Streamable HTTP with CloakBrowser Chromium: it forwards upstream Playwright MCP browser tools plus CloakBrowser binary and bridge info.
CloakBrowser MCP exposes 25 tools, including the upstream Playwright MCP browser automation set and the CloakBrowser binary and bridge info, with npm or Docker installation over stdio or Streamable HTTP. The dependency to note is that it runs upstream @playwright/mcp as the canonical tool surface and points that runtime at CloakBrowser Chromium.
GitHub stars167Stars / 30 days+146npm / typical week392PyPI / typical weekno attributed packageTools exposed25Last committodayCommits / 12 weeks84Maintenance gradeATool descriptionsBScore 75.5: show every number behind it
- Adoption60 / 100 · weight 40%
- GitHub stars56
- npm downloads28downloads 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
- Momentum79 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute87
- npm download trend30
- 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
- 75.5
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 75.5
Best for: For agentic browsing or agent-assisted web development with local Firefox: it exposes 35 tools for UID snapshots, network monitoring, console capture, screenshots, and downloads.
It controls Firefox through WebDriver BiDi (via Selenium WebDriver) and exposes 35 tools for tab/page control, UID snapshots and interactions, form filling, screenshots, PDFs, downloads, dialogs, extensions, screencasts, script evaluation, and Firefox output inspection. Before choosing it, note that it requires a local Firefox installation and cannot run on cloud hosting services, so deployment is local.
GitHub stars494Stars / 30 days+79npm / typical week1.6KPyPI / typical weekno attributed packageTools exposed35Last commit2 days agoCommits / 12 weeks117Maintenance gradeATool descriptionsAScore 74.1: show every number behind it
- Adoption72 / 100 · weight 40%
- GitHub stars67
- npm downloads34downloads 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
- Momentum85 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute77
- npm download trend69
- Tool quality71 / 100 · weight 13%
- Tool description quality63
- 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
- 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: Automating a browser from plain-English assistant instructions while keeping logins alive: AIHawk exposes 16 MCP tools for navigation, clicks, typing, reading, screenshots, and JavaScript evaluation.
AIHawk exposes 16 MCP tools that let assistants such as Claude Code, Codex, and Gemini CLI drive a browser over MCP: opening main or support browsers, navigating, reading text or HTML, snapshotting interactive elements, clicking, typing, selecting options, pressing keys, taking screenshots, watching the live window, and evaluating JavaScript. Before choosing it, note that it is self-hosted and its quickstart requires Node 24+, Go 1.25+, Git, hardware virtualization (x86-64), and an OpenRouter key, with setup installing QEMU and building or downloading the Dot's images.
GitHub stars32,150Stars / 30 days+606npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed16Last commit4 days agoCommits / 12 weeks418Maintenance gradeATool descriptionsAScore 73.7: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars100
- npm downloadsnot measuredno npm package
- Used through Glama14
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum74 / 100 · weight 14%
- Stars gained, relative to size56
- Stars gained, absolute100
- 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
- 94.5
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 73.7
Best for: LinkedIn outreach and research through an authenticated browser session: it exposes 17 tools for profiles, companies, jobs, feed, inbox, messaging, and connection requests.
The server provides 17 tools for LinkedIn browser automation, covering person and company profiles, people and company search, job search and details, feed posts, inbox and conversation search, and actions such as connect_with_person and send_message. It assumes an authenticated LinkedIn browser session; connect_with_person is annotated with destructiveHint so clients prompt for confirmation, and send_message is a write operation when confirm_send is True.
GitHub stars3,895Stars / 30 days+386npm / typical weekShips no npm packagePyPI / typical week10.9Kmcp-server-linkedinTools exposed17Last commit2 days agoCommits / 12 weeks451Maintenance gradeATool descriptionsAScore 72.7: show every number behind it
- Adoption96 / 100 · weight 40%
- GitHub stars90
- PyPI downloads43PyPI 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
- Momentum87 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute100
- PyPI download trend49
- 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
- 93.2
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 72.7
Best for: Automating tasks in an already logged-in Chrome profile: it runs as a Chrome extension and reuses the browser's existing configuration and login state.
It is a Chrome extension-based MCP server that exposes Chrome browser functionality to AI assistants through a locally installed bridge, with Streamable HTTP and documented support for automation, content analysis, and semantic search. Before choosing it, expect to install mcp-chrome-bridge globally, enable Developer mode in Chrome, and load the extension unpacked.
GitHub stars12,488Stars / 30 days+64npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit285 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 71.9: 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
- Momentum47 / 100 · weight 14%
- Stars gained, relative to size29
- Stars gained, absolute73
- 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
- 71.9
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 71.9
Best for: Debugging BrowserStack test failures or running manual app/browser sessions from an MCP client: it exposes last-run failure, live session, test instructions, and accessibility scan tools.
The BrowserStack MCP server exposes five tools: runTestsOnBrowserStack, runAppLiveSession, runBrowserLiveSession, getFailuresInLastRun, and startAccessibilityScan. Before choosing it, note that its documented setup requires Node version 20.9 or later.
GitHub stars155Stars / 30 days+4npm / typical week15.2KPyPI / typical weekno attributed packageTools exposed5Last commit2 days agoCommits / 12 weeks341Maintenance 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
- Momentum47 / 100 · weight 14%
- Stars gained, relative to size49
- Stars gained, absolute29
- npm download trend66
- 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: Automating a Chrome session that already has logins and extensions: it connects to the running browser through a Chrome extension and exposes the Playwright API.
Playwriter documents a Chrome extension, a CLI, and a Node connectViaExtension helper for driving a running Chrome or Chromium browser through the Playwright API, and it names MCP as another interface. Its use requires the Playwriter Chrome extension and a running Chrome or Chromium browser, and its MCP tool list is unknown because the server has not been inspected.
GitHub stars4,010Stars / 30 days+126npm / typical weekdownloads not countedPyPI / typical weekno attributed packageTools exposednever inspectedLast commit11 days agoCommits / 12 weeks175Maintenance gradeATool descriptionsNot gradedScore 69.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
- Momentum77 / 100 · weight 14%
- Stars gained, relative to size72
- Stars gained, absolute85
- 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.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: Cleaning up tabs and researching in the user's own Firefox: tab and tab-group management, history search, and consent-gated page reading through a paired extension.
Browser Control MCP pairs an MCP server with a Firefox add-on so an LLM client can open, close, group and reorder tabs, search browsing history, read a page's text and links, find and highlight text, and capture a screenshot of a tab's visible area. It cannot modify pages, click or run scripts in them, and reading content or taking screenshots requires explicit per-domain or per-tab consent in Firefox, with a shared secret configured between the server and the extension.
GitHub stars334Stars / 30 days+13npm / typical weekdownloads not countedPyPI / typical weekno attributed packageTools exposednever inspectedLast commit56 days agoCommits / 12 weeks3Maintenance gradeCTool descriptionsNot gradedScore 68.1: show every number behind it
- Adoption63 / 100 · weight 40%
- GitHub stars63
- npm downloadsnot measurednpm names no repository for browser-control-mcp, so its downloads cannot be attributed
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance70 / 100 · weight 24%
- Last commit touching this server88
- Repository maintenance grade55
- Commit cadence40
- Momentum59 / 100 · weight 14%
- Stars gained, relative to size67
- Stars gained, absolute46
- 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
- 68.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 68.1
Best for: Recording Playwright actions into generated test code: it exposes codegen session tools alongside navigation, click, fill, and screenshot actions.
mcp-playwright exposes 32 tools for browser automation, covering navigation, screenshots, clicks, form filling, iframe interactions, JavaScript evaluation, console logs, HTTP requests, response assertions, history navigation, drag, key presses, PDF saving, and code generation session recording. The server ships as the npm package @executeautomation/playwright-mcp-server and installs browser binaries automatically on first use, with manual installation via npx playwright install also documented.
GitHub stars5,668Stars / 30 days+14npm / typical week17.2KPyPI / typical weekno attributed packageTools exposed32Last commit310 days agoCommits / 12 weeks0Maintenance gradeFTool descriptionsBScore 67.6: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars94
- npm downloads90
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance25 / 100 · weight 24%
- Last commit touching this server42
- Repository maintenance grade5
- Commit cadence5
- Momentum28 / 100 · weight 14%
- Stars gained, relative to size20
- Stars gained, absolute48
- npm download trend19
- 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
- 67.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 67.6
Best for: Sessions needing a logged-in Chrome profile: it drives a real Chrome browser over CDP and exposes worker and workflow tools for isolated parallel tabs.
OpenChrome ships as a Node CLI and MCP runtime that drives Chrome over CDP through 122 tools covering navigation, DOM and accessibility reads, form filling, screenshots, cookies, storage, network capture, and parallel worker orchestration. It requires Node.js 20 or newer plus a global npm install and an
openchrome setuprun before the MCP host is restarted, and its repository scope excludes desktop apps, browser extensions, native-host installers, and deployment templates.GitHub stars236Stars / 30 days-1npm / typical week228PyPI / typical weekno attributed packageTools exposed122Last commit25 days agoCommits / 12 weeks173Maintenance gradeATool descriptionsBScore 66.9: show every number behind it
- Adoption63 / 100 · weight 40%
- GitHub stars59
- npm downloads25downloads 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
- Momentum8 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend32
- 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
- 66.9
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 66.9
Questions people ask
Playwright MCP Server or Chrome DevTools MCP for a coding agent?
Playwright MCP Server is the one for structured page automation: it exposes 25 tools for navigation, clicks, typing, forms, snapshots and tabs, its tool description grade is B, and @playwright/mcp recorded 7,371,788 npm downloads in a typical week, though its last commit was 10 days ago and it recorded 33 commits in the last 12 weeks. Chrome DevTools MCP is aimed at inspecting and debugging a live Chrome browser, including console and network inspection and performance traces, and it looks busier with 1,674,540 npm downloads in a typical week, a commit 0 days ago and 380 commits in the last 12 weeks.
What do I need before SeleniumBase MCP will run?
It installs from PyPI as seleniumbase, which recorded 316,400 downloads in a typical week, and no npm package is published. It drives a persistent SeleniumBase CDP Mode browser and ships a solve_captcha tool for detectable CAPTCHAs, so plan for a real browser process rather than a plain HTTP client. It exposes 24 tools at grade A, had a commit 1 day ago, and recorded 288 commits on its default branch in the last 12 weeks.
Can I rely on Chrome MCP Server for a long project?
Be careful. It is labelled Abandoned but popular, its last commit was 285 days ago, and it recorded 0 commits on its default branch in the last 12 weeks, though it is not archived. If reusing a Chrome login is the requirement, huashu-chrome had a commit 6 days ago with 56 commits in the last 12 weeks, and playwriter had a commit 11 days ago with 175 commits in the last 12 weeks.
Which servers can drive a browser I am already logged into?
huashu-chrome reuses your Chrome login state for form filling, clicking, data fetching and captchas, with a commit 6 days ago and 56 commits in the last 12 weeks. playwriter connects to your running Chrome and keeps existing logins and extensions, with 175 commits in the last 12 weeks. Browser Control MCP pairs with a Firefox extension for tab management, history search and consent-gated page reading, but its last commit was 56 days ago and it recorded 3 commits in the last 12 weeks.
Does a higher tool count mean a better server?
Not on its own. OpenChrome exposes 122 tools at grade B, while SeleniumBase MCP exposes 24 tools at grade A and firefox-devtools-mcp exposes 35 at grade A. Playwright MCP Server exposes 25 at grade B and CloakBrowser MCP exposes 25 at grade B. Match the tool list to the workflow you need, then weigh the grade.
SeleniumBase MCP, Stealth Browser MCP or CloakBrowser MCP for anti-bot sites?
SeleniumBase MCP drives a persistent CDP Mode browser and ships a solve_captcha tool, exposes 24 tools at grade A, and had a commit 1 day ago with 288 commits in the last 12 weeks. Stealth Browser MCP drives a real Chrome-family browser via nodriver and CDP to get past Cloudflare, anti-bot checks and login walls, and had a commit 6 days ago with 31 commits in the last 12 weeks. CloakBrowser MCP forwards upstream Playwright MCP browser tools plus CloakBrowser binary and bridge information over multi-session Streamable HTTP, exposes 25 tools at grade B, and had a commit 0 days ago with 84 commits in the last 12 weeks.