# Chrome MCP Server

> MIT Chrome extension MCP server for your own browser

**Category:** AI Agents  
**Pricing:** open-source  
**URL:** https://github.com/hangwin/mcp-chrome  
**GitHub:** https://github.com/hangwin/mcp-chrome  
**Added:** 2026-10-14

---

## The Hook

mcp-chrome is a Chrome extension plus a small bridge (npm install -g mcp-chrome-bridge) that lets any MCP client control the Chrome you already use — with your logins, cookies and open tabs.

## What's Good

MIT (hangwin/mcp-chrome), TypeScript, release v1.0.0 (2025-12-29). 20+ tools: screenshots, clicks and typing, network monitoring, bookmarks, history, and cross-tab context. Fully local, with Streamable HTTP transport and a built-in vector index for semantic search across open tabs. ★~12.5k.

## The Catch

Because it uses your real browser session, an agent can act as you on every site you are logged in to — point it at a separate Chrome profile for anything sensitive. The README still calls it early-stage, and the last commit was January 2026, so momentum has slowed. The extension is installed from GitHub releases, not the Chrome Web Store. Vs chrome-devtools-mcp (official from the Chrome DevTools team): that one gives DevTools-grade traces, Lighthouse and heap snapshots; mcp-chrome is about reusing your logged-in profile for everyday browsing tasks.

## Verdict

The quickest way to let an agent work in your logged-in Chrome — use a separate profile and keep expectations early-stage.