OR install globally with `pip`: ```bash pip install computer-control-mcp ``` Then run the server with: ```bash computer-control-mcp # instead of uvx
Computer Control MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. OR install globally with pip: bash pip install computer-control-mcp Then run the server with: ```bash computer-control-mcp # instead of uvx computer-control-mcp, so you can use the latest version, also you can uv cache clean to.
The server ships on npm as mcp-caller, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 2 environment variables: COMPUTER_CONTROL_MCP_SCREENSHOT_DIR, COMPUTER_CONTROL_MCP_WGC_PATTERNS. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by AB498; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
{
"mcpServers": {
"computer-control-mcp": {
"command": "uvx",
"args": ["computer-control-mcp@latest"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| COMPUTER_CONTROL_MCP_SCREENSHOT_DIR | Filesystem location the server is allowed to use. | Optional |
| COMPUTER_CONTROL_MCP_WGC_PATTERNS | 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.