Chrome MCP Control Center
Enables safe automation of Chrome browser through a local MCP server and Chrome extension, allowing LLMs to control browser tabs, pages, and computer-use actions with permission controls.
README
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
Quick start (developers)
npm install
npm run build
npm test
npm run desktop
End-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_click- Emergency 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.
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 now
See 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:export
Runs automatically after npm run build and npm run desktop:pack. Secrets and private logs are excluded.
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.