- Home
- MCP servers
- MCP Chrome Google Search
MCP Chrome Google Search
- html
22
GitHub Stars
html
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"cmann50-mcp-chrome-google-search": {
"command": "npx",
"args": [
"-y",
"@cmann50/mcp-chrome-google-search"
]
}
}
}You can enable Google search and web content extraction through Chrome by running a dedicated MCP server that works with Claude. This setup lets Claude perform Google queries and fetch webpage content by automating Chrome, while keeping your browser session and authenticated content accessible.
How to use
Use a compatible MCP client to connect to the Chrome Google Search MCP server. Once connected, you can request Google searches and have Claude fetch and extract content from webpages through your Chrome browser. The server runs locally and communicates via your MCP client, so you can perform searches and retrieve results or page snippets as needed without leaving your browser environment.
How to install
Prerequisites you need before installing are macOS, Google Chrome, and Node.js 20 or higher.
Option 1: NPX installation (quick start) simply runs the MCP server without a local install. Use this to start immediately.
Option 2: Custom installation (for a more integrated setup) involves configuring Claude to run the MCP server from a local checkout.
{
"mcpServers": {
"mcp-chrome-google-search": {
"command": "npx",
"args": [
"-y",
"@cmann50/mcp-chrome-google-search"
]
}
}
}
Additional setup and usage notes
First time setup requires granting macOS accessibility permissions so Claude can control Chrome and enabling JavaScript from Apple Events in Chrome. These need to be performed once per machine.
Also ensure Claude Desktop has been configured to allow this MCP server. After setup, restart Claude Desktop to apply changes.
Running in a typical local environment is straightforward, and the MCP server will operate through a Chrome window to perform searches and fetch content. Each request opens a new tab as needed and unused tabs can be closed to maintain performance.
Config, development, and debugging
The server uses Node.js tooling and can be tested locally by installing dependencies and building if you are contributing changes. You can observe logs in real time for troubleshooting.
For development, you can enable developer settings in Claude to access DevTools and monitor errors while tailing log output.
Troubleshooting
If you encounter a Chrome JavaScript error, re-enable JavaScript from Apple Events in Chrome: View > Developer > Allow JavaScript from Apple Events.
If Chrome control fails due to accessibility permissions, ensure the terminal app has Accessibility permissions enabled in System Preferences.
Security and notes
Visible automation will open and control Chrome windows. Treat this MCP as trusted only within secure environments where Claude has Chrome control access.
Available tools
google_search
Performs Google searches and extracts webpage content through Chrome by coordinating with Claude to fetch results and page content.