Chrome Browser Automation
Rank #27305pulsemcp/chrome-browser-automation
Enables browser automation through Selenium WebDriver, allowing direct interaction with Chrome for web scraping, testing, and navigation tasks without requiring complex automation code.
Chrome Browser Automation is a Model Context Protocol (MCP) server published by qoxogus. It ranks #27305 of 58,832 servers tracked on MCP Toplist, and its repository has 2 GitHub stars. Chrome Browser Automation is listed on PulseMCP, and ships as a single rolling release with no explicit version metadata. It was first listed on Apr 11, 2025.
Ranks ahead of 31,527 of 58,832 servers on MCP Toplist.
Use Chrome Browser Automation
Chrome Browser Automation doesn’t publish a machine-readable install config. Follow the setup instructions in its repository ↗, or open one of its registry listings above.
Listed on 1 registry
qoxogus
Not versioned
This server is published through a registry that does not expose explicit version metadata. The listing tracks a single rolling release.
Frequently asked questions
- What is Chrome Browser Automation?
- Enables browser automation through Selenium WebDriver, allowing direct interaction with Chrome for web scraping, testing, and navigation tasks without requiring complex automation code.
- Who maintains Chrome Browser Automation?
- Chrome Browser Automation is maintained by qoxogus, which publishes 1 MCP server (0 total versions) tracked on MCP Toplist.
- Is Chrome Browser Automation an official MCP server?
- Chrome Browser Automation is not on the Official MCP Registry. It is listed on PulseMCP.
- How many versions does Chrome Browser Automation have?
- Chrome Browser Automation ships as a single rolling release with no explicit version metadata.
- Where can I find the source code for Chrome Browser Automation?
- The source code for Chrome Browser Automation is hosted at github.com/qoxogus/spring-ai-chrome-mcp-server.