How does Browser Control differ from DOM-based tools?
It uses vision-first interaction based on page screenshots, avoiding fragile DOM queries. This reduces tokens per action by 50–100× and eliminates brittle selector inference.

@adityasasidhar
Basic information
Category
Browser Automation
Last updated
Transports
stdio
Author
adityasasidhar
Submitted by
Aditya Sasidhar
Stop feeding your agent raw HTML. BrowserControl gives LLMs true visual grounding with Set of Marks (SoM), letting them click exactly what they see without hallucinating selectors. With built-in developer tools, session recording, and persistent logins, it transforms web automati
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"browsercontrol": {
"command": "python",
"args": [
"-m",
"browsercontrol"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Browser Control is a production-ready MCP server that gives AI agents real browser capabilities using vision-first interaction. It controls Chromium through Playwright, providing screenshots with numbered interactive elements, persistent sessions, and built-in developer tooling—all locally without external vision APIs.
Install Python 3.11+ and Playwright (Chromium installed automatically). Add Browser Control as an MCP server in your AI agent’s client. Agents then call tools like click(5) or type_text(3, "hello") to interact with web pages.
It uses vision-first interaction based on page screenshots, avoiding fragile DOM queries. This reduces tokens per action by 50–100× and eliminates brittle selector inference.
Python 3.11+, FastMCP, and Playwright (auto-installs Chromium). All execution is local—no external AI or API calls.
All data, including cookies, localStorage, and recording traces, is stored locally on the machine running the MCP server.
It uses the MCP (Model Context Protocol) transport, designed for integration with AI agent clients. No authentication details are specified in the documentation.
Browser Control is stable, actively developed, and MIT licensed. No specific limits are documented beyond requiring a local Chromium installation.
Official MCP server of the Scrapling web scraping framework: HTTP requests, stealthy browser, screenshots and network inspection for AI agents.
MCP server for fetch web page content using Playwright headless browser.

MCP server for managing Gologin browser profiles, proxies, fingerprints and cloud browser sessions through AI conversations
🔮 Platform-neutral Browser Use for AI agents: real Chrome automation with a CLI + SDKs, no lock-in, dead simple.

Web scraping and fetch API for AI agents: retrieve any public URL live as clean Markdown or HTML, with geo-targeting per request (choose the country) for localized search results and prices, plus optional JavaScript rend
Comments