by cmann50
Integrate Google search with automated Chrome browsing for data extraction from web pages, perfect for web data scraping
Performs Google searches and extracts webpage content by automating your Chrome browser. Uses Chrome's interface to avoid search blocking and access authenticated content.
Google Search (via Chrome) is a community-built MCP server published by cmann50 that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate Google search with automated Chrome browsing for data extraction from web pages, perfect for web data scraping It is categorized under search web. This server exposes 2 tools that AI clients can invoke during conversations and coding sessions.
You can install Google Search (via Chrome) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Google Search (via Chrome) is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
Google Search (via Chrome) reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: Google Search (via Chrome) is the kind of server we cite when onboarding engineers to host + tool permissions.
Google Search (via Chrome) is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Google Search (via Chrome) is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Strong directory entry: Google Search (via Chrome) surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, Google Search (via Chrome) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Google Search (via Chrome) into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: Google Search (via Chrome) is the kind of server we cite when onboarding engineers to host + tool permissions.
Google Search (via Chrome) is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We wired Google Search (via Chrome) into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
showing 1-10 of 28
MCP tool for Google search and webpage content extraction using Chrome browser. Works with Claude to enable Google search and content fetching capabilities.
Configure Claude Desktop
{
"mcpServers": {
"mcp-chrome-google-search": {
"command": "npx",
"args": [
"-y",
"@cmann50/mcp-chrome-google-search"
]
}
}
}
First Time Setup
Grant Accessibility Permissions
Enable Chrome JavaScript from Apple Events
Once configured, Claude will be able to perform Google searches and extract webpage content through Chrome when you make requests.
npx mcp-chrome-google-search
npm run build{
"google-tools": {
"command": "node",
"args": [
"/your/checkout/path/mcp/mcp-chrome-google-search/dist/index.js"
]
}
}
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
# Follow logs in real-time
tail -n 20 -F ~/Library/Logs/Claude/mcp*.log
echo '{"allowDevTools": true}' > ~/Library/Application\ Support/Claude/developer_settings.json
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:
If Chrome control fails:
MIT License - see LICENSE file for details
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.