Skip to main content
Glama
Chrome MCP Control Center

Chrome MCP Control Center

by firyomaefx

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 desktop

End-user install: see INSTALLATION.md.
Pairing: LLM_PAIRING.md.
Architecture: docs/ARCHITECTURE.md.
Living status: CONTEXT.md.

Vertical slice

  1. Open Control Center → Start All

  2. Extension connects via Native Messaging

  3. Pair Grok CLI

  4. browser_list_tabs → browser_read_page → approve → browser_click

  5. Emergency Stop blocks next action

  6. 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.ts

Installers (from next pack):

  • ChromeMCP-ControlCenter_1.0.4_win-x64_Setup.exe

  • ChromeMCP-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 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

Available Tools

3 tools
browser_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

    C2.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct action: waiting for a selector, clicking coordinates, and typing text. There is no overlap between their purposes.

    Naming Consistency4/5

    All tool names use snake_case, but the prefix differs ('browser_' vs 'computer_'). This minor inconsistency does not hinder readability.

    Tool Count3/5

    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.

    Completeness2/5

    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

    ActivityNo data
    ResponsivenessSyncing

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      An 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Gives coding agents full control over a real Chrome browser, enabling navigation, clicking, typing, screenshotting, and more via an MCP server and Chrome extension.
      17 npm
      2
      MIT