browser-mcp
Related Servers
Alternatives to browser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceAn extension-based MCP server that enables AI assistants to control your existing Chrome browser, leveraging your active login states and settings for automation. It provides over 20 tools for tasks like semantic tab search, screen capture, network monitoring, and direct element interaction.-
- AlicenseAqualityAmaintenanceLocal MCP server and Chrome/Edge extension that let AI assistants use your existing signed-in browser sessions on Reddit and Zhihu. Provides 54 site operations through three stable MCP tools, with on-demand operation discovery, compact structured results, and pagination; requires Node.js 22+ and the companion extension on the same computer.31MIT
- AlicenseNot gradedqualityDmaintenanceAn extension-based MCP server that enables AI assistants to control your browser, leveraging existing sessions and login states for automation and content analysis. It provides over 20 tools for semantic tab search, interactive element manipulation, and network monitoring directly within your daily Chrome environment.MIT
- AlicenseAqualityDmaintenanceMCP server that lets AI assistants browse the web through your real Chrome with your cookies, sessions, and fingerprint, avoiding bot detection and CAPTCHAs. Enables web browsing, content extraction, and multi-step workflows via persistent tabs.151 npm3MIT
- AlicenseBqualityCmaintenanceTurns Chrome into a local MCP server, giving AI agents 51 browser tools to inspect DOM, automate clicks, run JavaScript, audit security and accessibility, mock APIs, extract data, record demos, and more from any MCP client.92671 npmMIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server lets AI agents read and extract data from your own logged-in Chrome browser via the HoloScrape extension, enabling private, local automation of web scraping and list extraction without uploading data.3 npmMIT
TDQS
Scored across 24 tools
Most tools are cleanly separated by domain prefix and action (e.g., browser_*, zhihu_*, xhs_*), making them easy to distinguish. However, browser_read and browser_snapshot both load URLs with different output types, and browser_read_page vs site_read_page could initially cause confusion.
All tool names use lowercase_with_underscores and a clear domain prefix, which is very consistent. The pattern is not always verb_noun (e.g., browser_status, zhihu_invitations), mixing action and noun forms, but the prefix-based scheme makes the set predictable.
With 24 tools, this server is on the heavy side, though the breadth of domains (browser control, platform-specific reads for five sites, and three search engines) argues for a larger surface. Some consolidation could reduce the count, but most tools earn their place.
The server covers the core browser lifecycle (load, view, click, type, scroll, select, press) plus a solid set of reads for major platforms and search engines. Missing advanced interactions like hover or multi-step workflows, but no obvious dead ends for the stated purpose.