Chrome MCP Control Center
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Chrome MCP Control Center list my open tabs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Chrome MCP Control Center
Single-click Windows Chrome Computer-Use MCP for non-technical users.
Install one app → open one desktop shortcut → complete a short wizard → click Start All → pair your LLM → automate Chrome safely.
Features (MVP)
Control Center desktop app (Start All / Stop All / Emergency Stop)
Local MCP server (stdio + optional loopback HTTP)
Chrome extension (Manifest V3) + Native Messaging
DOM-first browser tools; computer-use fallback (guarded)
Permission engine (read-only → reversible → commitment; L3 blocked)
LLM pairing for Grok CLI, Claude, Codex, generic MCP clients
Health check, Repair, audit logs with redaction
Related MCP server: Chrome MCP Server
Quick start (developers)
npm install
npm run build
npm test
npm run desktopEnd-user install: see INSTALLATION.md.
Pairing: LLM_PAIRING.md.
Architecture: docs/ARCHITECTURE.md.
Living status: CONTEXT.md.
Vertical slice
Open Control Center → Start All
Extension connects via Native Messaging
Pair Grok CLI
browser_list_tabs→browser_read_page→ approve →browser_clickEmergency Stop blocks next action
Stop All clean shutdown
Security
See SECURITY.md and THREAT_MODEL.md.
Webpage content is untrusted. Passwords and payment data never return to the LLM.
Versioning
SemVer MAJOR.MINOR.PATCH. One number everywhere (app, extension, installers, GitHub tag).
npm run version:patch # or version:minor / version:major
npm run version:sync # sync desktop, extension, VERSION, src/version.tsInstallers (from next pack):
ChromeMCP-ControlCenter_1.0.4_win-x64_Setup.exeChromeMCP-ControlCenter_1.0.4_win-x64_Portable.exe
Details: docs/VERSIONING.md.
Cloud improvement sync
Free and Paid both sync operational telemetry to the owner backend (after consent). Free is not local-only for diagnostics. Secrets are never uploaded.
npm run cloud:backend # owner ingest + dashboard :8788
# Control Center → Cloud & Privacy → Accept agreement → Sync nowSee docs/CLOUD_SYNC.md.
Obsidian knowledge base
Docs sync into the TTRG vault under 10-Projects/chrome-mcp-control-center/ (wikilinks, redacted).
npm run obsidian:exportRuns automatically after npm run build and npm run desktop:pack. Secrets and private logs are excluded.
License
MIT
Available Tools
3 toolsbrowser_wait_forC
Wait for a selector or timeout
Inputs: tabId, selector, timeoutMs.
computer_clickC
Click screen coordinates (high caution)
Inputs: x (required), y (required), url, tabId, +1 more.
computer_typeC
Type via OS keyboard (high caution)
Inputs: text (required), url, tabId, confirmed.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool targets a distinct action: waiting for a selector, clicking coordinates, and typing text. There is no overlap between their purposes.
All tool names use snake_case, but the prefix differs ('browser_' vs 'computer_'). This minor inconsistency does not hinder readability.
With only 3 tools, the server feels thin for a 'Chrome MCP Control Center'. It may be acceptable if the scope is intentionally narrow, but more tools are expected.
The tool set misses essential browser operations like navigation, page evaluation, or screenshot. For a control center, this leaves significant gaps that agents cannot work around.
Maintenance
Related MCP Connectors
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Control a real browser from AI agents: navigate, click, type, screenshot, read the page.
Web scraping, browser automation, screenshots and AI data extraction for AI agents via MCP.
Browz hosted MCP (free public beta): let an AI app drive your own Browz browser profiles from anywhere. Connect https://mcp.gobrowz.com/mcp and sign in with your Browz account (OAuth) or an agent token. Each call is relayed to the Browz app on your computer, which must be online with Remote control on and have a hardware security chip (Mac Secure Enclave or TPM 2.0). 17 tools: profiles, tabs, navigate, snapshot, act, wait, screenshot. Cookies, downloads and stored sign-ins stay on your computer.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn extension-based MCP server that enables AI assistants to control your browser, leveraging existing sessions and login states for automation and content analysis. It provides over 20 tools for semantic tab search, interactive element manipulation, and network monitoring directly within your daily Chrome environment.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceAn extension-based MCP server that enables AI assistants to control your existing Chrome browser, leveraging your active login states and settings for automation. It provides over 20 tools for tasks like semantic tab search, screen capture, network monitoring, and direct element interaction.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control Chrome browser actions like navigation, clicking, form filling, screenshots, and console/network logging via an MCP server and Chrome extension.MIT
- AlicenseNot gradedqualityDmaintenanceGives coding agents full control over a real Chrome browser, enabling navigation, clicking, typing, screenshotting, and more via an MCP server and Chrome extension.17 npm2MIT