Chrome MCP Server

🚀 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

1. Ensure you have the latest version of Node.js (version 14+) installed.
2. Clone this code repository to your local machine.
3. Run the command npm install to install the dependencies.
4. 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

1. Install the development tool extension supporting the MCP protocol in the Chrome browser.
2. Start the local server, which listens on port 3000 by default.
3. The development tool interacts with the server through HTTP requests.
4. 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+).

🔧 Technical Details

Security Precautions

• Use this server only in a trusted local network.
• Do not expose this service to the Internet.
• Regularly update security configurations and dependencies.

Additional Notes

• Support CORS configuration, allowing specified domains to access the API.
• Provide detailed logging functionality for easy debugging and analysis.
• Have an extensible plugin architecture, supporting more custom features.