MCP Chrome Server

🚀 MCP Chrome Server

A browser automation Chrome server based on MCP (Model-Controller-Prompt).

🚀 Quick Start

✨ Features

MCP Chrome Server offers the following key features:

1. Browser automation control
2. Multi-session management
3. Cross-platform support
4. Plugin extension compatibility

📦 Installation

Prerequisites

• Python 3.12
• Installed Google Chrome browser
• uv (Python package installer) or Docker

Install using Smithery

npx -y @smithery/cli install @dlwjdtn535/mcp-chrome-server --client claude

Configuration Settings

Choose a configuration method based on your environment:

1. Using uv (Recommended)

Windows Settings:

{
  "mcpServers": {
    "mcp-chrome-server": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "%LOCALAPPDATA%\\Programs\\mcp-chrome-server\\src",
        "mcp-chrome-server"
      ],
      "env": {
        "CHROME_PROFILE_PATH": "%LOCALAPPDATA%\\Google\\Chrome\\User Data"
      }
    }
  }
}

macOS Settings:

{
  "mcpServers": {
    "mcp-chrome-server": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/usr/local/bin/mcp-chrome-server/src",
        "mcp-chrome-server"
      ],
      "env": {
        "CHROME_PROFILE_PATH": "$HOME/Library/Application Support/Google/Chrome"
      }
    }
  }
}

Linux Settings:

{
  "mcpServers": {
    "mcp-chrome-server": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/usr/local/bin/mcp-chrome-server/src",
        "mcp-chrome-server"
      ],
      "env": {
        "CHROME_PROFILE_PATH": "$HOME/.config/google-chrome"
      }
    }
  }
}

Configuration

Chrome Profile Path

Default Chrome profile paths on different operating systems:

⚠️ Important Note

• Close all running Chrome instances before starting the automation server.
• Ensure that the Chrome profile directory has appropriate permissions.
• For Docker settings, make sure the volume mount path is correct.

💡 Usage Tip

• Do not write sensitive information directly into the configuration file.
• Regularly update the Chrome browser to get the latest security patches.
• It is recommended to conduct access control tests after configuration.

💻 Usage Examples

Start the Server

uv run mcp-chrome-server

Configuration Parameters

• --port: Specify the port the service listens on, default is 8080.
• --profile: Specify the Chrome profile directory, default is $HOME/.config/google-chrome.

Error Handling

Common Errors

1. Connection Refused: The server is not started or the port is occupied.
2. Profile Not Found: The specified profile path does not exist.
3. Version Mismatch: The Chrome version is incompatible.

Solutions

1. Ensure the server is started correctly.
2. Check if the configuration file path is correct.
3. Use a Chrome version compatible with the system.

Contact Information

• Email: support@dlwjdtn535.com
• GitHub: github.com/dlwjdtn535/mcp-chrome-server