- Explore MCP Servers
- chrome-mcp
Chrome Mcp
What is Chrome Mcp
chrome-mcp is a Model Context Protocol (MCP) server that allows LLM agents to control a local Chrome browser instance using the Chrome DevTools Protocol (CDP) without the need for screenshots.
Use cases
Use cases for chrome-mcp include automated testing of web applications, scraping data from websites, and developing browser-based applications that require real-time interaction.
How to use
To use chrome-mcp, first install Bun or Node.js, then enable remote debugging in Chrome. After setting up, install dependencies and start the server. For development, use the hot reloading feature.
Key features
Key features of chrome-mcp include fine-grained control over Chrome instances, the ability to interact with web pages programmatically, and support for hot reloading during development.
Where to use
chrome-mcp can be used in various fields including web automation, testing, and development environments where interaction with web pages is required.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Overview
What is Chrome Mcp
chrome-mcp is a Model Context Protocol (MCP) server that allows LLM agents to control a local Chrome browser instance using the Chrome DevTools Protocol (CDP) without the need for screenshots.
Use cases
Use cases for chrome-mcp include automated testing of web applications, scraping data from websites, and developing browser-based applications that require real-time interaction.
How to use
To use chrome-mcp, first install Bun or Node.js, then enable remote debugging in Chrome. After setting up, install dependencies and start the server. For development, use the hot reloading feature.
Key features
Key features of chrome-mcp include fine-grained control over Chrome instances, the ability to interact with web pages programmatically, and support for hot reloading during development.
Where to use
chrome-mcp can be used in various fields including web automation, testing, and development environments where interaction with web pages is required.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Content
Chrome MCP Server
A Model Context Protocol (MCP) server that provides fine-grained control over a Chrome browser instance through the Chrome DevTools Protocol (CDP).
Prerequisites
- Bun (recommended) or Node.js (v14 or higher)
- Chrome browser with remote debugging enabled
Setup
Installing Bun
- Install Bun (if not already installed):
# 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 -
Install dependencies:
bun install
- Start the server:
bun start
For development with hot reloading:
bun dev
The server will start on port 3000 by default. You can change this by setting the PORT environment variable.
Configuring Roo Code to use this MCP server
To use this Chrome MCP server with Roo Code:
-
Open Roo Code settings
-
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
- macOS:
-
Add the following configuration to the
mcpServersobject:
{
"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.
Available Tools
The server provides the following tools for browser control:
navigate
Navigate to a specific URL.
Parameters:
url(string): The URL to navigate to
click
Click at specific coordinates.
Parameters:
x(number): X coordinatey(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.
Usage
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.
Development
To run the server in development mode with hot reloading:
bun dev
This uses Bun’s built-in watch mode to automatically restart the server when files change.
License
MIT
Dev Tools Supporting MCP
The following are the main code editors that support the Model Context Protocol. Click the link to visit the official website for more information.










