Chrome MCP Server is a Model Context Protocol (MCP) server packaged as a Chrome extension. Instead of launching a separate automated browser the way Playwright-based servers do, it exposes the Chrome instance you already use, so an AI assistant or agent works with your existing login state, settings, and open tabs.
The setup has two parts: the extension itself, loaded unpacked in Chrome, and a mcp-chrome-bridge npm package that registers a native messaging host. MCP clients connect over streamable HTTP at a local port, or over stdio for clients that only support that transport. Everything runs locally.
A built-in vector database indexes tab content for semantic search, and a WebAssembly SIMD build accelerates the vector operations. The project is in early development; authentication, recording and playback, workflow automation, and a Firefox extension are listed as future work. A visual editor for Claude Code and Codex was added in late 2025.
Features
- Client agnostic: any LLM, chatbot client, or agent that speaks MCP can drive the browser
- Browser management: list windows and tabs, navigate, switch and close tabs, go back or forward, and inject content scripts
- Screenshots: element-targeted, full-page, and custom-dimension captures
- Network monitoring: webRequest capture, Debugger API capture with response bodies, and custom HTTP requests
- Content analysis: semantic search across tabs, HTML and text extraction, interactive-element discovery, and console output capture
- Interaction: click elements by CSS selector, fill forms and select options, and simulate keyboard input
- Data management: search history with time filters, and search, add, or delete bookmarks
- Cross-tab context: tools operate across multiple open tabs
- Transports: streamable HTTP (recommended) or stdio
