Chrome Browser Control

by lxe

13 stars

Not rated

GitHub

About

Enables fine-grained control over Chrome browser instances through the Chrome DevTools Protocol, allowing web navigation, element interaction, text input, and content extraction with automatic handling of dynamic content.

Details

Author: lxe
Repository: lxe/chrome-mcp
GitHub stars: 13
Categories: Web Scraping, Automation, Other, Productivity, Design, Developer Tools, AI, Infrastructure, Frontend
Tags: #web

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below
Plugin Name Chrome Browser Control

Command (node, npx, python, etc.) npx
Arguments
- Argument 1 -y
- Argument 2 @highlight/mcp-server
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "/c",
                "npx",
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "/c",
                "npx",
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "/c",
                "npx",
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "/c",
                "npx",
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "/c",
                "npx",
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

From the repository

1. Install Bun (if not already installed):

To use this Chrome MCP server with Roo Code: 1. Open Roo Code settings 2. Navigate to the MCP settings configuration file at: - macOS: ~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json - Windows: %APPDATA%\Code\User\globalStorage\rooveterinaryinc.roo-cline\settings\cline_mcp_settings.json - Linux: ~/.config/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json 3. Add the following configuration to the mcpServers object:

json
{
"mcpServers": {
"chrome-control": {
"url": "http://localhost:3000/sse",
"disabled": false,
"alwaysAllow": []
}
}
}
```

4. Save the file and restart Roo Code to apply the changes.

5. You can now use the Chrome MCP tools in Roo Code to control the browser.

`navigate`

Navigate to a specific URL. Parameters: url (string): The URL to navigate to

`click`

Click at specific coordinates. Parameters: x (number): X coordinate, y (number): Y coordinate

`type`

Type text at the current focus. Parameters: text (string): Text to type

`clickElement`

Click on an element by its index in the page info. Parameters: selector (string): Element index (e.g., '0' for the first element)

`getText`

Get text content of an element using a CSS selector. Parameters: selector (string): CSS selector to find the element

`getPageInfo`

Get semantic information about the page including interactive elements and text nodes.

`getPageState`

Get current page state including URL, title, scroll position, and viewport size.

The server provides the following tools for browser control:

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "chrome browser control": {
            "env": {},
            "args": [
                "-y",
                "@highlight/mcp-server"
            ],
            "command": "npx"
        }
    }
}

Linux

{
    "env": [],
    "args": [
        "-y",
        "@highlight/mcp-server"
    ],
    "command": "npx"
}

Macos

{
    "env": [],
    "args": [
        "-y",
        "@highlight/mcp-server"
    ],
    "command": "npx"
}

Windows

{
    "env": [],
    "args": [
        "/c",
        "npx",
        "-y",
        "@highlight/mcp-server"
    ],
    "command": "cmd"
}

A Model Context Protocol (MCP) server that provides fine-grained control over a Chrome browser instance through the Chrome DevTools Protocol (CDP).

# macOS, Linux, or WSL curl -fsSL https://bun.sh/install | bash # Windows (using PowerShell) powershell -c "irm bun.sh/install.ps1 | iex" # Alternatively, using npm npm install -g bun

Start Chrome with remote debugging enabled:

# macOS /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 # Windows start chrome --remote-debugging-port=9222 # Linux google-chrome --remote-debugging-port=9222

The server will start on port 3000 by default. You can change this by setting thePORTenvironment variable.

Configuring Roo Code to use this MCP server

To use this Chrome MCP server with Roo Code:

Navigate to the MCP settings configuration file at:

- macOS:~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json
- Windows:%APPDATA%\Code\User\globalStorage\rooveterinaryinc.roo-cline\settings\cline_mcp_settings.json
- Linux:~/.config/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json

Add the following configuration to themcpServersobject:

{ "mcpServers": { "chrome-control": { "url": "http://localhost:3000/sse", "disabled": false, "alwaysAllow": [] } } }

Save the file and restart Roo Code to apply the changes.

You can now use the Chrome MCP tools in Roo Code to control the browser.

The server provides the following tools for browser control:

- x(number): X coordinate
- y(number): Y coordinate

Click on an element by its index in the page info.

- selector(string): Element index (e.g., "0" for the first element)

Get text content of an element using a CSS selector.

- selector(string): CSS selector to find the element

Get semantic information about the page including interactive elements and text nodes.

Get current page state including URL, title, scroll position, and viewport size.

The server implements the Model Context Protocol with SSE transport. Connect to the server at:

- SSE endpoint:http://localhost:3000/sse
- Messages endpoint:http://localhost:3000/message?sessionId=...

When using with Roo Code, the configuration in the MCP settings file will handle the connection automatically.

To run the server in development mode with hot reloading:

This uses Bun's built-in watch mode to automatically restart the server when files change.

MCP server for browser automation via Vercel agent-browser CLI

Convert any URL to LLM-ready Markdown via real Chrome browsers. 3 tools: scrape, crawl, search. Free via MCP, pay-per-use via x402.

An MCP server that allows AI agents to control a web browser using the browser-use library.

Exposes Chrome browser functionality to AI assistants for automation, content analysis, and semantic search via a Chrome extension.

Stealthy, LLM-drivable browser engine — a Python library + 85-tool MCP server on stealth Chromium with full Chrome DevTools Protocol.

Multi-session browser MCP for AI agents — stealth mode, session pooling, humanization, 10x fewer tokens than Playwright

A Go-based MCP server for interacting with the Lightpanda Browser using the Chrome DevTools Protocol (CDP).

A browser automation agent using the Model Context Protocol (MCP) to enable browser interactions.

A browser automation service for capturing console output, useful for tasks like public sentiment analysis.

Control the Chrome browser for web automation using an AI model. Requires the MCP Chrome extension.

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

navigate

click

type

clickElement

getText

getPageInfo

getPageState

Claude Desktop / Cursor

Linux

Macos

Windows

Configuring Roo Code to use this MCP server

Install

More like this

@mendableai/firecrawl Mcp Server

Umut Naci

Playwright

Sequential Thinking

Filesystem

EverArt

`navigate`

`click`

`type`

`clickElement`

`getText`

`getPageInfo`

`getPageState`