MCP & Integrations
mcp-chrome
Source: github.com/hangwin/mcp-chrome · ★ 11849 · TypeScript
Last updated 2026-06-05 · benchmark checked 2026-11-12 · unchanged since 2026-07-30 — deterministic & reproducible
Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search.
mcp-chrome at a glance
Chrome MCP Server (mcp-chrome) is a Chrome extension-based Model Context Protocol server that lets AI assistants like Claude control your Chrome browser for automation, content analysis, and semantic search.
Good for
- Letting an AI assistant automate tasks in your everyday Chrome browser, using your existing logins and settings
- Searching and analyzing content across open browser tabs with built-in semantic search
- Connecting any MCP-compatible LLM or chatbot client to your browser for tasks like screenshots, network monitoring, bookmark and history management
Questions people ask
What does mcp-chrome do?
It is a Chrome extension that runs a local MCP server, exposing your browser's functionality (tabs, bookmarks, history, screenshots, and more) so AI assistants like Claude can control and automate it.
How is it different from browser automation tools like Playwright?
Instead of launching a separate browser process with a clean environment, it uses your actual Chrome browser, so it keeps your existing logins, configurations, and habits, and only needs to activate the extension rather than start a new browser.
Does it work with any AI model or chatbot?
Yes, it is described as chatbot/model agnostic, meaning any preferred LLM, chatbot client, or agent can be used to automate the browser.
Does my browsing data stay private?
The project describes itself as fully local, running a local MCP server intended to ensure user privacy.
What do I need to install it?
You need Node.js 20.0.0 or higher, pnpm or npm, and a Chrome or Chromium browser; you download the extension from the project's GitHub releases and install the mcp-chrome-bridge package globally.
Written by Legit.Show from github.com on 2026-09-30. It does not change the score.
Are you the maker of mcp-chrome? Claim this listing. It is free, takes a meta tag, a DNS record or GitHub admin rights, and never changes the score.
Launched something? Add your product, free.
To cite this score: legit.show/s/gh-hangwin-mcp-chrome/2026-11-12. That address never changes; this page moves with every re-measure.
Legit.Show scored mcp-chrome 67/100 on 2026-11-12, measured across 3 of 7 frames from its public surface. legit.show/s/gh-hangwin-mcp-chrome/2026-11-12
Is mcp-chrome production-ready?
Legit.Show scores mcp-chrome 67 out of 100 — the simple average of its 3 measured frames. Legit.Show ran its deterministic 7-Frame production-readiness benchmark on mcp-chrome (github assessment), measured from the public surface with no LLM in the scoring path. Its strongest frame is Security; its weakest is Discoverability. 3 of the seven frames returned a score; Performance, Accessibility, Privacy and Reliability were not measurable on this service and are recorded as null — not as zero. Maintenance is an additional frame from the open-source teardown, scored separately from the seven. Every frame it averages is published with its evidence on the Legit.Show listing.
The 7 Frames
- Performance — not measurable on this service (null — not scored as 0)
- Accessibility — not measurable on this service (null — not scored as 0)
- Security — 90/100How this compares across the catalogue: The Web Security Baseline
- Privacy — not measurable on this service (null — not scored as 0)
- Reliability — not measurable on this service (null — not scored as 0)
- Standards — 75/100
- Discoverability — 35/100
Open-source teardown
Scored separately — not one of the seven.
- Maintenance — 30/100
What we measured
- No Content-Security-Policy and no HSTS.
- No privacy policy found.
- Sets cookies / loads scripts with no consent prompt.
Who built it
KMG (@sumityadav8181)
Sources and updates
- Description
- Taken from github.com's own website on 2026-06-05.
- Benchmark
- Measured by Legit.Show from the live site, the way any visitor sees it — with no access to its code or accounts. Same method for every product, and no AI decides the score. Last checked 2026-11-12.
Put together from public information, without mcp-chrome's involvement. If anything here is wrong, tell us and a person will check it.
Visit mcp-chrome → · Alternatives to mcp-chrome → · How this was measured →