Control a Chrome browser through the Chrome DevTools Protocol (CDP) from MCP clients for browsing, inspection, and automation workflows.
If you want an AI assistant working directly with Chrome, the chrome mcp server is the bridge. 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).
Once connected, the assistant can call these 7 tools directly:
navigate — The navigate tool exposed by this serverclick — Parameters: - x (number): X coordinate - y (number): Y coordinatetype — The type tool exposed by this serverclickElement — Parameters: - selector (string): Element index (e.g., "0" for the first element)getText — Parameters: - selector (string): CSS selector to find the elementgetPageInfo — Get semantic information about the page including interactive elements and text nodesgetPageState — Get current page state including URL, title, scroll position, and viewport sizeThe server is distributed via npm as bun, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
| Tool | What it does |
|---|---|
| navigate | The navigate tool exposed by this server. |
| click | Parameters: - x (number): X coordinate - y (number): Y coordinate |
| type | The type tool exposed by this server. |
| 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.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.