Chrome MCP Control Center
Click on "Install 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 Centerlist 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
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceAn 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
- Alicense-quality-maintenanceAn 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.
- Alicense-qualityCmaintenanceEnables AI agents to control Chrome browser actions like navigation, clicking, form filling, screenshots, and console/network logging via an MCP server and Chrome extension.1,001MIT
- Alicense-qualityCmaintenanceGives coding agents full control over a real Chrome browser, enabling navigation, clicking, typing, screenshotting, and more via an MCP server and Chrome extension.112MIT
Related MCP Connectors
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Live browser debugging for AI assistants — DOM, console, network via MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/firyomaefx/chrome-mcp-control-center'
If you have feedback or need assistance with the MCP directory API, please join our Discord server