A Chrome server based on MCP (Model-Controller-Prompt) for browser automation.
Mcp chrome server mcp server lets Claude, Cursor and other MCP clients work with MCP Chrome Server directly. A Chrome server based on MCP (Model-Controller-Prompt) for browser automation.
A Chrome server based on MCP (Model-Controller-Prompt) for browser automation.
Once connected, the assistant can call these 4 tools directly:
Windows — %LOCALAPPDATA%\Google\Chrome\User DatamacOS — ~/Library/Application Support/Google/ChromeLinux — ~/.config/google-chromePrerequisites — The Prerequisites tool exposed by this serverThe server is distributed via npm as @smithery/cli, 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.
The server reads one environment variable: CHROME_PROFILE_PATH. Keep credentials in your client's env block or a secrets manager rather than committing them.
Browser automation servers are the ones people reach for when a site has no API — the assistant drives a real page instead of guessing at endpoints. MCP Chrome Server sits in that group, and the shape of its toolset — Windows, macOS, Linux among others — tells you what it is really for. Worth comparing against the other browser automation servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Windows | %LOCALAPPDATA%\Google\Chrome\User Data |
| macOS | ~/Library/Application Support/Google/Chrome |
| Linux | ~/.config/google-chrome |
| Prerequisites | The Prerequisites tool exposed by this server. |
**macOS Setup:**
```json
{
"mcpServers": {
"mcp-chrome-server": {
"command": "uv",
"args": [
"run",
"--directory",
"/usr/local/bin/mcp-chrome-server/src",
"mcp-chrome-server"
],
"env": {
"CHROME_PROFILE_PATH": "$HOME/Library/Application Support/Google/Chrome"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CHROME_PROFILE_PATH | Filesystem location the server is allowed to use. | 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.