Browser Automation MCP Servers

Driving a real browser — clicks, forms, screenshots, whole sessions. 412 Browser Automation MCP servers on Mcprush.

412 servers · 412 listings

Ranked by readers of the listing, not by downloads
Browser Automation

Eval-backed tool discovery for AI agents on the auxiliar.ai web-access gateway. recommend_tools picks the best search, scraping

4 tools
from $14/mo

MCP server that audits the images on any web page — natural vs rendered dimensions, oversized-image detection, and format breakdown

1 tool
from $14/mo

Model Context Protocol (MCP) server for controlling Google Chrome browser on macOS. Enables AI assistants like Claude to automate Chrome

15 tools
from $19/mo

MCP server that gives AI agents Unix-style filesystem commands (ls, cd, grep, click, type) to drive Chrome. Single-tool interface

39 tools
from $19/mo

MCP server that lets an MCP client (Claude Code, Codex, any MCP client) drive a real, logged-in Chrome profile. Ships the MonkeySee Chrome

24 tools
from $15/mo

Give your AI real senses — hear, see, and feel any web app in real time. Audio, visuals, performance, network, security, and console

4 tools
from $25/mo

MCP server that connects to your browser for real-time DOM, CSS, layout inspection, screenshot capture, and Figma design comparison — your

Free

Browser Automation MCP servers on mcprush, filed under one heading so the shelf can be read in one pass.

Every server here names the publisher behind it and whether that publisher has been verified, the runtime it uses, how it authenticates, the tool surface it exposes and the price model it is sold under — and where a security scan has been run against it, what the scan found. The filters on the left narrow it further and the sort at the top decides what comes first.

A server that runs on its publisher’s infrastructure is reached through the mcprush gateway, so one key covers everything installed against your account, the calls are metered where you can see them and the ceiling on what they may cost is yours to set. Installing one is a line of the mcprush CLI — npx mcprush@latest add, followed by the server’s id — and a --client flag writes another client’s config instead of the default one. A server that runs on your own machine carries its publisher’s own instructions instead, and the listing says which of the two it is before you install anything.

Compare
tick one more
Side-by-side