$ loading_
Automate browsing, form filling, login, and page interactions through a Chrome MCP server.
This tool claims to provide Chrome-based browser automation and does not require secrets or declare remote endpoints; the main concerns are local browser-process execution and access to web/browser-session data. Its open-source repository improves auditability, but the third-party registry source, missing README, low adoption, and unknown maintenance warrant caution.
The materials explicitly state there are no required keys or environment variables, and no API keys, tokens, or external service credentials are requested. However, because it supports website login and form filling, it may handle user-entered site credentials during use, which should be controlled by the user.
No fixed remote endpoint is declared, and the materials do not indicate data is sent to a developer-controlled server. However, browser automation inherently connects to user-directed websites and may submit forms or login data to target pages, which is a normal network behavior for this type of tool.
The system flags executes-code, and the description indicates navigation, element manipulation, and login via a Chrome-based MCP server, implying it launches and/or controls a local browser process to perform automation. This is standard execution capability for an MCP tool, and the materials do not show requests for system privileges beyond its stated function.
By function, it can access browser page content, form fields, session state, and data from websites opened during automation. If it reuses the local Chrome profile, it may also indirectly access cookies or existing login state. The materials do not specify local file read/write scope and show no obvious overbroad authorization request, but the data exposure surface should be considered broad.
A positive factor is that there is an open-source repository, allowing code review. However, it comes from a third-party registry, has no declared license, no README, 0 stars, and unknown maintenance status, so overall trust is limited. There are not enough concrete red flags to rate it as high risk, but its supply-chain maturity is weak.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcp-chrome-server" yet — see the docs or source repo.
Use Chrome MCP to open the target website, complete the login flow (if a CAPTCHA appears, ask me to handle it), go to the signup page, automatically fill in the name, email, and phone number, submit the form after validation, and return the execution result.
An execution log showing login and form submission steps, including the final status.
Use Chrome MCP to visit this list of page URLs one by one, extract the title, price, and main description from each page, and compile them into a structured list. If a page fails to load, record the reason and continue to the next one.
A structured result with extracted fields and error records for further analysis.
Use Chrome MCP to test the website checkout flow: open the homepage, search for a product, add it to the cart, and go to the checkout page. Verify that key buttons and texts exist at each step, then output the test results with notes on failed screenshots.
A page flow test report describing passed checks, failed checks, and supporting page evidence.
Control your signed-in Chrome browser for web automation and screenshots via MCP.
Control Chrome and automate multi-session browsing through MCP clients.
Automate browser tasks, capture console logs, and take screenshots for web workflows.
Automate Chrome with Playwright for web actions, testing, and data collection.
Control a real Chrome browser for browsing, interaction, and page reading.
Automate Chromium for web actions, debugging, and browser testing tasks.