$ loading_
Expose browser automation tools to any MCP client through Claude's Chrome extension.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "chrome-mcp-bridge" yet — see the docs or source repo.
Use chrome-mcp-bridge to open a target webpage and complete navigation, clicking, and information retrieval with the available browser automation tools.
Returns page results or extracted information after executing browser automation steps.
Connect chrome-mcp-bridge to my MCP client and drive the official Claude Chrome extension via native messaging for browser actions.
Provides a browser automation capability callable by the MCP client without requiring a claude.ai login.
Call the browser tools exposed by chrome-mcp-bridge in an automation workflow to perform a set of web interaction tasks.
Outputs web automation results orchestrated through the MCP client.
Developers using an MCP client can add browser automation capabilities through this bridge, letting the model actually drive web interactions. It is useful when browser actions need to be part of a unified MCP toolchain.
When a team wants browser capabilities from the Claude Chrome extension without relying on a gated access path, this tool offers an ungated reimplementation. It is available to any MCP client rather than a single entry point.
If logging into claude.ai is inconvenient but web actions still need to be performed through the official Claude Chrome extension, this bridge can connect via native messaging. This preserves the extension-based execution path while removing the login dependency.
It is an MCP bridge tool that reimplements the “Claude in Chrome” bridge. It exposes 22 browser automation tools to any MCP client and drives the official Claude Chrome extension through native messaging.
Based on the provided description, no claude.ai login is required. One of its stated goals is to provide this bridge capability without requiring that login.
It is known to drive the official Claude Chrome extension via native messaging, so it at least involves that extension and the native messaging mechanism. For more detailed installation and runtime requirements, see the source repository.
Control a real Chrome browser for browsing, interaction, and page reading.
Control Chrome via MCP for browsing, form filling, screenshots, and logs.
Control Chrome locally or remotely to automate browsing, forms, screenshots, and scripts.
Connect MCP clients to WebMCP-enabled Chrome pages for tool discovery and execution.
Debug web apps through Chrome DevTools using natural language commands.
An MCP bridge that lets Claude Code consult ChatGPT mid-task.