Chrome MCP Server

A Node.js server that acts as a bridge between the Chrome DevTools extension and Cursor AI, providing debugging and monitoring functions, including capturing console logs, network requests, screenshots, etc.

Developer tools Monitoring #Debugging tool #Monitoring service #Chrome extension #AI integration .JavaScript

rating : 2.5 points

downloads : 15

update time : 2025-04-23

What is the Chrome MCP Server?

The Chrome MCP Server is a Node.js service that integrates with the Chrome DevTools extension to provide browser debugging and monitoring capabilities for Cursor AI.

How to use the Chrome MCP Server?

Through simple installation and configuration steps, you can quickly start using the server to capture browser data.

Use cases

It is suitable for scenarios where developers need to debug browser behavior, capture network requests, or monitor page elements.

Main Features

Capture console logsCollect all log information in the browser console in real - time.

Capture network requestsTrack successful and failed network requests and record detailed HTTP information.

Take screenshotsTake a snapshot of the current web page with one click.

Automatically detect port conflictsWhen the default port is occupied, the server will automatically try other available ports.

Force JSON outputEnsure that all outputs are in standard JSON format for easy parsing and analysis.

Advantages and Limitations

Advantages

Easy to install and configure

Support multiple browser monitoring functions

Powerful log parsing ability

Compatible with mainstream operating systems

Limitations

Only for local use, does not support public network deployment

Requires a Node.js environment to be installed

How to Use

Install dependencies

Make sure Node.js version 14+ is installed.

Start the server

Run the server to start capturing browser data.

Configure Cursor

Add a new MCP server address in the Cursor settings.

Usage Examples

Capture console logsUse this function to view all console outputs.

Check network requestsRecord and analyze the success or failure of network requests.

Frequently Asked Questions

Why can't my server start?

How to ensure that all outputs are in JSON format?

Related Resources

Official documentation

Visit the GitHub repository for more help and support.

Node.js official website

Download and install the Node.js environment.

🚀 Chrome Browser MCP Protocol Development Guide

This guide provides a comprehensive introduction to the development of the Chrome browser MCP protocol, including installation steps, feature descriptions, usage processes, and more.

🚀 Quick Start

Installation Steps

Ensure you have the latest version of Node.js (version 14+) installed.
Clone this code repository to your local machine.
Run the command npm install to install the dependencies.
Start the server: Use npm start or directly run node src/index.js.

✨ Features

Core Features

Log Collection: Retrieve real - time log outputs from the browser console.
Network Data Monitoring: Capture network request and response information of web pages.
Element Operations: Obtain information about the currently selected element and its context.
Screenshot Function: Support full - screen screenshots or screenshots of specified areas.

Available Tools

getConsoleLogs: Get console logs.
getConsoleErrors: Get console error information.
getNetworkErrorLogs: Get logs of failed network requests.
getNetworkSuccessLogs: Get logs of successful network requests.
takeScreenshot: Take a screenshot of the page.
getSelectedElement: Get information about the currently selected element.
wipeLogs: Clear all stored log data.

💻 Usage Examples

Basic Usage

Install the development tool extension supporting the MCP protocol in the Chrome browser.
Start the local server, which listens on port 3000 by default.
The development tool interacts with the server through HTTP requests.
The Claude AI plugin obtains the required data through the MCP interface.

📚 Documentation

Frequently Asked Questions

Question: "Port is already in use" is prompted when starting the server.

Solution:
- Check if there are other processes occupying port 3000.
- You can specify a new port by setting the environment variable PORT=custom_port.
```
# Windows
set PORT=3001 && node src/index.js

# Mac/Linux
PORT=3001 node src/index.js
```

Question: The server does not respond after starting.

Troubleshooting Steps:
1. Check the network configuration to ensure that the firewall does not block the port.
2. Check the console output for detailed error information.
3. Ensure that the Node.js version meets the requirements (14+).