Chrome MCP Server

Content

Chrome MCP Server is an extension-based MCP server for controlling and inspecting a local Chrome browser. Unlike browser automation servers that launch a separate clean browser, this project is designed to work with an existing Chrome profile, including open tabs, settings, extensions, and login state.

It uses a Chrome extension plus the mcp-chrome-bridge package. The project documents a streamable HTTP setup generated by the extension and an alternate stdio bridge path for clients that do not support streamable HTTP.

Source Review

• https://github.com/hangwin/mcp-chrome
• https://github.com/hangwin/mcp-chrome/blob/master/README.md
• https://www.npmjs.com/package/mcp-chrome-bridge

These sources were reviewed on 2026-06-05. Prefer the live repository for current release downloads, bridge installation steps, supported transports, and tool lists.

Features

• Streamable HTTP MCP endpoint through a local Chrome extension bridge.
• Stdio fallback documented for MCP clients that do not support streamable HTTP.
• Access to existing Chrome tabs and logged-in browser state.
• Browser window and tab listing, switching, navigation, and close operations.
• Screenshots, page content extraction, semantic tab content search, console output, and interactive element discovery.
• Network capture and custom request tooling.
• Click, form fill/select, keyboard, history, and bookmark tools.

Installation

Install the bridge:

npm install -g mcp-chrome-bridge

Then download and load the latest Chrome extension release from the project repository, connect it, and use the MCP configuration generated by the extension. If a client only supports stdio, use the fallback path documented in the project README and point the client at the installed stdio bridge file.

{
  "mcpServers": {
    "chrome-mcp-stdio": {
      "command": "node",
      "args": ["/ABSOLUTE_PATH_TO/mcp-server-stdio.js"]
    }
  }
}

Use Cases

• Summarize, inspect, or compare open browser tabs.
• Capture screenshots and page content for UI debugging.
• Inspect network requests while reproducing a web application issue.
• Automate browser actions in a dedicated test profile.
• Search browser tab content semantically across active work.

Safety and Privacy

This server is powerful because it works with the user's real Chrome session. Prefer a separate Chrome profile for agent work, keep sensitive accounts closed, and require human confirmation before actions that submit forms, change account state, purchase goods, send messages, or alter data.

Treat screenshots, tab content, browsing history, bookmarks, and network captures as sensitive. They may contain private application data or personal information.

Duplicate Check

content/mcp/chrome-devtools-mcp-server.mdx covers the official Chrome DevTools MCP server. This entry covers the separate hangwin/mcp-chrome extension-based server that uses an existing Chrome profile.

• Source repositorygithub.com 2026-07-21T01:31:08+00:00
• Documentationgithub.com
• Submitted by oktofeesh12026-06-05