Chrome Tools
An MCP server that provides tools for interacting with Chrome through its DevTools Protocol, enabling remote control of Chrome tabs to execute JavaScript, capture screenshots, monitor network traffic, and more.
What is Chrome Tools?
Chrome Tools is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to mcp server that provides tools for interacting with chrome through its devtools protocol, enabling remote control of chrome tabs to execute javascript, capture screenshots, monitor network traffic, an...
An MCP server that provides tools for interacting with Chrome through its DevTools Protocol, enabling remote control of Chrome tabs to execute JavaScript, capture screenshots, monitor network traffic, and more.
This server falls under the Browser Automation category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- An MCP server that provides tools for interacting with Chrom
Use Cases
Maintainer
Works with
Installation
Manual Installation
npx chrome-tools-mcp-serverConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use Chrome Tools
Chrome Tools MCP Server connects AI agents to a running Chrome browser instance via Chrome's DevTools Protocol (CDP), enabling programmatic control of browser tabs from within MCP conversations. It provides tools to list open tabs, execute JavaScript, capture screenshots, monitor network traffic, navigate URLs, inspect DOM elements, and click page elements — all without a separate automation framework. Developers use it for AI-assisted debugging, automated testing, web scraping workflows, and visual inspection of web applications directly from Claude.
Prerequisites
- Node.js 18 or later installed
- Google Chrome browser installed on the same machine or accessible via SSH tunnel
- Chrome must be launched with remote debugging enabled on port 9222
- An MCP-compatible client such as Claude Desktop
Launch Chrome with remote debugging enabled
Chrome must be started with the --remote-debugging-port flag. Close any existing Chrome instances first, then launch with debugging enabled.
# macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
# Windows
"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222
# Linux
google-chrome --remote-debugging-port=9222Verify Chrome DevTools Protocol is accessible
Confirm that Chrome's remote debugging interface is reachable at the default URL before configuring the MCP server.
curl http://localhost:9222/json/versionInstall the chrome-tools package
Install the MCP server package globally or use it via npx. Installing globally makes the binary available without repeated downloads.
npm install -g @nicholmikey/chrome-toolsAdd the server to your MCP client configuration
Edit your claude_desktop_config.json to add the chrome-tools server. Set CHROME_DEBUG_URL if Chrome is on a non-default port or accessed remotely.
Restart Claude Desktop and verify connection
Restart Claude Desktop, then ask Claude to list open Chrome tabs. A successful response means the CDP connection is established.
Chrome Tools Examples
Client configuration
Add this to claude_desktop_config.json. The CHROME_DEBUG_URL defaults to http://localhost:9222 if not set.
{
"mcpServers": {
"chrome-tools": {
"command": "npx",
"args": ["-y", "@nicholmikey/chrome-tools"],
"env": {
"CHROME_DEBUG_URL": "http://localhost:9222",
"CHROME_CONNECTION_TYPE": "direct"
}
}
}
}Prompts to try
Once connected to Chrome, use these prompts to control the browser from Claude.
- "List all open Chrome tabs and tell me which ones are loading slowly"
- "Take a screenshot of the current tab and describe what you see"
- "Execute JavaScript on the active tab to get the page title and all heading text"
- "Monitor network traffic on this tab for 10 seconds and show me all API calls made"
- "Click the submit button on the current form and capture the result"Troubleshooting Chrome Tools
Connection refused at localhost:9222
Chrome was not launched with --remote-debugging-port=9222, or another Chrome instance without the flag is already running. Quit all Chrome windows, then relaunch with the debugging flag.
list_tabs returns empty or shows only one tab
Chrome's remote debugging only exposes tabs from the specific Chrome instance launched with the debugging flag. Ensure you are opening pages in that same Chrome instance, not a separately launched one.
Screenshots are blank or show wrong content
Verify the correct tabId is being used. Run list_tabs first to get current tab IDs, as IDs change when tabs are opened or closed. Also ensure the tab is in the foreground.
Frequently Asked Questions about Chrome Tools
What is Chrome Tools?
Chrome Tools is a Model Context Protocol (MCP) server that mcp server that provides tools for interacting with chrome through its devtools protocol, enabling remote control of chrome tabs to execute javascript, capture screenshots, monitor network traffic, and more. It connects AI assistants to external tools and data sources through a standardized interface.
How do I install Chrome Tools?
Follow the installation instructions on the Chrome Tools GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.
Which AI clients work with Chrome Tools?
Chrome Tools works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is Chrome Tools free to use?
Yes, Chrome Tools is open source and available under the MIT License license. You can use it freely in both personal and commercial projects.
Chrome Tools Alternatives — Similar Browser Automation Servers
Looking for alternatives to Chrome Tools? Here are other popular browser automation servers you can use with Claude, Cursor, and VS Code.
Chrome DevTools MCP
★ 40.6kAI-powered Chrome automation server with natural language element detection. Control Chrome browser through MCP protocol for testing, debugging, and performance analysis. Features 91% accuracy in element location, works with free AI models, and suppo
UI TARS Desktop
★ 34.9k📇 🏠 - Browser automation capabilities using Puppeteer, both support local and remote browser connection.
Playwright
★ 32.8kA production-ready browser automation server that enables AI assistants to interact with web pages using tools for navigation, element interaction, and data extraction. It features a built-in Inspector UI and robust crash recovery for reliable automa
Page Agent
★ 18.0kJavaScript in-page GUI agent. Control web interfaces with natural language.
Chrome
★ 11.7kAn extension-based MCP server that enables AI assistants to control your browser, leveraging existing sessions and login states for automation and content analysis. It provides over 20 tools for semantic tab search, interactive element manipulation,
LAMDA
★ 7.8kThe most powerful Android RPA agent framework, next generation mobile automation.
Browse More Browser Automation MCP Servers
Explore all browser automation servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up Chrome Tools in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use Chrome Tools?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.