MCP Chrome Google Search
MCP Chrome Google Search Tool
MCP tool for Google search and webpage content extraction using Chrome browser. Works with Claude to enable Google search and content fetching capabilities.
Quick Installation
Configure Claude Desktop
Open Claude Desktop on Mac
Go to Claude > Settings > Developer > Edit Config
Add the following to your config file:
{ "mcpServers": { "mcp-chrome-google-search": { "command": "npx", "args": [ "-y", "@cmann50/mcp-chrome-google-search" ] } } }Restart Claude Desktop
First Time Setup
Grant Accessibility Permissions
On first run, approve macOS accessibility permissions prompt
Navigate to: System Preferences > Security & Privacy > Privacy > Accessibility
Add and enable permissions for your terminal app
Enable Chrome JavaScript from Apple Events
Open Chrome
Navigate to: View > Developer > Allow JavaScript from Apple Events
One-time setup only
Once configured, Claude will be able to perform Google searches and extract webpage content through Chrome when you make requests.
Key Advantages
Free to search google
Opens and small windows and uses your chrome browser, so should not get blocked
Since it is using your Chrome window it can access authenticated content. Claude can just open the URL in your browser.
Platform Support
✅ macOS
❌ Windows (not supported)
❌ Linux (not supported)
Requirements
macOS
Google Chrome
Node.js 20 or higher
Alternative Installation Methods
NPX Installation
npx mcp-chrome-google-searchCustom Installation
Checkout from git
Run
npm run buildAdd to Claude config (use absolute path):
{
"google-tools": {
"command": "node",
"args": [
"/your/checkout/path/mcp/mcp-chrome-google-search/dist/index.js"
]
}
}Local development
To test changes locally bump package.json version and run to put it in edit mode:
npm install -g .Then just do npm run build and the files will go in dist where claude is monitoring
Then press ctrl-R in claude desktop, no need to restart it
Debugging
Log Monitoring
# Follow logs in real-time
tail -n 20 -F ~/Library/Logs/Claude/mcp*.logDev Tools Access
Enable developer settings:
echo '{"allowDevTools": true}' > ~/Library/Application\ Support/Claude/developer_settings.jsonOpen DevTools: Command-Option-Shift-i in Claude desktop
Use ctrl-r in Claude desktop while tailing for better errors
Troubleshooting
Chrome JavaScript Error
If you see:
execution error: Google Chrome got an error: Executing JavaScript through AppleScript
is turned off. For more information: https://support.google.com/chrome/?p=applescript (12)Solution:
Open Chrome
View > Developer > Allow JavaScript from Apple Events
Accessibility Permission Issues
If Chrome control fails:
Open System Preferences
Security & Privacy > Privacy > Accessibility
Ensure terminal app is listed and enabled
Use lock icon to make changes if needed
Implementation Details
Uses AppleScript for Chrome control
Visible automation - Chrome windows will open/navigate
Each request opens a new Chrome tab
Close unused tabs periodically for optimal performance
Only use with trusted Claude instances (has Chrome control access)
Support
Create GitHub issues for problems
Include macOS and Chrome version details
License
MIT License - see LICENSE file for details
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/cmann50/mcp-chrome-google-search'
If you have feedback or need assistance with the MCP directory API, please join our Discord server