openchrome and chrome-local-mcp
The two tools are competitors, as both aim to provide a Multi-Control Protocol (MCP) server for automating Chrome, but they differ in their approach and intended use-case: `shaun0927/openchrome` focuses on controlling a "real Chrome" instance for AI agents, implying a more general and potentially distributed automation solution, while `callmehuyv/chrome-local-mcp` specifically targets local Chrome automation for "Claude Code" powered by Puppeteer, suggesting a more specialized and constrained local development environment.
About openchrome
shaun0927/openchrome
Open-source browser automation MCP server. Control your real Chrome from any AI agent.
This project helps anyone who uses AI agents to automate web tasks, like gathering information or interacting with websites. It allows an AI to control a real Chrome browser, inputting requests and receiving structured data or task completion confirmations. This is designed for AI developers or data scientists building automated web scraping, data collection, or testing workflows.
About chrome-local-mcp
callmehuyv/chrome-local-mcp
A local Chrome browser automation MCP server for Claude Code, powered by Puppeteer
This tool helps you automate repetitive web tasks by giving Claude Code direct control over a real Chrome browser. You can instruct Claude Code in plain language to navigate websites, fill out forms, click buttons, extract text, and take screenshots. This is ideal for anyone who uses Claude Code and needs to interact with web pages to gather information or perform actions without manual intervention.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work