mcp-chrome-server
Provides browser automation capabilities for Google Chrome, including navigation, element manipulation, login automation (with CAPTCHA and 2FA handling), and credential management via system keychain.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-chrome-serverlog in to my GitHub account"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Chrome Server
A Chrome server based on MCP (Model-Controller-Prompt) for browser automation.
Installation
Prerequisites
Python 3.12
Google Chrome browser installed
uv (Python package installer) or Docker
Installing via Smithery
npx -y @smithery/cli install @dlwjdtn535/mcp-chrome-server --client claudeConfiguration Setup
Choose one of the following setup methods based on your environment:
1. Using uv (Recommended)
Windows Setup:
{
"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 Setup:
{
"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 Setup:
{
"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"
}
}
}
}Related MCP server: Browser-MCP Server
Configuration
Chrome Profile Paths
Default Chrome profile paths for each operating system:
OS | Path |
Windows |
|
macOS |
|
Linux |
|
Important Notes
Close all running Chrome instances before starting the automation server
Ensure proper permissions for the Chrome profile directory
For Docker setup, make sure the volume mount path matches your system's Chrome profile path
Credential Management
Securely store and manage login information using the system keychain:
# Save credentials
result = tool_save_credentials(
site="example.com",
username="your_username",
password="your_password"
)
# Retrieve saved credentials
result = tool_get_credentials(
site="example.com",
username="your_username"
)Key Features
Browser Control
# Open browser
result = tool_open_browser()
# Navigate to URL
result = tool_navigate(url="https://example.com")
# Close browser
result = tool_close_browser()Web Login
result = tool_web_login(
url="https://example.com/login",
credentials={
"username": "your_username",
"password": "your_password"
},
selectors={
"username": "#id",
"password": "#pw",
"submit": ".login-button"
}
)Special handling:
Waits for user to solve CAPTCHA when detected
Automatic detection of 2-factor authentication
Detailed analysis of login failure scenarios
Element Manipulation
# Click element
result = tool_click(selector=".button")
# Type text
result = tool_type(
selector="#input-field",
text="Hello, World!"
)
# Get text
result = tool_get_text(selector=".content")
# Get multiple elements
result = tool_get_elements(selector=".items")Important Considerations
Chrome Profile Usage
Verify correct profile path configuration
Close all other Chrome windows using the profile
Automation Detection Prevention
Simulation of natural user behavior
Maintain appropriate delays between login attempts
Security
Always use system keychain for important credentials
Never expose credentials directly in environment variables or configuration files
This server cannot be installed
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dlwjdtn535/mcp-chrome-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server