chrometools-mcp
by docentovich
Overview
MCP server for browser automation, web scraping, and UI testing using Puppeteer, enhanced with AI-powered element finding, page analysis, visual UI recording, and Figma design-to-code validation.
Installation
npx -y chrometools-mcpEnvironment Variables
- FIGMA_TOKEN
- ENABLED_TOOLS
- CHROMETOOLS_DEBUG
- DISPLAY
- CLAUDE_PROJECT_DIR
- PROJECT_DIR
Security Notes
The server includes an `executeScript` tool that uses `eval()` to execute arbitrary JavaScript code provided by the user (or AI agent) directly in the browser's context. Similarly, `new Function()` is used in `evaluateCustomCondition` within the recorder. This capability, while central to browser automation, represents a significant security risk if the input is not from a fully trusted source, potentially allowing for cross-site scripting (XSS), data exfiltration, or other malicious actions if the MCP client or its input is compromised. There are no obvious hardcoded secrets beyond configuration keywords, and API tokens are managed via environment variables.
Similar Servers
chrome-devtools-mcp
Control and inspect a live Chrome browser programmatically via an MCP server, enabling AI coding agents to perform reliable automation, in-depth debugging, and performance analysis.
mcp-server-browserbase
Enables LLMs to perform cloud browser automation tasks such as navigating, interacting with elements, extracting data, and capturing screenshots on web pages.
flowlens-mcp-server
Provides coding agents with full browser context from recorded user flows for debugging and regression testing.
blueprint-mcp
Enable AI assistants and coding agents to control and automate real web browsers (Chrome, Firefox, Opera) through a browser extension, maintaining logged-in sessions and avoiding bot detection.