get_windows_and_tabsLABSCO SUMMARY
Your login state is the feature — and the thing to think about before installing.
Reusing your real profile is why this works on sites that need an account, with no separate login step and no headless-browser detection. It also means anything the model drives is acting as you, in a browser holding your sessions. The debugger-based network capture is the other standout: it returns response bodies, which the webRequest path cannot.
What it is
A Chrome extension that turns your everyday browser into an MCP server. Unlike Playwright-based servers it does not launch a fresh browser: it drives the Chrome you are signed into, so existing sessions and settings apply, and it has Chrome's own APIs rather than an automation subset.
What you get
- Windows and tabs listed, navigated, switched, closed and moved through history —
get_windows_and_tabs,chrome_navigate,chrome_switch_tab,chrome_close_tabs,chrome_go_back_or_forward - Screenshots with element targeting, full-page support and custom dimensions —
chrome_screenshot - Network capture two ways: the webRequest API for request lists, and the Debugger API when you need response bodies —
chrome_network_capture_start,chrome_network_capture_stop,chrome_network_debugger_start,chrome_network_debugger_stop - Custom HTTP requests sent from the browser's own context —
chrome_network_request - Content read and analysed: page HTML or text, the interactive elements on it, and semantic search across the content of your open tabs backed by a built-in vector database —
chrome_read_page,chrome_get_web_content,chrome_get_interactive_elements,search_tabs_content - Interaction by CSS selector plus keyboard input —
chrome_click_element,chrome_fill_or_select,chrome_keyboard - Browsing history searched with time filters, and bookmarks searched, added and deleted —
chrome_history,chrome_bookmark_search,chrome_bookmark_add,chrome_bookmark_delete
Requirements
Chrome or Chromium, plus Node.js >= 20.0.0 and pnpm or npm. Three steps: install mcp-chrome-bridge globally, load the extension from the GitHub release in developer mode, then connect. The recommended client transport is streamableHttp at http://127.0.0.1:12306/mcp; a stdio path exists for clients that need it, pointing at the bridge's mcp-server-stdio.js. Fully local. On pnpm v7+ the post-install registration may need running by hand as mcp-chrome-bridge register.
Setup effort
Follow the published steps
USE CASES
01
Working out what API a site calls and what it returns
Start the debugger-based capture, do the action in the page, then stop and read back the requests with their response bodies — not just the URLs.
02
Finding which of your twenty open tabs has the thing you need
Search the tabs by meaning rather than by title, then switch to the one that matched.
03
Automating a task on a site you are already logged into
Navigate, list the interactive elements to find the right selectors, then click and fill — your existing session carries through, so there is no login step.
04
Making sense of your own browsing
Search history over a time window and pull the content of the pages that matter, instead of scrolling the history page.
25 tools
Listed in project docs. Your client may show a different list.
chrome_navigatechrome_switch_tabchrome_close_tabschrome_go_back_or_forwardchrome_inject_scriptchrome_send_command_to_inject_scriptchrome_screenshotchrome_network_capture_startchrome_network_capture_stopchrome_network_debugger_startchrome_network_debugger_stopchrome_network_requestchrome_read_pagesearch_tabs_contentchrome_get_web_contentchrome_consolechrome_computerchrome_click_elementchrome_fill_or_selectchrome_keyboardchrome_historychrome_bookmark_searchchrome_bookmark_addchrome_bookmark_deleteBEFORE YOU INSTALL
What to know first
Tools you get
25 tools named in the project's documentation.
Requires
- npm on PATH
- Node.js >= 20.0.0
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
Download the latest Chrome extension from GitHub:
URL
https://github.com/hangwin/mcp-chrome/releasesTERMINAL
npm install -g mcp-chrome-bridgeOpen chrome://extensions/ in Chrome, turn on Developer mode, click Load unpacked and select the extension folder you downloaded.
Click the extension icon to open the plugin, then click Connect to see the MCP configuration.
MCP Clients
Cherry Studio — HTTP
CHERRY STUDIO — HTTP · JSON
{
"mcpServers": {
"chrome-mcp-server": {
"type": "streamableHttp",
"url": "http://127.0.0.1:12306/mcp"
}
}
}Claude Code — HTTP
CLAUDE CODE — HTTP · JSON
{
"mcpServers": {
"chrome-mcp": {
"type": "http",
"url": "http://127.0.0.1:12306/mcp"
}
}
}Any MCP client — stdio
ANY MCP CLIENT — STDIO · JSON
{
"mcpServers": {
"chrome-mcp-stdio": {
"command": "npx",
"args": [
"node",
"/Users/<YOUR_USERNAME>/Library/pnpm/global/5/node_modules/mcp-chrome-bridge/dist/mcp/mcp-server-stdio.js"
]
}
}
}The folder up to /Library/pnpm/global/5 is the one npm list -g mcp-chrome-bridge (or pnpm list -g mcp-chrome-bridge) prints; the file is under it at node_modules/mcp-chrome-bridge/dist/mcp/mcp-server-stdio.js.
