claude-chrome

Claude Chrome MCP enables browser automation capabilities via the Claude Chrome Extension using the Chrome Native Messaging protocol. The MCP server exposes an HTTP-based interface that clients can connect to in order to control a Chrome browser through Claude's automation features, such as navigation, form filling, click and scroll actions, and extracting page content. It supports secure token-based authentication and can be configured with custom ports and CORS settings. Once installed and running, you can configure your MCP clients (OpenCode, Claude Desktop, or other MCP clients) to point at http://localhost:3456/mcp (or your configured port) and supply the authorization token provided during installation or via the status command.

To use the server’s capabilities, first install the Claude Chrome extension and register the native host as described in the Quick Start. Then start the MCP server process and obtain the token. With a configured client, you can instruct the client to perform browsing, text extraction, form interactions, and more, while also capturing screenshots or recording workflows for debugging or sharing. If you need development mode features, you can run with insecure mode to bypass token-based auth (not recommended for production).

Prerequisites:

• Node.js or Bun toolkit installed on your machine
• Access to the internet to fetch dependencies
• Chrome with Claude Chrome Extension installed

Installation steps:

1. Install the MCP server globally (via Bun as shown in the Quick Start): bun install -g git+https://github.com/nonsleepr/claude-chrome-mcp.git

2. Build and link the server for CLI usage: git clone https://github.com/nonsleepr/claude-chrome-mcp.git cd claude-chrome-mcp bun install bun run build bun link

3. Register the Native Host in your Chrome profile (this prints an authentication token): claude-chrome-mcp --install

4. Start the MCP server (example depending on your setup): claude-chrome-mcp --port 3456

5. Retrieve the current status and token at any time: claude-chrome-mcp --status

Configure your MCP client to point at http://localhost:3456/mcp with the provided Authorization header.

Notes:

• Ensure Chrome is fully closed when registering the native host and again after any changes to the extension configuration.
• If you encounter port conflicts, re-run the install with a different port (e.g., claude-chrome-mcp --install --port 8080).
• Insecure mode is intended for local development only and disables token-based authentication; use with caution and never expose it to untrusted networks.
• The CLI supports optional parameters for tokens, port, and CORS origins; consult the help output (claude-chrome-mcp --help) for details.
• Client configurations shown in the README (OpenCode and Claude Desktop) illustrate how to supply the Authorization header for requests.