Why it’s hereMost popular in this category on AllMCPs
Chrome DevTools for coding agents
The best MCP servers for browser automation — drive a real browser from an AI agent to navigate, click, fill forms, and extract page content.
Why it’s hereMost popular in this category on AllMCPs
Chrome DevTools for coding agents
Why it’s hereOfficial server
Official Microsoft Playwright MCP server, enabling LLMs to interact with web pages through structured accessibility snapshots
Why it’s hereCommunity pick
Browser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
Why it’s hereCommunity pick
Browser automation capabilities using Puppeteer, both support local and remote browser connection.
Why it’s hereCommunity pick
An MCP server using Playwright for browser automation and webscrapping
Why it’s hereCommunity pick
The Open-Source Multimodal AI Agent Stack: Connecting Cutting-Edge AI Models and Agent Infra
Why it’s hereCommunity pick
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
Why it’s hereCommunity pick
A Model Context Protocol (MCP) server for interacting with iOS simulators. This server allows you to interact with iOS simulators by getting information about them, controlling UI interactions, and inspecting UI elements.
Why it’s hereCommunity pick
BrowserStack's Official MCP Server
Why it’s hereCommunity pick
MCP server for browser and desktop automation: OCR, image recognition, real mouse and keyboard input
Microsoft's official playwright-mcp is the most widely used starting point — it exposes Playwright's accessibility-tree snapshot to the agent instead of raw screenshots, which tends to make click/fill actions more reliable than vision-based automation.
Run browser automation servers headless by default; switch to a headed/visible browser only when you're debugging a flow that isn't working, since watching the browser act is the fastest way to see where a selector or step is failing.
If a workflow needs to log into a site, use a scoped or disposable test account wherever the site supports one — an agent driving a real browser session has the same access a logged-in human would.
Servers wrapping Playwright, Puppeteer, and browser-use are the most installed. This page ranks browser automation servers by real usage.
Most support both headless and headed modes. Headless is typical for servers and CI; headed is useful for debugging or when a site needs a visible session.
Yes, if you provide credentials — but treat that access carefully and prefer scoped or throwaway accounts for automation.