19 Best Browser Automation MCP Servers, Compared (August 2026)
The short answer
For most readers, start with Chrome DevTools MCP. It is built to drive and inspect a live Chrome browser, including network-request monitoring, console inspection, and performance-trace analysis, and it has 49,454 stars, 1,882,510 downloads in a typical week, a commit 0 days ago, and 242 commits in the last 12 weeks. Choose Playwright MCP Server instead when you need exploratory automation from accessibility snapshots without a vision model; it exposes 24 tools and has 6,623,369 downloads 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
- 1Chrome DevTools MCP — AI coding assistants that must drive and inspect a live Chrome browser — it exposes network-request monitoring, console inspection, and performance-trace analysis.
- 2Playwright MCP Server — Exploratory automation and self-healing tests—it inspects pages via accessibility snapshots, no vision model required.
- 3browser-tools-mcp — Debugging a live app in your own logged-in Chrome session — it attaches via a DevTools extension and streams console, network, screenshots and Lighthouse audits.
- 4Stealth Browser MCP — Bypassing Cloudflare and anti-bot challenges in real Chrome instances — it exposes CDP-based tools for network inspection and element cloning.
- 5OpenChrome — Authenticated multi-site research in one real Chrome — it runs parallel lanes with existing logins and no re-auth.
Which one, for your situation
| Your situation | What to use |
|---|---|
| I need the default browser automation server for my agent. | Chrome DevTools MCP, because it is built for live Chrome control and inspection, has 49,454 stars, and had a commit 0 days ago with 242 commits in the last 12 weeks. |
| I need to automate pages using accessibility snapshots, no vision model. | Playwright MCP Server, because it is built for accessibility-snapshot automation without a vision model and has 24 tools, tool descriptions graded B, and 6,623,369 downloads in a typical week. |
| I need local Firefox testing and scraping. | firefox-devtools-mcp, because it is the Firefox option with 32 tools, tool descriptions graded B, a commit 0 days ago, and 85 commits in the last 12 weeks. |
| I need to automate my running Chrome with existing logins. | playwriter, because it connects to your running Chrome browser and preserves existing logins and extensions, with a commit 4 days ago and 144 commits in the last 12 weeks. |
| I need to get through Cloudflare and anti-bot walls. | Stealth Browser MCP, because its stated purpose is bypassing Cloudflare, antibots, and social media blocks in real Chrome instances. |
| I need browser automation where npm installs are not possible. | superpowers-chrome, because it is designed for environments that cannot run npm installs and exposes a single use_browser tool that controls Chrome via CDP. |
Top MCP servers for Browser Automation
| Best for | Profile | ||||||
|---|---|---|---|---|---|---|---|
| 1 | AI coding assistants that must drive and inspect a live Chrome browser — it exposes network-request monitoring, console inspection, and performance-trace analysis. | Community favourite | 49,454 | +2,111 | today | 93.5 | |
| 2 | Exploratory automation and self-healing tests—it inspects pages via accessibility snapshots, no vision model required. | Community favourite | 36,286 | +961 | yesterday | 90.9 | |
| 3 | Debugging a live app in your own logged-in Chrome session — it attaches via a DevTools extension and streams console, network, screenshots and Lighthouse audits. | Community favourite | 7,291 | +22 | 8 days ago | 84.6 | |
| 4 | Bypassing Cloudflare and anti-bot challenges in real Chrome instances — it exposes CDP-based tools for network inspection and element cloning. | Community favourite | 1,589 | +83 | 26 days ago | 84.1 | |
| 5 | Authenticated multi-site research in one real Chrome — it runs parallel lanes with existing logins and no re-auth. | Community favourite | 232 | +8 | 22 days ago | 79.9 | |
| 6 | Automating a user's already-open Chrome browser with existing login states — it connects via a Chrome extension rather than launching a separate browser. | Abandoned but popular | 12,293 | +187 | 226 days ago | 78.2 | |
| 7 | For browser automation in environments that cannot run npm installs — it exposes a single use_browser tool that controls Chrome via CDP and auto-captures pages. | Community favourite | 341 | +10 | 13 days ago | 77.6 | |
| 8 | Chrome-based browser automation from an agent runtime — it exposes MCP tools for tab management, navigation, CDP, action plans, and cleanup. | Community favourite | 231 | +33 | 43 days ago | 76.3 | |
| 9 | Managing AdsPower browser profiles and automating pages in them — it exposes profile lifecycle and in-page interaction tools. | Community favourite | 129 | +17 | 31 days ago | 73.8 | |
| 10 | Local Firefox testing and scraping — it provides snapshot/UID-based interactions and always-on network and console capture. | Community favourite | 365 | +54 | today | 72.6 | |
| 11 | Recruiters and job seekers with an active LinkedIn session — it offers 17 tools for profile, company, job, and inbox scraping. | Community favourite | 3,162 | +281 | 2 days ago | 71.3 | |
| 12 | For teams automating browser workflows and generating Playwright tests — it offers codegen sessions alongside navigation, click, fill, and screenshot tools. | Abandoned but popular | 5,633 | +24 | 250 days ago | 70.7 | |
| 13 | A user needing ready-made professional skills—offers many skills for browser automation. | Community favourite | 1,278 | +93 | today | 70.0 | |
| 14 | Teams on BrowserStack's Test Platform — all five tools route live sessions, test runs, and accessibility scans into BrowserStack's cloud instead of a local browser. | Community favourite | 150 | +6 | 3 days ago | 70.0 | |
| 15 | Users who want LLM-assisted tab management, history search, and content reading in their own Firefox browser — the paired extension requires consent for page reads. | Community favourite | 314 | +11 | 27 days ago | 69.0 | |
| 16 | An agent editing a browser video project live while a human watches — its patch_project applies targeted timeline-JSON edits without round-tripping the whole document. | Community favourite | 588 | +148 | 5 days ago | 67.4 | |
| 17 | Automating a browser you already use, with existing logins and extensions—it connects to your running Chrome instead of launching a fresh one. | Community favourite | 3,771 | +64 | 4 days ago | 67.1 | |
| 18 | AI-assisted Pine Script development and chart automation on TradingView Desktop—its CDP bridge exposes commands for scripting, navigation, alerts, and screenshots. | Community favourite | 5,639 | +853 | 23 days ago | 64.8 | |
| 19 | Automating authenticated web apps without API keys — it exposes 42 tools and talks to each site's internal APIs via a Chrome extension. | Community favourite | 897 | +34 | 23 days ago | 64.3 |
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.
- 1ChromeDevTools/chrome-devtools-mcp ↗
Chrome DevTools MCP
Community favouriteBest for: AI coding assistants that must drive and inspect a live Chrome browser — it exposes network-request monitoring, console inspection, and performance-trace analysis.
The server gives an MCP client control of a live Chrome browser, exposing automation, network-monitoring, console-debugging, and performance-analysis operations, plus a CLI for use without MCP. Only Google Chrome and Chrome for Testing are officially supported, so other Chromium-based browsers are not guaranteed to work.
GitHub stars49,454Stars / 30 days+2,111npm / typical week1.9MTools exposednever inspectedLast committodayCommits / 12 weeks242Maintenance gradeATool descriptionsNot gradedScore 93.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
- Momentum83 / 100 · weight 14%
- Stars gained, relative to size86
- Stars gained, absolute100
- npm download trend60
- 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
- 93.5
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 93.5
- 2microsoft/playwright-mcp ↗
Playwright MCP Server
Community favouriteBest for: Exploratory automation and self-healing tests—it inspects pages via accessibility snapshots, no vision model required.
This server exposes a broad toolset—navigation, clicking, typing, snapshots, network requests, and form filling—all driven by structured accessibility data rather than screenshots. Note its browser_run_code_unsafe tool executes arbitrary Playwright code in the server process, equivalent to remote code execution, so only attach it to trusted clients.
GitHub stars36,286Stars / 30 days+961npm / typical week6.6MTools exposed24Last commityesterdayCommits / 12 weeks22Maintenance gradeATool descriptionsBScore 90.9 — show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars100
- npm downloads100
- Used through Glama21
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum72 / 100 · weight 14%
- Stars gained, relative to size67
- Stars gained, absolute100
- npm download trend48
- 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
- 90.9
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 90.9
- 3AgentDeskAI/browser-tools-mcp ↗
browser-tools-mcp
Community favouriteBest for: Debugging a live app in your own logged-in Chrome session — it attaches via a DevTools extension and streams console, network, screenshots and Lighthouse audits.
The server connects to an existing Chrome session through a DevTools extension and exposes tools for console logs, network requests, screenshots, tab listing, browser storage, and Lighthouse audits. It requires Node 22.19 or newer, loading the extension unpacked from the repo, and keeping DevTools open on the tab to inspect.
GitHub stars7,291Stars / 30 days+22npm / typical weekShips no npm packageTools exposednever inspectedLast commit8 days agoCommits / 12 weeks23Maintenance gradeATool descriptionsNot gradedScore 84.6 — 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
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum35 / 100 · weight 14%
- Stars gained, relative to size22
- Stars gained, absolute55
- npm download trendnot measuredno npm download history
- 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
- 84.6
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 84.6
- 4vibheksoni/stealth-browser-mcp ↗
Stealth Browser MCP
Community favouriteBest for: Bypassing Cloudflare and anti-bot challenges in real Chrome instances — it exposes CDP-based tools for network inspection and element cloning.
The server runs a real Chrome-family browser via nodriver and CDP, exposing tools for navigation, element extraction, network inspection, and JavaScript execution. It requires a local Python 3.10+ environment with Chrome, Chromium, or Edge installed, and its tool surface is not measured at publication.
GitHub stars1,589Stars / 30 days+83npm / typical weekShips no npm packageTools exposednever inspectedLast commit26 days agoCommits / 12 weeks7Maintenance gradeATool descriptionsNot gradedScore 84.1 — show every number behind it
- Adoption80 / 100 · weight 40%
- GitHub stars80
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance93 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence65
- Momentum86 / 100 · weight 14%
- Stars gained, relative to size91
- Stars gained, absolute78
- npm download trendnot measuredno npm download history
- 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
- 84.1
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 84.1
- 5shaun0927/openchrome ↗
OpenChrome
Community favouriteBest for: Authenticated multi-site research in one real Chrome — it runs parallel lanes with existing logins and no re-auth.
OpenChrome drives a real, already-logged-in Chrome via CDP, exposing over one hundred tools for navigation, DOM queries, forms, network capture, workflows, and performance diagnostics, with a CLI and playbook runner on top. Before adopting it, know that it requires the agent host to launch and manage a dedicated Chrome instance (a normal Chrome without the remote-debugging port stays separate); installation is via npm (or optional standalone executables), and as a wrapper around Chrome it depends on Chrome being present.
GitHub stars232Stars / 30 days+8npm / typical week1.8KTools exposed100Last commit22 days agoCommits / 12 weeks254Maintenance gradeATool descriptionsBScore 79.9 — show every number behind it
- Adoption78 / 100 · weight 40%
- GitHub stars59
- npm downloads69
- 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
- Momentum48 / 100 · weight 14%
- Stars gained, relative to size61
- Stars gained, absolute39
- npm download trend34
- Tool quality68 / 100 · weight 13%
- Tool description quality60
- 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
- 79.9
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 79.9
- 6hangwin/mcp-chrome ↗
Chrome MCP Server
Abandoned but popularBest for: Automating a user's already-open Chrome browser with existing login states — it connects via a Chrome extension rather than launching a separate browser.
Chrome MCP Server is a Chrome-extension-based MCP server that gives AI assistants control of the user's existing Chrome browser and documents tools for screenshots, network monitoring, interactive operations, bookmark management, and browsing history. The main requirement before choosing it is manual setup: Node.js 20.0.0 or newer, Chrome/Chromium, a globally installed npm bridge, and an unpacked extension loaded from the repository's release download.
GitHub stars12,293Stars / 30 days+187npm / typical weekShips no npm packageTools exposednever inspectedLast commit226 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 78.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
- Maintenance46 / 100 · weight 24%
- Last commit touching this server68
- Repository maintenance grade30
- Commit cadence5
- Momentum67 / 100 · weight 14%
- Stars gained, relative to size50
- Stars gained, absolute92
- npm download trendnot measuredno npm download history
- 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.2
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 78.2
- 7obra/superpowers-chrome ↗
superpowers-chrome
Community favouriteBest for: For browser automation in environments that cannot run npm installs — it exposes a single use_browser tool that controls Chrome via CDP and auto-captures pages.
It exposes a single use_browser tool that drives a persistent Chrome browser via the Chrome DevTools Protocol, automatically capturing page state after each DOM action. Before choosing it, note that it requires Chrome to be installed and on Linux/WSL2 headed mode the MCP server needs the DISPLAY environment variable.
GitHub stars341Stars / 30 days+10npm / typical weekShips no npm packageTools exposed1Last commit13 days agoCommits / 12 weeks27Maintenance gradeATool descriptionsAScore 77.6 — show every number behind it
- Adoption63 / 100 · weight 40%
- GitHub stars63
- 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
- Momentum52 / 100 · weight 14%
- Stars gained, relative to size58
- Stars gained, absolute42
- npm download trendnot measuredno npm download history
- 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
- 77.6
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 77.6
- 8iFurySt/open-browser-use ↗
open_browser_use
Community favouriteBest for: Chrome-based browser automation from an agent runtime — it exposes MCP tools for tab management, navigation, CDP, action plans, and cleanup.
The README documents an MCP server that exposes browser tools for tab listing, opening, claiming, navigation, CDP, action plans, and cleanup. It requires installing a Chrome extension and native host through the open-browser-use CLI setup before use.
GitHub stars231Stars / 30 days+33npm / typical week182Tools exposednever inspectedLast commit43 days agoCommits / 12 weeks2Maintenance gradeATool descriptionsNot gradedScore 76.3 — show every number behind it
- Adoption66 / 100 · weight 40%
- GitHub stars59
- npm downloads48
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance88 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence40
- Momentum77 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute62
- npm download trend55
- 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
- 76.3
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 76.3
- 9AdsPower/adspower-browser ↗
AdsPower LocalAPI MCP Server
Community favouriteBest for: Managing AdsPower browser profiles and automating pages in them — it exposes profile lifecycle and in-page interaction tools.
It wraps AdsPower's LocalAPI, exposing 27 tools that create, open, close, update, and delete browser profiles, manage groups, and drive pages with navigation, clicking, filling, and script evaluation. The server requires a running AdsPower client (headless mode supported) and an API key/port; some APIs depend on the client version and may return 'Not found' if it is outdated.
GitHub stars129Stars / 30 days+17npm / typical week434Tools exposed27Last commit31 days agoCommits / 12 weeks26Maintenance gradeBTool descriptionsCScore 73.8 — show every number behind it
- Adoption64 / 100 · weight 40%
- GitHub stars53
- npm downloads56
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance92 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence85
- Momentum73 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute51
- npm download trend51
- Tool quality53 / 100 · weight 13%
- Tool description quality45
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integrates100
- Weighted mean of the five
- 73.8
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 73.8
- 10mozilla/firefox-devtools-mcp ↗
firefox-devtools-mcp
Community favouriteBest for: Local Firefox testing and scraping — it provides snapshot/UID-based interactions and always-on network and console capture.
It automates a local Firefox via WebDriver BiDi, with tools for navigation, snapshot/UID clicks and fills, network monitoring, console capture, screenshots, downloads, dialogs, and evaluate_script. Before choosing, note it requires a local Firefox installation (Node.js >= 20.19.0) and cannot run on cloud hosting.
GitHub stars365Stars / 30 days+54npm / typical week770Tools exposed32Last committodayCommits / 12 weeks85Maintenance gradeATool descriptionsBScore 72.6 — show every number behind it
- Adoption73 / 100 · weight 40%
- GitHub stars64
- npm downloads61
- 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
- Momentum75 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute70
- npm download trend35
- Tool quality68 / 100 · weight 13%
- Tool description quality60
- 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
- 72.6
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 72.6
- 11stickerdaniel/linkedin-mcp-server ↗
LinkedIn MCP Server
Community favouriteBest for: Recruiters and job seekers with an active LinkedIn session — it offers 17 tools for profile, company, job, and inbox scraping.
It automates a logged-in browser to scrape LinkedIn profiles, companies, jobs, and messages, exposing tools for search, retrieval, and even sending connection requests or messages. The server requires an active LinkedIn session in a local browser, and write operations like send_message trigger a confirmation prompt.
GitHub stars3,162Stars / 30 days+281npm / typical weekShips no npm packageTools exposed17Last commit2 days agoCommits / 12 weeks174Maintenance gradeATool descriptionsAScore 71.3 — show every number behind it
- Adoption88 / 100 · weight 40%
- GitHub stars88
- 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
- Momentum100 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute99
- npm download trendnot measuredno npm download history
- 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
- 91.4
- × relevance — the keyword is declared here
- 0.78
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 71.3
- 12executeautomation/mcp-playwright ↗
mcp-playwright
Abandoned but popularBest for: For teams automating browser workflows and generating Playwright tests — it offers codegen sessions alongside navigation, click, fill, and screenshot tools.
The server exposes 32 tools for browser control, including navigation, clicking, filling, screenshots, JavaScript evaluation, HTTP requests, and codegen sessions that record actions into test files. It assumes a Node.js runtime for installation via npm or npx, and automatically installs browser binaries on first use, so no separate Playwright setup is needed.
GitHub stars5,633Stars / 30 days+24npm / typical week20.1KTools exposed32Last commit250 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsBScore 70.7 — show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars94
- npm downloads92
- 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
- Momentum40 / 100 · weight 14%
- Stars gained, relative to size26
- Stars gained, absolute57
- npm download trend44
- 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.7
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 70.7
- 13mohitagw15856/pm-claude-skills ↗
pm-claude-skills-mcp
Community favouriteBest for: A user needing ready-made professional skills—offers many skills for browser automation.
The server exposes no browser automation tools; the unknown tool list, for Browser Automation; a source for Browser Automation is not here.
GitHub stars1,278Stars / 30 days+93npm / typical week1.4KTools exposednever inspectedLast committodayCommits / 12 weeks702Maintenance gradeATool descriptionsNot gradedScore 70.0 — show every number behind it
- Adoption88 / 100 · weight 40%
- GitHub stars78
- npm downloads67
- 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, absolute80
- npm download trend93
- 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
- 89.7
- × relevance — the keyword is declared here
- 0.78
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 70.0
- 14browserstack/mcp-server ↗
BrowserStack MCP server
Community favouriteBest for: Teams on BrowserStack's Test Platform — all five tools route live sessions, test runs, and accessibility scans into BrowserStack's cloud instead of a local browser.
Each of the five tools either starts a live app or website session on a chosen device or browser/OS combination, returns instructions for running test suites on BrowserStack, debugs the last run's failures when browserstack.yml is in the project root, or launches an accessibility scan for listed URLs. Before installing, know that every tool assumes BrowserStack's cloud infrastructure with no local fallback, and the README requires Node.js 18 or newer.
GitHub stars150Stars / 30 days+6npm / typical week8.1KTools exposed5Last commit3 days agoCommits / 12 weeks122Maintenance gradeBTool descriptionsBScore 70.0 — show every number behind it
- Adoption88 / 100 · weight 40%
- GitHub stars54
- npm downloads79downloads 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
- Momentum50 / 100 · weight 14%
- Stars gained, relative to size57
- Stars gained, absolute33
- npm download trend57
- 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.4
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — modest but real audience
- 0.85
- Composite score
- 70.0
- 15eyalzh/browser-control-mcp ↗
Browser Control MCP
Community favouriteBest for: Users who want LLM-assisted tab management, history search, and content reading in their own Firefox browser — the paired extension requires consent for page reads.
The README describes an MCP server paired with a Firefox extension, covering tab management, history search, and reading page text and links with user consent. It requires the Firefox extension and a shared-secret configuration, and the project labels itself experimental.
GitHub stars314Stars / 30 days+11npm / typical weekdownloads not countedTools exposednever inspectedLast commit27 days agoCommits / 12 weeks1Maintenance gradeCTool descriptionsNot gradedScore 69.0 — show every number behind it
- Adoption62 / 100 · weight 40%
- GitHub stars62
- 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
- Maintenance77 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade55
- Commit cadence40
- Momentum56 / 100 · weight 14%
- Stars gained, relative to size64
- Stars gained, absolute44
- npm download trendnot measuredno npm download history
- 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
- 69.0
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 69.0
- 16ronak-create/FableCut ↗
FableCut
Community favouriteBest for: An agent editing a browser video project live while a human watches — its patch_project applies targeted timeline-JSON edits without round-tripping the whole document.
FableCut runs a browser-based video editor and exposes seven MCP tools — status, docs, get project, patch project, set project, analyze reference, import media — with the timeline represented as one JSON document that can be hot-reloaded in the open UI. The one thing worth knowing before choosing it is that no npm package is published: deployment is a single
node server.js, and the browser UI is what hot-reloads the live timeline.GitHub stars588Stars / 30 days+148npm / typical weekShips no npm packageTools exposed7Last commit5 days agoCommits / 12 weeks118Maintenance gradeATool descriptionsAScore 67.4 — show every number behind it
- Adoption72 / 100 · weight 40%
- GitHub stars69
- npm downloadsnot measuredno npm package
- Used through Glama21
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum95 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute88
- npm download trendnot measuredno npm download history
- Tool quality85 / 100 · weight 13%
- Tool description quality77
- 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.4
- × relevance — the keyword is declared here
- 0.78
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 67.4
- 17remorses/playwriter ↗
playwriter
Community favouriteBest for: Automating a browser you already use, with existing logins and extensions—it connects to your running Chrome instead of launching a fresh one.
It attaches to a running Chrome browser through a companion extension and documents CLI commands for navigation, clicking, snapshots, screenshots, and debugging via the Playwright API. Before choosing it, note that it assumes the extension is installed in your browser and that the browser must already be running.
GitHub stars3,771Stars / 30 days+64npm / typical weekdownloads not countedTools exposednever inspectedLast commit4 days agoCommits / 12 weeks144Maintenance gradeATool descriptionsNot gradedScore 67.1 — show every number behind it
- Adoption89 / 100 · weight 40%
- GitHub stars89
- 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
- Momentum61 / 100 · weight 14%
- Stars gained, relative to size53
- Stars gained, absolute73
- npm download trendnot measuredno npm download history
- 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
- 86.0
- × relevance — the keyword is declared here
- 0.78
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 67.1
- 18tradesdontlie/tradingview-mcp ↗
TradingView MCP Bridge
Community favouriteBest for: AI-assisted Pine Script development and chart automation on TradingView Desktop—its CDP bridge exposes commands for scripting, navigation, alerts, and screenshots.
The server connects an AI assistant to a locally running TradingView Desktop via Chrome DevTools Protocol, exposing tools for Pine Script injection, chart navigation, drawing, alerts, replay, screenshots, and chart monitoring. Note that it requires a paid TradingView Desktop setup started with a debug flag, and it relies on TradingView's undocumented internal Electron structure that may break.
GitHub stars5,639Stars / 30 days+853npm / typical weekdownloads not countedTools exposednever inspectedLast commit23 days agoCommits / 12 weeks62Maintenance gradeBTool descriptionsNot gradedScore 64.8 — show every number behind it
- Adoption94 / 100 · weight 40%
- GitHub stars94
- npm downloadsnot measurednpm names no repository for tradingview-mcp, so its downloads cannot be attributed
- 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
- Momentum100 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute100
- npm download trendnot measuredno npm download history
- 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
- Trust0 / 100 · weight 9%
- License0
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 83.1
- × relevance — the keyword is declared here
- 0.78
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 64.8
- 19opentabs-dev/opentabs ↗
OpenTabs
Community favouriteBest for: Automating authenticated web apps without API keys — it exposes 42 tools and talks to each site's internal APIs via a Chrome extension.
OpenTabs runs a local MCP server bridged to Chrome by an extension, exposing tools for tab control, clicking, typing, network capture, and storage access, with plugins for services like Slack, Discord, and GitHub. Before choosing it, know that all 42 tools ship disabled and must be explicitly enabled, and that it requires Node.js 22+ and Chrome.
GitHub stars897Stars / 30 days+34npm / typical weekShips no npm packageTools exposed42Last commit23 days agoCommits / 12 weeks96Maintenance gradeATool descriptionsAScore 64.3 — 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
- Momentum69 / 100 · weight 14%
- Stars gained, relative to size74
- Stars gained, absolute62
- npm download trendnot measuredno npm download history
- Tool quality78 / 100 · weight 13%
- Tool description quality70
- 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.4
- × relevance — the keyword is declared here
- 0.78
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 64.3
Questions people ask
Chrome DevTools MCP or Playwright MCP Server: which should I install?
Chrome DevTools MCP is the better choice when you need to drive and inspect a live Chrome browser: it is built for network-request monitoring, console inspection, and performance-trace analysis, and it had a commit 0 days ago with 242 commits in the last 12 weeks. Playwright MCP Server is the better choice when you want accessibility-snapshot automation without a vision model, and it has 6,623,369 downloads in a typical week versus Chrome DevTools MCP's 1,882,510. If you only have time to install one and your task is general Chrome automation, Chrome DevTools MCP is the safer active default.
Which server works with my existing Chrome logins?
playwriter connects to your running Chrome browser and keeps existing logins and extensions; it had a commit 4 days ago and 144 commits in the last 12 weeks. Chrome MCP Server also uses existing login states through a Chrome extension, but it has had 0 commits in the last 12 weeks and its last commit was 226 days ago. browser-tools-mcp is the alternative if your goal is debugging a logged-in session: it attaches via a DevTools extension and streams console, network, screenshots, and Lighthouse audits.
I need Firefox automation. Which MCP server should I use?
firefox-devtools-mcp is the Firefox option with the strongest measured activity: 32 tools, tool descriptions graded B, a commit 0 days ago, and 85 commits in the last 12 weeks. It is built for testing, scraping, and browser control via WebDriver BiDi, with snapshot/UID-based interactions, network monitoring, console capture, and screenshots. Browser Control MCP also targets Firefox, but it is for tab management, history search, and content reading through a paired extension, not general test automation.
What's the difference between mcp-playwright and Playwright MCP Server?
Playwright MCP Server (microsoft/playwright-mcp) is the active one: it had a commit 1 day ago, 22 commits in the last 12 weeks, 24 tools, and tool descriptions graded B. mcp-playwright (executeautomation/mcp-playwright) exposes 32 tools with the same B grade, but it is labelled 'Abandoned but popular' and had a commit 250 days ago with 0 commits in the last 12 weeks. If you need Playwright automation that is still being worked on, choose Playwright MCP Server; if you specifically want its codegen sessions, mcp-playwright is the one that offers them.
What do I need before BrowserStack MCP server will run?
BrowserStack MCP server only makes sense if you are on BrowserStack's Test Platform; its five tools route live sessions, test runs, and accessibility scans into BrowserStack's cloud rather than automating a local browser. It exposes 5 tools and had a commit 3 days ago with 122 commits in the last 12 weeks, so the project itself is active.
What should I be careful about when pointing an agent at my authenticated browser?
Several servers are built to use your existing logged-in session. playwriter connects to your running Chrome and keeps existing logins and extensions; OpenTabs works through your authenticated browser session via a Chrome extension; Chrome MCP Server leverages existing login states. That means the agent can operate in places where you are already signed in, so keep that in mind when choosing what to ask it to do. For local debugging, browser-tools-mcp attaches to your logged-in Chrome via a DevTools extension and can stream console, network, screenshots, and Lighthouse audits from that session.