search-web

Google Search (via Chrome)

by cmann50

Integrate Google search with automated Chrome browsing for data extraction from web pages, perfect for web data scraping

Integrates Google search and webpage content extraction via Chrome browser automation, enabling access up-to-date web information for tasks like fact-checking and research.

github stars

22

Free Google searchingmacOS onlyAccesses authenticated content

best for

  • / Researchers needing current web information
  • / Users requiring access to authenticated web content
  • / Fact-checking and web research tasks

capabilities

  • / Search Google with filtering by site and timeframe
  • / Extract readable text content from webpages
  • / Access authenticated content through your logged-in Chrome session
  • / Get paginated search results with ~10 results per page

what it does

Performs Google searches and extracts webpage content by automating your Chrome browser. Uses Chrome's interface to avoid search blocking and access authenticated content.

about

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.

how to install

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.

license

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.

readme

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

  1. 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
  2. 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

  1. macOS
  2. Google Chrome
  3. Node.js 20 or higher

Alternative Installation Methods

NPX Installation

npx mcp-chrome-google-search

Custom Installation

  1. Checkout from git
  2. Run npm run build
  3. Add 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*.log

Dev Tools Access

  1. Enable developer settings:
echo '{"allowDevTools": true}' > ~/Library/Application\ Support/Claude/developer_settings.json
  1. Open DevTools: Command-Option-Shift-i in Claude desktop
  2. 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:

  1. Open Chrome
  2. View > Developer > Allow JavaScript from Apple Events

Accessibility Permission Issues

If Chrome control fails:

  1. Open System Preferences
  2. Security & Privacy > Privacy > Accessibility
  3. Ensure terminal app is listed and enabled
  4. 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

FAQ

What is the Google Search (via Chrome) MCP server?
Google Search (via Chrome) is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for Google Search (via Chrome)?
This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
MCP server reviews

Ratings

4.510 reviews
  • Shikha Mishra· Oct 10, 2024

    Google Search (via Chrome) is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Piyush G· Sep 9, 2024

    We evaluated Google Search (via Chrome) against two servers with overlapping tools; this profile had the clearer scope statement.

  • Chaitanya Patil· Aug 8, 2024

    Useful MCP listing: Google Search (via Chrome) is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Sakshi Patil· Jul 7, 2024

    Google Search (via Chrome) reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Ganesh Mohane· Jun 6, 2024

    I recommend Google Search (via Chrome) for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Oshnikdeep· May 5, 2024

    Strong directory entry: Google Search (via Chrome) surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Dhruvi Jain· Apr 4, 2024

    Google Search (via Chrome) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Rahul Santra· Mar 3, 2024

    According to our notes, Google Search (via Chrome) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Pratham Ware· Feb 2, 2024

    We wired Google Search (via Chrome) into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Yash Thakker· Jan 1, 2024

    Google Search (via Chrome) is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.