Control a Chrome browser through the Chrome DevTools Protocol (CDP) from MCP clients for browsing, inspection, and automation workflows.
Control a Chrome browser through the Chrome DevTools Protocol (CDP) from MCP clients for browsing, inspection, and automation workflows.
A Model Context Protocol (MCP) server that provides fine-grained control over a Chrome browser instance through the Chrome DevTools Protocol (CDP).
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| navigate | |
| click | Parameters: - x (number): X coordinate - y (number): Y coordinate |
| type | |
| clickElement | Parameters: - selector (string): Element index (e.g., "0" for the first element) |
| getText | Parameters: - selector (string): CSS selector to find the element |
| getPageInfo | Get semantic information about the page including interactive elements and text nodes. |
| getPageState | Get current page state including URL, title, scroll position, and viewport size. |
{
"mcpServers": {
"chrome-control": {
"url": "http://localhost:3000/sse",
"disabled": false,
"alwaysAllow": []
}
}
}Configuration as documented by the project. Restart the client after saving.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.
The configuration file will be generated at `/Users/username/.moling/config/config.json`, and you can modify its contents as needed.
MCP server that integrates with FE development server for Cursor
Token-efficient browser agent for local LLMs. Playwright + accessibility tree + MarkGrab.