Dazzle CLI — cloud stages for AI agents and live streaming
412 servers · 412 listings
Real-browser automation based on Patchright with ad blocking.
Eval-backed tool discovery for AI agents on the auxiliar.ai web-access gateway. recommend_tools picks the best search, scraping
MCP server for Chrome browser control via CDP - 通过 MCP 协议控制 Chrome 浏览器
MCP server that audits the images on any web page — natural vs rendered dimensions, oversized-image detection, and format breakdown
Model Context Protocol (MCP) server for controlling Google Chrome browser on macOS. Enables AI assistants like Claude to automate Chrome
MCP server that gives AI agents Unix-style filesystem commands (ls, cd, grep, click, type) to drive Chrome. Single-tool interface
MCP server that lets an MCP client (Claude Code, Codex, any MCP client) drive a real, logged-in Chrome profile. Ships the MonkeySee Chrome
MCP server for SnapRender Screenshot API — lets AI agents capture website screenshots
Give your AI real senses — hear, see, and feel any web app in real time. Audio, visuals, performance, network, security, and console
MCP server that scans web pages for WCAG accessibility issues with axe-core, so AI agents can audit and fix accessibility. By
ADA MCP server for web/mobile automation (stdio + remote HTTP)
MCP server integrating with Vercel's agent-browser for AI-driven browser automation
MCP server wrapper for the local agent-browser CLI with Codex bootstrap support.
MCP stdio bridge for controlling your own Chrome browser with AI agents
Token-efficient browser automation MCP for AI agents — semantic page snapshots and stable element IDs.
Lets AI assistants interact with the user's local browsers.
MCP server that connects to your browser for real-time DOM, CSS, layout inspection, screenshot capture, and Figma design comparison — your
Headless browser primitives for AI agents when sites need real JS rendering.
MCP server that uses Puppeteer to monitor and control a Chrome dev instance.
Model Context Protocol server for 3DStreet — drive an open 3DStreet tab from Claude Desktop or Claude Code.
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.