A protocol that enables AI models to control Chrome browser and perform web automation.
MCP Chrome Integration MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Chrome Integration directly instead of describing what you should do. A protocol that enables AI models to control Chrome browser and perform web automation.
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once MCP Chrome Integration is connected, these are the calls the assistant has available:
Prerequisites — The Prerequisites tool exposed by this serverYou will need one environment variable: WEBSOCKET_PORT. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Chrome Integration's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by dlwjdtn535; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
**macOS Setup:**
```json
{
"mcpServers": {
"mcp-chrome-integration": {
"command": "uv",
"args": [
"run",
"--directory",
"/usr/local/bin/mcp-chrome-integration/src",
"mcp-server"
],
"env": {
"WEBSOCKET_PORT": "8012"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| WEBSOCKET_PORT | Configuration value read at startup. | Optional |
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.