Chrome MCP Server (mcp-chrome)
A Chrome extension that exposes your everyday browser, with its logins, to AI assistants over MCP.
Sources and review
Checked against public documentation on . Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.
Letting an assistant work in the browser you already use instead of a clean automation profile.
You want isolation; the assistant acts inside your real browser profile and sessions.
About Chrome MCP Server (mcp-chrome)
Chrome MCP Server runs as a Chrome extension plus a native bridge, exposing your regular browser, with its settings and logged-in sessions, to AI assistants for automation, content analysis and semantic search across tabs. Unlike Playwright-style tools it does not launch a separate browser. The author describes it as early-stage and under active development.
Chrome MCP Server (mcp-chrome) is listed in this index written primarily in TypeScript, with 13k stars on GitHub. Its latest recorded repository push was in January 2026; that is not an ASE editorial review date.
Before connecting: access and data
This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.
- List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
- Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
- Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
- Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.
npm install -g mcp-chrome-bridge