mcpSource-backedReview first Safety ✓ Privacy ✓

Chrome MCP Server

Chrome extension-based MCP server that exposes an existing Chrome browser profile to AI assistants for tab management, page content, screenshots, interaction, history, bookmarks, and network inspection.

by hangwin·added 2026-06-05·

Claude CodeClaude Desktop

HarnessClaude CodeClaude Desktop

Install

Source

npm install -g mcp-chrome-bridge

Readiness

TrustReview first
Sourcesource-backed
Safety notesPresent
ReviewedYes

Documentation Source repository Registry JSON · LLM text

Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

This server controls the user's existing Chrome browser profile and can reuse logged-in sessions.
Tools can navigate pages, click elements, fill forms, inspect tabs, capture screenshots, inspect network traffic, read history, manage bookmarks, and inject scripts.
Use a dedicated browser profile for agent work and avoid sensitive accounts unless the workflow explicitly requires them.
Do not allow agents to submit forms, make purchases, change account settings, or perform irreversible actions without human approval.
The project describes itself as early-stage and under active development; test carefully before relying on it for critical workflows.

Privacy notes

Open tabs, page content, screenshots, browsing history, bookmarks, cookies/session-derived page state, and network request metadata may be exposed to the MCP client and model.
Screenshots and network responses can contain credentials, personal data, customer data, tokens, and private documents.
Browser automation prompts may reveal personal browsing habits, internal applications, and authenticated service access.

Prerequisites

Node.js 20 or newer and npm or pnpm.
Chrome or Chromium browser.
Latest Chrome MCP extension release from the project repository.
Globally installed mcp-chrome-bridge package.
MCP client that supports streamable HTTP, or the documented stdio fallback.

Schema details

Install type: cli
Troubleshooting: No

Source repository stats

Scope: Source repo

Collection metadata

Estimated setup: 15 minutes
Difficulty: intermediate

Full copyable content

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

About this resource

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

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.

#chrome#browser#automation#screenshots#local

Source citations

Signals

Loading live community signals…